<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity Reseed on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/identity-reseed/</link><description>Recent content in Identity Reseed on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/identity-reseed/index.xml" rel="self" type="application/rss+xml"/><item><title>SQL Server DBCC CHECKIDENT: Check and Reseed Identity</title><link>https://www.sqlserver70.com/post/sql-server-dbcc-checkident-reseed-identity-columns/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/sql-server-dbcc-checkident-reseed-identity-columns/</guid><description>
&lt;p&gt;A logging table grew to forty million rows, the bulk of it was archived out, and now only the last week's data remains — but the next insert still gets identity value 40,000,001, leaving a vast gap below it. Or a botched data load left the seed sitting far above the real maximum, and future inserts skip millions of values. &lt;code&gt;DBCC CHECKIDENT&lt;/code&gt; closes both gaps in a single statement, and knowing how to check before you reseed keeps it from creating a worse problem than it solves.&lt;/p&gt;</description></item></channel></rss>