2012-04-09
52 reads
2012-04-09
52 reads
This Friday Steve Jones asks about your on-call responsibilities and the load you face from after hours calls. If you're a DBA that doesn't work strictly 9-5 every week, let us know.
2012-04-06
164 reads
Steve Jones reminds us that our databases contain code, and as such, they ought to be under some type of version control.
2012-04-05
215 reads
Today Steve Jones talks about his favorite feature in SSMS 2012 and why everyone should use it.
2012-04-04
615 reads
Too much data can be as much of a problem as too little. Today Steve Jones talks about some problems that we have in working with lots of data and how we might address the issues. Those that do well, will succeed in the future.
2012-04-03
186 reads
No April Fool's jokes from SQLServerCentral this year and Steve explains why today.
2012-04-02
274 reads
Tony Davis argues that the WITH REPLACE option of the RESTORE DATABASE command is a case where the naming of the option masks its true "JFDI" nature…
2012-04-02
148 reads
Today's editorial was originally published on May 13, 2007. It is being re-run as Steve is at SQL Server Connections. Today Steve Jones talks about the need to train yourself, just like people in other professions.
2012-03-30
204 reads
Today's editorial was originally published on Apr 17, 2007. It is being re-run as Steve is at SQL Server Connections. Today Steve talks about the Mechanical Turk process at Amazon.
2012-03-29
220 reads
Today's editorial was originally published on Apr 27, 2007. It is being re-run as Steve is at SQL Server Connections. Today Steve talks programming.
2012-03-28
362 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') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers