2004-05-25
2,015 reads
2004-05-25
2,015 reads
Do you know which of your databases are being backed up? Everyone answers "Yes", but I'm sure that there are times that someone creates a new database and you don't know about it. I know in my job, with hundreds of servers, it happens. Here's a technique for keeping track of those databases from Leo Peysakhovich.
2004-05-24
13,493 reads
2004-05-21
1,949 reads
2004-05-20
1,533 reads
Creating a system stored procedure isn't hard. You're always cautioned from making changes to the system, depending on the system for a particular functionality, etc., and you should be cautious. However adding system stored procedures to your servers can be beneficial and make your administration much more convenient. Read on the see how easy this can be to do.
2004-05-20
13,991 reads
2004-05-19
1,782 reads
This article by Chris Kempster shows you how to quickly move a database by detaching or taking a database offline.
2008-02-08 (first published: 2004-05-18)
148,336 reads
2004-05-17
1,828 reads
Another article from our own Chris Hedgate! This one looks at the different types of fragmentation that can exist inside your SQL Server and some ways you can go about minimizing them.
2007-10-02 (first published: 2004-05-10)
48,395 reads
Here's a little replacement for Query Analyzer that appears to provide most of the functions, plus a few more. While we haven't given it a full review, at first glance it appears to do the job. Plus there's NO INSTALL!!!! Always a plus for me.
2004-05-07
760 reads
By Arun Sirpal
Until now, a CRITICAL finding did the right internal routing, but the last mile...
By Steve Jones
This is actually inspired by an article SQL Server Central, which taught me something...
By alevyinroc
T-SQL Tuesday is a monthly blog party hosted by a different community member each...
Comments posted to this topic are about the item How Clustering can be Used...
Comments posted to this topic are about the item Moving the Error Log
Comments posted to this topic are about the item A Security and AI Fail
How can I change the location in which the SQL Server error log is written in SQL Server 2025?
See possible answers