2004-10-26
2,144 reads
2004-10-26
2,144 reads
2004-10-22
2,698 reads
2004-10-21
2,262 reads
2004-10-20
1,824 reads
2004-10-19
2,565 reads
2004-10-15
1,831 reads
2004-10-14
2,618 reads
2004-10-12
2,323 reads
Part 2 of Steve Jones' Incident Response series that looks at how you should be prepared as well as what to do when disaster strikes. Part 1 established a basic framework and part 2 dives deeper into what you might need for the next virus, hardware failure, or hurricane :(.
2004-10-11
4,922 reads
Working with a QA server in SQL Server 2000 is something everyone should learn to do. Having some staging area between development and production will help ensure a more stable environment and smoother deployments. After a little hiatus, Steve Jones continues with this series looking at moving the latest backup over to QA.
2004-09-29
6,561 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