Kurt W. Zimmerman (10/29/2013)

---

I ran into this very same problem a number of years ago. I was managing a database on a hosted/managed service. Turned out that the...

You have a disconnected differential and full backup. Some other process is running full backups between the time you ran yours and you ran the differential. You won't be able...

Assuming you're monitoring your servers, you know that server X is under some stress for CPU and this new app looks like it might have lots of recompiles, so it...

Steph Locke (10/28/2013)

---

I think that unless a certain dresscode is required, dressing in a suit to an interview is a pretty much an ironclad prerequisite, and people who don't adhere...

Oops. My bad. I typed it from memory. No quotes around the d. You can look up more about DATEADD here.

I don't know of a specific resource.

A lot of people are scared (semi-justified) of data deduplication. It's a somewhat new technology and it can be a little sketchy, but...

You've got the function in place, but it's not comparing it to anything. That's why you're getting an error. Assuming you want exactly 30 days ago, you can do this;

SELECT...

FROM...

WHERE...

Assuming you're running on 2008 since this is a forum for that, I don't recommend trace. Instead, use extended events. The events to capture queries against the database are rpc_completed...

The compression for the backup will occur within SQL Server, so there's no issue there. I'll bet you don't get any additional compression on the drive since the file will...

I've never tried creating a plan guide for a system procedure. I'm not sure it will work.

But, the error suggests you might not be trying to create it in the...

Yeah, if you create a temporary table as a local temp table, using #temptablename, it's only for the connection using it. You can create a global temporary table using ##temptablename...

Check out my sig for a book on reading execution plans. You can even download it for free.

I'm pretty sure the differences are in how the query is dealing with the DISTINCT statement. Look at the execution plan to see how that is resolving itself.

Since DISTINCT is...

I'm with Gail. I can't think of anything that would lead me to regularly restart the instance because of something within TEMPDB.

From a core behavior stand point, there's no real difference between the two. Both are basically just deallocating the resource. But, you then have to go back and recreate the...