As for your performance problem (and please in future post different questions in different threads), can you please post the actual execution plan. What you posted was an estimated and...

No useful information in that.

Edit the job, go to the job step, the advanced tab and configure an output file. If the job fails again, look in the output...

Kill no.

As for how it works, it would take a few pages to explain, so maybe have a read through the entries in BoL (there's a load of information)...

No such things as global variables.

Use the task space usage and session space usage DMVs to identify what's using lots of TempDB and tune the queries so that they don't...

Look into using resource governor (not query governor), if you just kill sessions there's a fair chance that the people running them swear, curse and rerun the queries.

Be careful, filegroup backups require that you do have backups of all the filegroups that you intend to restore (and I'm not talking about a dev refresh, more a disaster...

A full backup is always a full backup of the entire DB. You can do things like filegroup backups and have the CDC tables in another filegroup, but that complicated...

There's a script in the first article that Igor linked, just take the part to create a new partition and ignore the part to switch and merge the partitions since...

Create a job that runs every year and splits a new partition. It's the same as the sliding window except you're only doing the split partition half, not the switch...

Case gives you table/index scans. Very consistent performance, but not good performance once you get to tables with more than a couple hundred rows. The OR method can use index...

http://sqlinthewild.co.za/index.php/2009/03/19/catch-all-queries/

You're looking for the function datediff, however it'll overflow for a value that far back as datediff returns an int and 1900/01/01 is more than MAXINT seconds ago.

This works.

SELECT CAST(datediff(hour,'1900/01/01',GETDATE())...

Can you be a bit clearer what you want?

Kill all the queries that have been running for 2 hours and have been blocking other queries for 2 hours?

Kill all the...

The index isn't covering and doesn't even support most of the where clause. Unless a very, very, very, very small portion of the table qualifies for that filtered index, it's...

Please note: 4 year old thread.