Eduardo Pivaral

SQL Server Database Administrator/Developer with experience in large environments.
I have worked on IT for nearly 15 years in different areas.

Microsoft Certified Solutions Associate: SQL 2016 Database Administration since 2018.
Microsoft Certified Solutions Associate: SQL Server 2012/2014 since 2017.
Microsoft Certified Professional since 2014.

Install Python on Windows

Python is the most famous development language today.
This is because is open-source, scalable and robust. It can run in almost any device with a processor (or microprocessor, we will...

2021-01-21 (first published: )

871 reads

Blogs

Whiling away an afternoon, thinking

By

I come to Heathrow often. Today is likely somewhere close to 60 trips to...

Black Box vs. Gray Box vs. White Box Testing

By

If your organization is spending money, then meaningful results are a must. Pen testing...

Webinar Series – SQL Server Indexing

By

I’m starting a webinar series about SQL Server indexing with the fine folks of...

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