SQL Server clusters are great tools to ensure that your servers are highly available. However there are some times when you'll want to manually perform a failover for testing, maintenance, etc. New author Anthony Bressi brings you a technique and code to allow you to use VB 6.0 to build a small program to automatically do this.
2004-12-06
4,876 reads
2004-12-03
1,905 reads
SQL Server 2000 is easy to administer relative to other RDBMS, but there is still plenty of room for improvement. Author Andre Vigneau has built a database toolkit to allow him to manage his cross platform databases. This is the second article in his series and deals with establishing connections to any database platform.
2004-12-01
5,395 reads
The default location for the SQL Server system databases doesn't always meet the standards of many organizations. Author Chris Hedgate has taken the time to put together a short checklist on how you can move the master, msdb, model, and tempdb databases easily.
2004-11-30
21,826 reads
SQL Server was designed to make the DBA job easier, distribution of security, automated procedures, etc. But in some areas it either does not go far enough, or a feature is used for an unintended purpose. One of those areas comes into play when allowing many people to create databases. Author Eli Leiba brings us a tecehnique he uses to close the gap and track down those newly created databases.
2004-11-18
4,951 reads
SQL Server 7 revamped Enterprise Manager to be an MMC snap in with many more capabilities and functions than it had in SQL Server 6.5. Dale Elizabeth Corey brings us a look at the top ten features in Enterprise Manager that you may not be aware of.
2004-11-16
11,306 reads
SQL Server has a great scheduling system in SQLAgent. But sometimes SQLAgent won't work or isn't available. Author Andre Vigneau has built a solid system for auomtating the management of SQL Server, one that he deploys with the software that his company sells. Read about the basics of this system and get some code that might come in handy for you.
2004-11-04
5,864 reads
2004-11-02
1,854 reads
SQL Server shows lots of information in Enterprise Manager, but getting a report for someone or manipulating this data is hard from the GUI. Using T-SQL, it's easier, but sometimes not obvious how to get the data. Author Santveer Singh brings us a way to get at some of that information, the users and their database roles.
2004-11-02
23,760 reads
SQL Server 2005, the next evolution of SQL Server, should be growing the capacities as well as the capabilities of the product. With some research, Steve Jones brings you the best current information he could find about SQL Server 2005, comared with the SQL Server 7 and 2000 values.
2007-01-26 (first published: 2004-11-01)
41,889 reads
By Steve Jones
Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...
SQL Server 2025 introduces native support for vector data types and external AI models....
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
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...
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')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers