2025-10-03
463 reads
2025-10-03
463 reads
2025-09-26
378 reads
2023-07-31
511 reads
2023-07-19
416 reads
There are a number of ways to generate key values in SQL Server tables including the IDENTITY column property, the NEWID() function and more recently, SEQUENCES. The IDENTITY column property is the earliest of these methods. It was introduced very early in the history of SQL Server and it is arguably the simplest approach. Though old, IDENTITY is still maintained in modern versions of SQL Server and is still relevant for simple use cases.
2020-05-21
8,465 reads
2024-12-23 (first published: 2020-05-05)
767 reads
2020-03-06
703 reads
2020-02-27
724 reads
In this tip we look at how to change the SQL Server setting for a tables identity column to not for replication for existing tables.
2019-05-03
2019-02-26
1,140 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers