2026-03-16
146 reads
2026-03-16
146 reads
2026-03-09
913 reads
2026-03-04 (first published: 2026-03-02)
1,031 reads
2026-02-16
678 reads
Learn about the critical 823 and 824 errors in SQL Server and how to deal with them in this article.
2025-12-01
1,463 reads
Short story: what the title says.
2025-11-24
2025-11-10
1,046 reads
2025-11-07
1,219 reads
2025-11-03
1,289 reads
2025-09-24
352 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