2004-04-26
2,220 reads
2004-04-26
2,220 reads
2004-04-23
1,779 reads
2004-04-22
1,985 reads
2004-04-21
1,737 reads
2004-04-20
1,577 reads
2004-04-19
1,523 reads
2004-04-16
1,411 reads
Are you a new SQL Server administrator? A network admin or developer who got the responsibility for a SQL Server dropped on your head? Steve Jones starts a new series looking at a few of the things that you might want to know if you've never worked with SQL Server before.
2004-04-15
19,756 reads
2004-04-14
1,723 reads
2004-04-13
2,159 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