2004-05-11
1,546 reads
2004-05-11
1,546 reads
2004-05-10
2,036 reads
2004-05-07
1,529 reads
2004-05-06
1,872 reads
2004-05-05
1,762 reads
2004-05-04
2,158 reads
2004-05-03
1,834 reads
2004-04-30
1,553 reads
2004-04-29
1,914 reads
It's been some time and he apologizes. This next part of this series from Steve Jones looks at selective auditing changes to data on the server using a combination of methods presented in previous articles in the series. Read on if you have problems tracking changes to data on some tables, but don't want to implement a solution that tracks every change.
2004-04-28
12,821 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...
I’m starting a webinar series about SQL Server indexing with the fine folks of...
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