sql server performance tuning videos

After a period of research, we started to optimize the performance this week. Before optimization, I will summarize some of the information I have investigated. 1. Background This is a system developed in the past 03 years. NET 1.1 + SQL Server 2000, the operating system uses Windows2003. After so many years of use, the operating system was upgraded (from Windows

The source of this article: http://www.cnblogs.com/wy123/p/7106861.html(It is not the original works right to retain the source, I my book still far to reach, just to link to the original text, because the following may exist some errors to amend or supplement, without him)Recently encountered in SQL Server several times the developer submitted the performance pr

implemented in a stored procedure, we use a undocument query hint directly on the statement, which causes the parallel cost threshold of the query to be reduced to 0, which forces the statement to go parallel and the statement execution time from 20 seconds to 5 seconds (note: Using the hash join hint is 7 seconds). The following is a simple example of the effect of using this hint, as shown in Listing 1 of the sample T-sql: from [AdventureWorks]. [S

, Daysarray.length-2, Guidarray, guidarray.length-6, 2);Array.copy (Msecsarray, msecsarray.length-4, Guidarray, guidarray.length-4, 4);return new System.Guid (Guidarray);}Generate time information from the GUID returned by SQL SERVERpublic static DateTime Getdatefromcomb (System.Guid Guid){DateTime basedate = new DateTime (1900,1,1);byte[] Daysarray = new Byte[4];byte[] Msecsarray = new Byte[4];Byte[] Guidarray = GUID. Tobytearray ();Copy the date par

the same, does not necessarily apply to the current query, the performance problem is generated.Why is the execution plan compiled with a completely inconsistent current, and the cache has not been cleaned up so far? There are two reasons for personal speculation, but it is not entirely certain thatOne is based on the current data distribution (statistical information) obtained by an implementation plan, it may be that the statistics are not accurate

high-performance applications. I am not a DBA, but an ordinary developer. The above are some experiences and experiences in my practical work. In view of my very limited level, if you say something wrong or cannot understand it, I hope you can correct it to avoid misleading others. I am very grateful. In the future, I will continue to write some practical experience on SQL

Unlike other SQL Server databases, tempdb stops at SQL Server and automatically drops and re-create upon restart. by default, a new 8 MB (MDF file: 8 MB; LDF file: 1 MB, autogtouth is set to 10%) recovery model is a simple tempdb database. After the tempdb database is created, DBA can create data objects, temporary

target_recovery_time = [number of seconds or minutes]As mentioned earlier, SQL Server analyzes the current system pressure and, when it considers that there is no need to checkpoint at this time, kills the process, thus preventing the disk subsystem from becoming worse. When checkpoint is throttled, it is recorded in the information of the Sleep_bpool_flush wait type.Under normal circumstances, this wait s

-consuming to index the above, so the efficiency is lower than using the self-increment field.3, CombGiven the pros and cons of the two primary key types above, the comb type can be used to find a balance for both. Its design idea is this: since the GUID type has no regularity can be made index inefficient, affecting the performance of the system, then can not be combined to preserve the GUID of the first 10 bytes, with the latter 6 bytes to represent

SQL Server performance optimization -- wait -- SLEEP_BPROOL_FLUSHPreface: There is a database for historical archiving (referred to as the historical database). After a certain amount of time, the data file has reached more than 700 GB, and it was decided that some data does not need to be retained, this part of data is truncate and more than 600 GB of space is a

Use Windows performance monitor to monitor common SQL Server metrics As mentioned in the above article, Win's Performance Monitor is an essential tool for monitoring database performance. Next I will introduce some common monitoring metrics, which are nothing more than disks