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.

Long Running Jobs

SLQ Server has a fantastic job scheduling system, but there are some times that things go wrong. Leo Peysakhovich brings us another great article that looks at a way to check if your job engine is running and how to restart it. Practical code included in this one.

What is the most recent service pack for...

SQL Server 2005 - Setup and Deployment

So far, in our series of articles, we have presented the most significant new and enhanced features available in Microsoft's SQL Server 2005 Beta 2, but neglected to provide you with information regarding its installation. While it is more than likely that, by now, you already have accomplished this entirely on your own, we suspect that you still should be able to benefit from a more in-depth analysis of the setup process. Explaining improvements in its design and implementation is the primary purpose of this article.

SQL Server 2005 Roadshows

Ongoing now, the SQL Server 2005 Roadshows in conjunction with PASS. Read Robert Pearl's notes from the show and if you are in Dallas or Houston or Europe, there is still time to attend on of these events.

Identifying Long Running SQL Server Agent Jobs

In my article last month, I wrote about different methods you could use to identify the state of a SQL Server Agent job. One of the methods I discussed was using the undocumented extended stored procedure (XP) "xp_sqlagent_enum_jobs." In this article, I will show you how to use the "xp_sqlagent_enum_jobs" XP to help identify long running jobs.

Controlling Unusually Long Running Jobs

The SQLAgent scheduler in SQL Server 2000 is an amazing tool that allows you to schedule many different kinds of jobs with a great deal of flexibility. However, it doesn't have great facilities for handling jobs that may take longer than expected. And about which you'd like to be notified. Leo Peysakhovich brings us his code and technique for detecting when a job step runs long.