Editorials

Food for Thought for SQL Server

Featured Article(s)
Find all Un-Restricted/Restricted Sized db files on SQL Server
The following stored procedure finds all files on the server (with difference between log and data files ) that have / do not have a MAX SIZE limit These file can auto-Grow to consume all space on the drive. The procedure can report data files or log files.

SelectViews Special
People have been asking what a vConference session is like. Today we’re releasing a sample session for the show this week so you can see exactly what it’s like. Today’s show is Buck Woody of Microsoft going through the essentials of Disaster Recovery – Database Recovery 101 – Find out about what makes your database tick and how this impacts recovery. Learn about recovery models and more. (Special vConference Session)

[Watch the show here]

Food for Thought for SQL Server
A couple of things to consider today – things that are quick and dirty and can help in managing your SQL Server(s)

– Consider reviewing your maintenance plans. Go back, look through your plans and make sure they’re doing what you need and expect of them. So many people have set up maintenance plans and then never look back to make sure they’re still doing what you need them to do. Make sure that you are using your best lessons learned in these plans – from reindexing operations to backups to shrinking your database (if you really have to do this) and the other options you have with these utilities. Make sure, too, that you’re tracking the success and failure of these jobs. Finally, look through the execution history for the jobs. Make sure they’re running without issue as you expect.

– Check your file locations. This pertains to the physical location of files. From database files to log files to OS files, you want to split your major categories of files across disk spindles. This means you want to, if at all possible, put them on different physical drives (logical drives don’t count). This can help with performance on your system by alleviating congestion on the disk level. Avoid having both databases and transaction logs on the same physical drive, and avoid having the operating system share a drive with your database storage. Each of these can cause contention when it comes to disk access and contention leads to poorer performance.

Featured White Paper(s)
Understanding Business Intelligence: ETL Best Practices
This paper is about building powerful data marts that require minimal administration and are simple to change. This may seem … (read more)

Addressing the Insider Threat
This paper discusses the current state of database security, and the importance of activity monitoring and vulnerability asse… (read more)