Do you have startup procedures? In some scenarios we might be having some startup procedures in our SQL Server system and we might face some issue during starting SQL server. So for troubleshooting purpose we might need to bypass the startup procedures so that SQL Server don’t need to grant worker thread for each procedure.
This is one of the familiar trace flag for every DBA. If you are working with SQL Server 2000 then to move the system databases you will be using this trace flag frequently. What does this trace flag do? When you enable this trace flag in startup parameter it will bypass recovery for all databases including system databases except master database.
Today we are going to see two trace flags which is going to help for troubleshooting purposes. These two trace flags will get you full SQL Server dump by using the undocumented DBCC command. Continue reading Day 8 – Trace Flags 2544 & 2546 – Generate Full dump from SQL Server
Happy Weekend folks. Today let me discuss about trace flag 2528 which will disable parallelism on maintenance DBCC. By using this trace flag it disables parallel checking of objects by DBCC CHECKDB, DBCC CHECKFILEGROUP, and DBCC CHECKTABLE commands. By default parallelism is enabled and it will look for max degree of parallelism to utilize parallel processors for all queries however in some scenarios if you want to turn off parallelism for maintenance DBCC commands then you can utilize this trace flag so that you can utilize other processors for your adhoc queries and other operations
Today we are going to see the trace flag 1117. Have you ever heard or read that all your data file should be in same size? Wonder why? Let’s assume you have four files in a database which is not equally sized then SQL Server will utilize the data file which is largest in size, assume you have auto growth option enabled then obviously that file will grow and SQL Server will keep on using the data file which is largest in size.