How to Edit Read-Only Non-clustered Columnstore Data
As I've discussed in some of my previous posts, creating a non-clustered Columnstore index will make the index as well...
2014-08-06 (first published: 2014-07-29)
8,110 reads
As I've discussed in some of my previous posts, creating a non-clustered Columnstore index will make the index as well...
2014-08-06 (first published: 2014-07-29)
8,110 reads
As I’ve discussed in some of my previous posts, there are quite a few data types that cannot be part...
2014-07-08
757 reads
In a previous post about non-clustered columnstore indexes, I mentioned the creation of an index is a very memory intensive...
2014-06-03
2,177 reads
SQL Server 2012 introduced non-clustered columnstore indexes, and SQL Server 2014 gave us clustered columnstore indexes. Both share the same...
2014-05-20
1,825 reads
First introduced in SQL Server 2012, the Columnstore index is a new in-memory feature that allows for the creation of...
2014-04-29
5,563 reads
When I first started poking around in SQL Server 2012, I noticed an extended event session called “system_health” was created...
2014-04-21 (first published: 2014-04-08)
4,046 reads
Have you ever needed to restore a large database while someone is standing over your shoulder asking “How long is...
2014-03-04
3,235 reads
Where do I begin? First let me say, WOW what an experience!
How it All Began
When I first heard about SQL...
2014-02-11
1,365 reads
In a previous post, Collecting Historical Wait Statistics, I discussed how you can easily collect historical wait stats by using...
2013-12-17
1,462 reads
As a DBA, I'm sure you've heard many times to always check the sys.dm_os_wait_stats DMV to help diagnose performance issues...
2013-12-16 (first published: 2013-12-11)
2,489 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