2020-03-12
597 reads
2020-03-12
597 reads
2020-03-11
648 reads
Steve Jones highlights the importance he sees for data professionals in the containerization of software.
2020-03-11
293 reads
2020-03-10
337 reads
2020-03-10
888 reads
Today is T-SQL Tuesday #124 and I’m dropping a quick post as I’ve had lots of other stuff to do since returning from my sabbatical. Tracy Boggiano is the...
2020-03-10
118 reads
2020-03-09
639 reads
2020-03-06
703 reads
I deliberately didn’t set any goals at the start of 2020 since I was taking six weeks off for a sabbatical. That’s done, and it’s time to look forward....
2020-03-06 (first published: 2020-03-02)
478 reads
Today Steve asks what reasons a developer has for using stored procedures.
2020-03-06
541 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