2006-03-30
1,626 reads
2006-03-30
1,626 reads
It is something you do rarely, but with SQL Server 2005 and ten services, there are more decisions to make. Steve Jones gives some advice on which service accounts to choose and some common problems with others.
2006-03-30
18,760 reads
2006-03-23
1,304 reads
Are you aware that SQL Server 2005 can have up to ten services running? Working with that many service accounts can be a challenge. Steve Jones takes a look at these services and a few of the things that you will want to know before setting up SQL Server 2005.
2008-07-11 (first published: 2006-03-23)
50,559 reads
2006-03-21
1,890 reads
It is an interesting question and one I hope every DBA can answer positively. New author Thomas LaRock brings us his method for ensuring that the backups have occurred and the files are still on disk.
2006-03-21
8,032 reads
Every DBA needs a few tricks up his/her sleeves to help them better manage their SQL Server 2000 environment. In this article I will explore a couple of such tricks. I will first explore how to cycle the SQL Server error log, and why you might want to do this. Secondly I will discuss backup history information and why you would need to periodically remove some of the older history information.
2006-03-16
2,855 reads
2006-03-13
1,818 reads
SQL Server 2000 has a rock solid backup scheme , but do you really need to run full backups every day? What if you could decide on the fly if it was more efficient for a full or a differential backup? Darwin Hatheway brings us the basis for a scheme that can predict the size of a differential backup by examining how much of the database has changed.
2006-03-13
7,452 reads
2006-03-09
1,841 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