Chris Yates

Chris Yates is a Database Administration Manager with over thirteen years of experience in the SQL industry. His experience includes design and implementation of both OLTP and OLAP solutions as well as assessment and implementation of SQL Server environments for best practices, performance, and high availability solutions accompanied by a strong development background. He enjoys helping others in the SQL Server community and does this by contributing on several SQL forums, creating “The SQL Professor”, and speaking at several SQL functions. His passion and focus is not only with technology but also helping others along their way and career path.

All authors

All authors

Blogs

Blog a Day – Day 1: History of AI

By

it has been a year since i have not written much on the blog...

A New Word: on tenderhooks

By

on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...

Ramblings about data communities and your contributions, no excuses

By

I have been active in the data community throughout my career. I have met...

Read the latest Blogs

Forums

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 tedo

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

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

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