2023-09-25
469 reads
2023-09-25
469 reads
Do you actively choose which compatibility level makes sense for your SQL Server databases? Or do you just take the defaults? Steve has a few thoughts today on actively managing your system.
2023-06-14
1,758 reads
The database compatibility level ought to provide some protection from database upgrade changes, but do you believe that?
2020-09-21
330 reads
2015-10-19
1,334 reads
Changes the database compatibility level of all databases to the given level.
2013-01-31 (first published: 2013-01-07)
929 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