2026-03-16 (first published: 2026-03-11)
1,078 reads
2026-03-16 (first published: 2026-03-11)
1,078 reads
2026-03-16
771 reads
2026-03-13
1,177 reads
2026-03-09
919 reads
2026-03-06
517 reads
2026-03-04 (first published: 2026-03-02)
1,033 reads
2026-03-04
591 reads
2026-03-04 (first published: 2026-02-27)
730 reads
2026-02-25
1,121 reads
2026-02-23
979 reads
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
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