Tag: troubleshoot

Have you ever faced allocation contention problems with tempdb database in SQL Server 2000? If yes then you might be ended up with the recommendation to enable trace flag 1118** as per http://support.microsoft.com/kb/328551 or http://support.microsoft.com/kb/936185. By default when you create a temporary object it will allocate a single page to that object searching SGAM however…

Have you ever tried to capture when CHECKPOINT is happening to the database? If not then you can utilize trace flag 3502 to capture CHECKPOINT information to errorlog. You need to add this trace flag to SQL Server startup parameter to capture these information when CHECKPOINT triggers. This will help you to analyze how frequently…

In one of our development server we will be frequently running trace files to capture information for performance trouble shooting. However this in turn writes so many entries about trace file in errorlog which fills the errorlog. Errorlog entry is big and we are not to search it easily so to avoid the trace information…

Today we are going to see how can we attach data file exists in network share with the help of trace flag 1807. By default SQL Server 7,2000 and 2005 will not allow you to attach data file that exists in network share. This is the default behavior because attach database file from network share…

Today I’m going to cover trace flag 3604 & 3605. These two trace flags are used to print information’s or output from DBCC commands. As far as I know these two trace flags are widely used to get output for DBCC IND & DBCC PAGE commands. These two commands will not print anything unless or…