2006-12-06
1,316 reads
2006-12-06
1,316 reads
2006-12-05
1,041 reads
2006-12-04
2,146 reads
2006-12-01
1,317 reads
2006-11-30
1,276 reads
2006-11-29
823 reads
2006-11-28
954 reads
2006-11-27
981 reads
2006-11-24
905 reads
Data space can be a concern in many situations as more and more data is being stored in your systems. Designing your schema to take this into account is important for a DBA and Steve Jones takes a look at how design decisions can be used to solve a business problem.
2006-11-23
5,744 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