Keeping track of your DDL is something that is critical and some sort of VCS system should be used. However pulling out your scripts from SQL Server sometimes entails a bit more than the standard scripting. New author Richard Sutherland brings us an open source project that can help you get this done. Complete with code.
Read more...

As a SQL Server DBA you should know that your code is stored in syscomments by default. While most DBAs use version control systems, there are times you might want to look through the code on the server for comparison purposes. Robert Cary brings us an article on how you can do this in 2000 and 2005.
Read more...

Most DBAs are constantly looking for ways to tune their servers to run better. Joe Doherty brings us the second part of his series on indexes with an in depth look at how the indexes are stored in your database.
Read more...

Monitoring your servers for issues and alerts is something every DBA should be doing on a regular basis. However even with a small number of servers, a DBA can easily be overwhelmed if some level of automation is not implemented. Thomas LaRock brings us a method of scanning your error logs automatically and notifying the DBA of problems.
Read more...

One day, you may need to change those service credentials under which your SQL Server services normally run. If you have a number of servers, then you'll really want to read about Rodney's solution.
Read more...

Keeping track of your DDL is something that is critical and some sort of VCS system should be used. However pulling out your scripts from SQL Server sometimes entails a bit more than the standard scripting. New author Richard Sutherland brings us an open source project that can help you get this done. Complete with code.
Read more...

This article covers the basics of full backup backups and restores in SQL Server. The examples are from SQL Server 2005 however it applies to SQL Server 2000 and SQL Server 2005. This is a very basic article covering full database backups, database restores and the simple and full recovery models.
Read more...

As a SQL Server DBA you should know that your code is stored in syscomments by default. While most DBAs use version control systems, there are times you might want to look through the code on the server for comparison purposes. Robert Cary brings us an article on how you can do this in 2000 and 2005.
Read more...

Monitoring your servers for issues and alerts is something every DBA should be doing on a regular basis. However even with a small number of servers, a DBA can easily be overwhelmed if some level of automation is not implemented. Thomas LaRock brings us a method of scanning your error logs automatically and notifying the DBA of problems.
Read more...

Most DBAs are constantly looking for ways to tune their servers to run better. Joe Doherty brings us the second part of his series on indexes with an in depth look at how the indexes are stored in your database.
Read more...

As DBAs we try our best to appropriately size a SQL Servers to match the anticipated load. But things change over time and we may find that some databases are overloading the server. When it's time to move your database to a new home on another server, Paul Mu brings us a technique for doing so.
Read more...

Trending the size data for your databases can be crucial when ordering new hardware or just ensuring that you can handle the load. In Part 3, Roy Carlson looks at how you get the sizes needed for your instances into Excel and generate a chart for trending of this important piece of performance data.
Read more...