2025-08-27
197 reads
2025-08-27
197 reads
2025-08-25
370 reads
2025-08-25 (first published: 2025-08-11)
161 reads
rivener – n. a chilling hint of distance that creeps slowly into a relationship – beginning to notice them laugh a little less, look away a little more, explain...
2025-08-22
14 reads
2025-08-22
410 reads
This Friday Steve asks about what you're looking forward to in SQL Server 2025, if anything.
2025-08-22
118 reads
2025-08-20
490 reads
Asking for a raise is a scary event for many employees. Today Steve gives you a few things to think about and some advice on how to go about changing your job.
2025-08-20
98 reads
2025-08-18
441 reads
A customer was asking about how to track all the stored procedures that execute on their system. We have a section in Redgate Monitor that’s set to look at...
2025-08-18
17 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