2003-12-22
2,182 reads
2003-12-22
2,182 reads
2003-12-19
1,752 reads
2003-12-18
1,972 reads
2003-12-17
2,257 reads
2003-12-16
2,500 reads
Why would you ever create duplicate indexes? Does that even make sense? Steve Jones isn't sure, and that's for another day, but it sure caused him some problems. Follow along and find a solution for tracking these down.
2003-12-15
5,114 reads
2003-12-15
2,014 reads
2003-12-12
2,174 reads
2003-12-11
1,981 reads
2003-12-10
2,095 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