2019-11-22
1,038 reads
2019-11-22
1,038 reads
2019-11-21
758 reads
2019-11-21
125 reads
2019-11-20
593 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. Recently I was testing some security change, and...
2019-11-20
118 reads
The period after a conference is a good time to start driving yourself forward.
2019-11-20
131 reads
2019-11-19
417 reads
2019-11-18
229 reads
2019-11-18
1,250 reads
Steve ends his week of career thoughts with a look at the job descriptions that we often use to decide if we want to apply for a job.
2019-11-15
278 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