SQL Server in a MSCS cluster can't backup...

Making Good Use of Sysforeignkeys Table - Part 1: Display table relati

Sysforeignkeys is a valuable SQL Server resource. How many times have you had to "pick up the pieces" from a database developed by someone else and dropped on your desk? Ever get a database diagram with that? A data dictionary? Probably not too often. Jeffrey Yao has developed a system of finding those parent-child relationships automatically and displaying them so he can get up to speed quickly on these inherited databases. Read on to find out more.

The workload governer in SQL Server 2000 Personal...

What is the difference between using the NO_LOG...

You have installed a new database (Sales) for...

In a Sales database that you have, the...

Every DBA Should Know Which Databases are be Backed Up

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.

What's the difference between user_name() and suser_sname()?

Does setuser affect user_name()? Does it affect suser_sname()

Creating a System Stored Procedure

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.