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...

For just learning PowerShell, I'd suggest Don Jones book, PowerShell in a Month of Lunches. It'll give you most of what you need to learn it.

The EPM does all the work for you. But the other stuff is documented on Microsoft. It's very easy. Yes, for more complete direct control you'll do PowerShell scripting, but...

Just don't ever forget that all these types of tables from table variables, multi-statement UDF and table parameters, all of them lack statistics which can seriously, negatively, impact performance.

Sure. It's a part of PBM. You can make calls from Agent. Keep reading in the documentation. PBM is great.

All databases must have a transaction log, even on SQL Server 2000. Are you trying to remove a log file you are no longer using, but there will still be...