The SQL Server Community
I attended, and spoke at, the inaugural meeting of the Seacoast SQL Server User’s group last night. There were about...
2010-04-14
915 reads
I attended, and spoke at, the inaugural meeting of the Seacoast SQL Server User’s group last night. There were about...
2010-04-14
915 reads
Tomorrow, Wednesday April 14th, is the next SNESSUG meeting. We’re going to get a great presentation from Scott Abrants on...
2010-04-13
740 reads
Tomorrow is the Seacost SQL Server User’s Group inaugural meeting. I’ll be presenting a session called “Understanding Execution Plans.” It’s...
2010-04-12
735 reads
I’ve posted before about issues I’m having either with behaviors of nHibernate, or behaviors of teams using nHibernate, but I...
2010-04-09
971 reads
The kids over at the Professional Association of SQL Server Users have done it again. They’re hosting 24 Hours of...
2010-04-06
712 reads
One of the national sponsors for SQL Satuday is Confio Software. Just because they sponsor SQL Saturday, it’s worth checking out their...
2010-04-06
2,810 reads
I’ve blogged in the past about the nHibernate project that has been going on at my company for the last...
2010-04-05
1,017 reads
I received my renewal notice and, after checking the message header, it is April 1st, I got very happy. I’d...
2010-04-01
511 reads
New York, New York, it’s a hell of a town. The Bronx is up and the Battery’s down. The people...
2010-03-23
553 reads
One of my development teams needed a mechanism for identifying the value of a key that was part of a...
2010-03-18
4,668 reads
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
I’m starting a webinar series about SQL Server indexing with the fine folks of...
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