The user connections/activity will be having SPIDs over 50 and most of the internal checks will be below that number.

I like to pull the error logs using running SP : SP_readerrorlog.This is much simple and easy to read.

You can run DBCC  TRACESTATUS to pull the info.

These are really useful trace flags : Stop logging all successful backups in your SQL Server error logs : DBCC  TRACEON(3226,-1) Capture deadlocks in SQL Server error logs : DBCC…

This will pull server level info and will provide information on couple of things which are really useful : ProductName ProductVersion Platform FileVersion ProcessorCount

There are many assumptions on SQL Server compatibility option which is available.Changing the compatibility is major for the T-SQL changes which comes in with different versions.

There are some important news about SQL 2000 and 2005 support.Please read the article below for more information: http://www.microsoft.com/sqlserver/en/us/support/support-updates.aspx The best suggestion for everyone is to migrate to the latest…

A basic assumption is that you take a backup and you are safe.This is not at all a right approach.You have to verify your backup set and confirm that its…

SQL Server configuration manager throws this error sometimes if we change start-up parameters for any instance and the solution is :   Start > Run > type services.msc and press…

ALTER INDEX REBUILD you don’t need to update the statistics.Statistics are updated as part of an index rebuild. If you use ALTER INDEX REORGANIZE however, you may want to update…