Why I’m Excited About Hekaton
I recently readMicrosoft’s research paper on Hekaton, the new in-memory database engine in SQL Server 2014. When I first heard...
2013-10-22
2,339 reads
I recently readMicrosoft’s research paper on Hekaton, the new in-memory database engine in SQL Server 2014. When I first heard...
2013-10-22
2,339 reads
Partitioning is a feature that has been around since SQL Server 2005. It allows for users to split a table...
2013-10-12
2,654 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