Christian lives in Guatemala. He has worked with Databases for about 12 years, at the beginning as a software developer and for the last 10 years as DBA. His expertise areas are Database migration, Performance tuning, Security of SQL Server and Designing and Implementing HA and DR environments. He has worked with SQL Server since version 2000. Passionate about SQL Server, Azure and joining to the Online SQL Server community. You can always find him on Twitter (@charaujo).

All authors

All authors

Blogs

Building the Team: Roles and Responsibilities in FinOps

By

In my experience, FinOps success has never been just about tools or dashboards. It...

Tooling for Success: The Best FinOps Tools and Technologies

By

As a DevOps person, I know that to make FinOps successful, you need more...

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

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)
GO
Today, 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 REPLACE
What happens?

See possible answers