http://www.sqlservercentral.com/Articles tagged Administering, Monitoring, SQL Server 7, 2000 posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)Monitoring in the real world. Roy Carlson concludes his series on space monitoring for your SQL Servers with a real world example of how he found a problem and fixed it. http://www.sqlservercentral.com/articles/Administering/2681/2006/11/09http://www.sqlservercentral.com/articles/Administering/2681/Joe has a bunch of small, easy to use scripts that can definitely be the beginning of a great set of monitoring tool. Amazing how much info you can gather with a little bit of code! http://www.sqlservercentral.com/articles/Administering/sevenmonitoringscripts/1024/2005/05/13http://www.sqlservercentral.com/articles/Administering/sevenmonitoringscripts/1024/One of the biggest performance gains built into SQL Server is the stored procedure. In this article by Brian Kelley, he shows you how to fully utilize, debug and monitor the caching of such objects. http://www.sqlservercentral.com/articles/Administering/procedurecache/591/2004/11/19http://www.sqlservercentral.com/articles/Administering/procedurecache/591/Knowing which databases are being backed up is a critical thing for all DBAs to know. After reading an article on this subject, new author Santveer Singh decided to share his own techniques for checking SQL Server databases and their backup status. He shows us how to look for failed backups as well as find those databases which have not been backed up. http://www.sqlservercentral.com/articles/Administering/whichdatabasesarebeingbackedupanotherlook/1390/2004/06/09http://www.sqlservercentral.com/articles/Administering/whichdatabasesarebeingbackedupanotherlook/1390/New Author! We've run a couple articles on similar topics, this one takes a slightly different approach. It's a short article and has two scripts included. http://www.sqlservercentral.com/articles/Administering/monitoringfailedjobsteps/1301/2004/03/01http://www.sqlservercentral.com/articles/Administering/monitoringfailedjobsteps/1301/Are you using alerts to help you keep track of things? Are you using as many alerts as you should be? Jeremy has a great list of alerts that he considers so important they are on his 'best practice' list. Definitely worth reading. http://www.sqlservercentral.com/articles/Administering/alertalertbackupandrestorebaby/1253/2004/01/08http://www.sqlservercentral.com/articles/Administering/alertalertbackupandrestorebaby/1253/The second part of Steve Jones's series on having SQL Server automatically report information to a DBA. http://www.sqlservercentral.com/articles/Administering/20010422115754/85/2003/12/25http://www.sqlservercentral.com/articles/Administering/20010422115754/85/Ever wanted to use the SQL Trace system stored procedures instead of Profiler, but got intimidated by the cryptic system stored procedure calls? Then this article is just for you. It will show you how to use SQL Trace system stored procedures and provide you with wrapper stored procedures, that can be used to quickly get server side traces up and running. http://www.sqlservercentral.com/redirect/articles/1214/2003/12/10http://www.sqlservercentral.com/redirect/articles/1214/Don't like the blackbox approach of maintenance plans? Like the maintenance plans but need a tweak to suit your needs? New author Robin Back has put together a monster script to allow you to build your own quickly and easily. http://www.sqlservercentral.com/articles/Administering/createmaintenancejobwithaclickwithoutusingawizard/1102/2003/08/20http://www.sqlservercentral.com/articles/Administering/createmaintenancejobwithaclickwithoutusingawizard/1102/Joe has a bunch of small, easy to use scripts that can definitely be the beginning of a great set of monitoring tool. Amazing how much info you can gather with a little bit of code! http://www.sqlservercentral.com/articles/Administering/sevenmonitoringscripts/1024/2005/05/13http://www.sqlservercentral.com/articles/Administering/sevenmonitoringscripts/1024/New author! Mike Pearson discusses how auto close was at the root of a performance problem he was troubleshooting, how you can check your servers easily, and discusses why both auto close and auto shrink are bad ideas in a production environment. http://www.sqlservercentral.com/articles/Administering/autocloseandautoshrinkjustdont/984/2003/05/05http://www.sqlservercentral.com/articles/Administering/autocloseandautoshrinkjustdont/984/A monster book at 980 pages, it's written in 'how-to' format and has a ton of good material. Andy gave it the once over for us and reports back - see what he thinks! http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/2003/04/18http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/Have you ever had the problem where a user ran a query against your SQL Serer and crashed it or made the server unusable since the CPU was spiked at 100%? A SQL Server black box is the equivalent of a flight data record. The black box records all queries being passed to your SQL Server and other useful information like errors. http://www.sqlservercentral.com/articles/Administering/blackbox/954/2003/04/11http://www.sqlservercentral.com/articles/Administering/blackbox/954/We've had a good run of jobs about job management lately, Randy sent us another one that looks at the job of job management and shows us how he tackled the problem. http://www.sqlservercentral.com/articles/Administering/managingjobsusingtsql/945/2003/04/02http://www.sqlservercentral.com/articles/Administering/managingjobsusingtsql/945/Jobs are pretty basic aren't they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading! http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/2003/02/14http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/How many jobs do you have? 10? 100? 1000? Andy makes the point that what works to manage for a small number of jobs doesn't work when that number doubles or triples (well, unless you only had 1 job to start with!). In part one of two, this article looks at ideas for using categories and naming conventions to get things under control. http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/2003/01/31http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/Andy says Windows Authentication "is bad". What? That's not what Microsoft says! Heck, that's not even what we say! Everyone knows NT authentication is the way to go. Then again, when was the last time Andy wrote an article that wasn't worth reading?! Read the article, rate it and add a comment - and automatically be entered in a drawing for a copy of SQL Server 2000 Performance Tuning donated by Microsoft Press. http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginspart1/714/2002/06/25http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginspart1/714/In this article by Robert Marda, he shows you how to detect and correct deadlocks. http://www.sqlservercentral.com/articles/Administering/exploringdeadlocks/616/2002/02/19http://www.sqlservercentral.com/articles/Administering/exploringdeadlocks/616/One of the biggest performance gains built into SQL Server is the stored procedure. In this article by Brian Kelley, he shows you how to fully utilize, debug and monitor the caching of such objects. http://www.sqlservercentral.com/articles/Administering/procedurecache/591/2004/11/19http://www.sqlservercentral.com/articles/Administering/procedurecache/591/Running a script automatically from SQL Server is easier than you think. Here are a few methods you can use. http://www.sqlservercentral.com/articles/Administering/scriptscheduling/450/2001/10/17http://www.sqlservercentral.com/articles/Administering/scriptscheduling/450/Have you ever worked with an application that forgot to close its connections? Ever run out of connections on your SQL Server and had to manually go remove the ones that are not in use? This article will present a technique for keeping the database clean. http://www.sqlservercentral.com/articles/Administering/sweepuptheslackers/158/2001/05/07http://www.sqlservercentral.com/articles/Administering/sweepuptheslackers/158/The eighth part of Steve Jones's series on having SQL Server automatically report information to a DBA. http://www.sqlservercentral.com/articles/Administering/20010423065956/94/2001/04/29http://www.sqlservercentral.com/articles/Administering/20010423065956/94/The sixth part of Steve Jones's series on having SQL Server automatically report information to a DBA. http://www.sqlservercentral.com/articles/Administering/20010422115803/89/2001/04/25http://www.sqlservercentral.com/articles/Administering/20010422115803/89/The fifth part of Steve Jones's series on having SQL Server automatically report information to a DBA. http://www.sqlservercentral.com/articles/Administering/20010422115801/88/2001/04/24http://www.sqlservercentral.com/articles/Administering/20010422115801/88/The fourth part of Steve Jones's series on having SQL Server automatically report information to a DBA. http://www.sqlservercentral.com/articles/Administering/20010422115759/87/2001/04/22http://www.sqlservercentral.com/articles/Administering/20010422115759/87/The third part of Steve Jones's series on having SQL Server automatically report information to a DBA. http://www.sqlservercentral.com/articles/Administering/20010422115756/86/2001/04/20http://www.sqlservercentral.com/articles/Administering/20010422115756/86/