Jason Brimhall

All authors

Blog Post

Top 10 Recommended Books…

So the title says it all, right?  Well, only really partially. Recently an article was published listing the top 10 most recommended books for SQL Server.  That’s the part...

2014-07-29

5 reads

Blog Post

Murder In Denver

I am about to set sail on a new venture with my next official whistle stop.  This year has been plenty full of whistle stops and I plan on...

2014-07-14

4 reads

Blog Post

The SQL Sac wrap!!

Every SQL Saturday leaves a mark of some sort.  This time around, the folks in Sacramento have really helped leave a BIG mark. That’s right, this last weekend was...

2014-07-14

3 reads

All authors

Blogs

TempDB Internals – What’s New (SQL Server 2016 to 2022)

By

I wrote about TempDB Internals and understand that Tempdb plays very important role on...

Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI

By

continuing from Day 1 where we covered the history of AI and GPT family,...

A Wellbeing Day at Redgate

By

It’s a day off for Redgate today. This is our annual wellbeing day, where...

Read the latest Blogs

Forums

adage acting funny

By stan

Hi, i know this is a shot in the dark.  i dont know what...

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By Terry Jago

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code: 

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers