2021-11-12
468 reads
2021-11-12
468 reads
2021-11-05
504 reads
2021-10-18
387 reads
Sometimes just running a backup isn't enough, especially in this era of ransomware. Steve has a few thoughts on backup strategies and recovery skills.
2021-08-09
435 reads
2021-02-08
469 reads
Without a good backup and recovery strategy in place, a DBA should make sure their resume is always up to date. In this article, Greg Larsen discusses what should be considered when developing a backup plan.
2020-12-17
One of the most important responsibilities for a DBA is to ensure that a database can be restored in case of corruption, a dropped table, or another disaster. In this article, Greg Larsen explains the different types of backups available with SQL Server.
2020-12-01
2020-11-12
481 reads
Losing your instance might result in the need to get information from what you have. Steve Jones looks at a way to get the proper version and patch, and database list, from what limited resources you might have.
2020-10-27
2,579 reads
2020-10-13
415 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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