2005-07-26
1,363 reads
2005-07-26
1,363 reads
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.
2005-07-18
1,765 reads
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.
2005-07-14
11,181 reads
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.
2006-11-24 (first published: 2005-07-07)
31,665 reads
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.
2008-01-11 (first published: 2005-06-29)
199,271 reads
2005-06-27
2,251 reads
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.
2005-06-23
13,455 reads
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.
2007-10-02 (first published: 2005-06-13)
39,747 reads
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.
2005-06-08
2,281 reads
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.
2005-06-07
3,314 reads
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
We have a report that has multiple tables that list the top 15 performers...
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9 GO DBCC CHECKIDENT(TravelLog, RESEED) GO INSERT dbo.TravelLog ( CityID, StartDate, EndDate ) VALUES (4, '2025-09-14', '2025-09-17') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers