2006-01-13
1,051 reads
2006-01-13
1,051 reads
I decided to commit to the book, so I'm waiting on some information and a contact from my co-author and...
2006-01-12
1,458 reads
2006-01-12
1,229 reads
2006-01-11
1,733 reads
2006-01-10
1,142 reads
2006-01-09
1,833 reads
Writing outer joins can be more difficult than it appears at first glance. Steve Jones examines this less often used query technique and brings to light a few places where you can lose data.
2006-01-05
18,606 reads
I'm getting ready to look for a new cell phone and I got lots of suggestions from my editorial on...
2006-01-05
1,525 reads
That's the decision to be made.
Apress contacted me about the update for my book. I wrote 1/2 of the Designing...
2006-01-05
1,496 reads
2006-01-04
1,219 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
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