2005-09-01
1,947 reads
2005-09-01
1,947 reads
How much backup data should you keep around and what are the implications? Part 2 of a series looking at backups and their implications.
2005-08-30
2,752 reads
2005-08-23
2,152 reads
2005-08-18
1,889 reads
2005-08-10
1,974 reads
2005-08-04
2,100 reads
2005-07-28
1,880 reads
2005-07-15
1,740 reads
2005-07-07
1,860 reads
2005-06-30
1,621 reads
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...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
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