T-SQL Tuesday #62 - Achieving Healthy SQL with MDW
Today:
Tuesday, January 13, 2015 is the 62nd entry and first T-SQL Tuesday
of the year 2015, and I am honored to...
2018-03-27 (first published: 2015-01-13)
8,748 reads
Today:
Tuesday, January 13, 2015 is the 62nd entry and first T-SQL Tuesday
of the year 2015, and I am honored to...
2018-03-27 (first published: 2015-01-13)
8,748 reads
So, here’s a silly little take on a serious end-user issue where no-one could access the production database.
Got a call...
2017-08-11 (first published: 2014-04-07)
122,105 reads
So, the new industry buzz word is Data Science. Are you a Data Scientist? Do you remember taking that in...
2016-08-23
1,568 reads
Wednesday, August 10, 2016, The next meeting of the Central NJ SQL Server Users Group will be on Wednesday August...
2016-08-09
1,159 reads
Well, today is a busy T-SQL Tuesday no. 79, (it's also Flag Day in the U.S, and also a clerical...
2016-06-14
1,837 reads
Quick post-event follow-up of our very successful SQL Server 2016 NYC Launch Event! We would like to thank ALL our...
2016-06-10
1,395 reads
Presenting the OFFICIAL SQL Server 2016 NYC Launch Event Schedule for Thursday, June 2, 2016, just ONE day after the...
2016-05-31
1,949 reads
In a previous blog, I spoke about the upcoming RTM Launch of SQL Server 2016 - Get Ready! Microsoft is ready...
2016-05-24
1,322 reads
You've been waiting, you've been asking, some begging to know the magic date of when Microsoft's SQL Server 2016 will...
2016-05-06
1,117 reads
By now, all you folks who logged on to watch the ultimate Microsoft Data Driven event, streamed live from New...
2016-03-11
1,249 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