Jul 272013
 
SQL Tip-5 | Lightning Fast way to find errors in SQL Server Error Logs

In my first SQL Tip Don’t forget to recycle your SQLServer ErrorLog I listed some common problems you may face if you are not recycling your errorlogs timely. However, I do understand the criticality and importance of Error Log that’s the reason I also suggested you to increase the retention of your Error Logs in [Read More]

Jul 252013
 
SQL Tip-4 | Do you know you can increase number of archived Errorlogs

By default, SQL Server keeps only seven error logs; Errorlog and Errorlog.1 to Errorlog.6. The name of the current, most recent log is Errorlog with no extension. In my SQL Tip-1 I advised why you should recycle your errorlog on frequent basis and how. But as we know when you recycle errorlogs SQL Server makes [Read More]

Jul 252013
 

Disable “xp_cmdshell” where it is not required. If this is required for some admin tasks make sure you disable this post completion of the activity to reduce surface area. Related posts: Best Practice No.1 Best Practice No.4 Best Practice No.18 Best Practice No.12

Jul 232013
 

You should avoid shrinking your database until and unless it becomes unmanageable. Shrinking is a Resource intensive task, Moreover it introduces high degree of fragmentation which affects performance. Let’s say you shrink a Database, Now if the data is growing in your database the data\log file will reserve more space by auto-growth (if configured) to meet the [Read More]

Jul 212013
 
Virtual Tech Conference | 1st August 2013 | 4PM till 10PM

Here is another chance to learn from MVPs. Microsoft & MVPs present VTC – Virtual Tech Conference – 12 Hours of non stop learning. Register Today & Block your Seat, here are the URLs and the complete Agenda. http://virtualtechconference.azurewebsites.net/ To Register for Dev: http://aka.ms/OzhcyhIT Pro: http://aka.ms/Uu9msj   Time Speaker Dev Track Sessions 4:00PM IST/6:30AM EST [Read More]

Jul 182013
 

I know this one is very basic but in the recent past I noticed a couple of environments where the startup type of SQL Server Agent was set to manual which resulted in lot of issues. Long story cut short – if your SQL Server is not clustered make sure the startup type is set [Read More]