Data Portion and Used threshold

When Database Administrators manage multiple databases on multiple servers, it is difficult to keep track of and monitor the used percentage of data portion on every database. Though SQL Server has the capability of auto growth whenever the data portion reaches 100%, it is always advisable to increase the database size manually when it comes to VLDB. This article examines monitoring the percentage used on the data portion of every database and alerting the DBA using threshold settings. This article has been written for SQL Server 2000 server.

Running Out of Space

How many times have you run out of space in a database? What about on a file system? Andy Warren has had this happen a few times, especially when large imports take place. He brings us an article that describes some of the precautions he has taken to prevent this from happening.

SQL Server Management Studio

After quite a few versions, Enterprise Manager is being retired. SQL Server 2005 will have a new management tool called the SQL Server Management Studio (SSMS). Amit Lohia brings us a first look at some of the features of this new tool.

Installing and Upgrading to SQL Server 2005

If you have not had the chance to work with SQL Server 2005, or even if you have, Robert Pearl brings us some important information about what your upgrade or installation of the next version of SQL Server will bring. This is information every administrator needs to know to get prepared.

You have an index on the OrderDate column....

Finding Table Space

One of the most popular questions on SQL Server 2000 deals with determining how much space the various tables in your database take up. There are a variety of reasons for this and a few ways to gather the information. Author Amit Lohia takes a look at how sp_spaceused works and how you might customize it to suit your needs.

Querying System Tables

It is not recommended, but there is quite a bit of valuable information stored in the SQL Server 2000 system tables. Raj Vasant brings us a look at some of the information that you can get by directly querying the system tables and explains what is stored in a number of them, including gathering information about computed columns.

Enumerate SQL Server Names from "SQL Server Enterprise Manager"

Occasionally, SQL Server database administrators are requested to provide a list of development SQL Servers, production SQL Servers and so on. Many articles, such as "Monitor Disk Space on Multiple SQL Servers" and "Inventorying hardware and OS information on all SQL Servers" require a list of servers in a text file.

SQL Server 2005 System Tables and Views

When a SQL Server object is created, its properties are called metadata. The metadata is stored in special System Tables. For example, in SQL 2000, when a new column was created, the column name and data type could be found in an internal System Table called syscolumns. All SQL objects produce metadata. Every time SQL 2000 Enterprise Manager or SQL 2005 SQL Server Management Studio is browsed, the information displayed about database, tables, and all objects, comes from this metadata.

SQL Server 2005 Import/Export Server Registrations

SQL Server 2000 has a great management tool in Enterprise Manager, but one of the hassles is registering large numbers of servers on all your workstations. SQL Server 2005 makes this easier and new author Vinod Devasia shows us how.