The Service Pack Fiasco
The recent SQL Server 2014 Service Pack fiasco wasn't the first, but hopefully it won't be the last.
2015-05-11
204 reads
The recent SQL Server 2014 Service Pack fiasco wasn't the first, but hopefully it won't be the last.
2015-05-11
204 reads
In which Phil Factor claims that professional application development requires a broad knowledge base.
2015-05-11
99 reads
This week's poll asks about virtualization in your environment. Let us know if you are moving your SQL Server to virtual machines.
2019-03-20 (first published: 2015-05-08)
187 reads
Steve Jones looks at the next version of SQL Server, SQL Server 2016. Until this week, it was known as vNext.
2015-05-07
270 reads
There are all sorts of coding practices that produce better code. Steve Jones talks about one today.
2024-11-04 (first published: 2015-05-06)
550 reads
It doesn't seem to be a feature that an auditing system can fail, but the application being audited continues to run.
2018-10-26 (first published: 2015-05-05)
140 reads
2015-05-04
57 reads
When we write scripts, we often assume many settings will be at some default value. When we generate scripts, that's not the case. Perhaps we should be sure that we always include the settings we expect.
2015-05-04
123 reads
This week Steve Jones has a poll on performance tuning code. Since many people aren't experts, the answers this week might help them learn where to focus their efforts.
2015-05-01
218 reads
Today Steve Jones looks at the reasons for upgrading, or not, from SQL Server 2005.
2015-04-30
192 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,...
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...
We have a tool called DB Moto that reads journals (like t-logs) and replicates...
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