I would suggest run reindex job(s) on wknd basis. You can start implemening that by creating a table which list your table names and subsequent indexes. And then, when scandensity falls...

You may want to buy SQL LiteSpeed. You will gain not only space, but also time...

You could start with (others will add; also you could search forum for that topic)

1.  SQL Error Logs

2.  Event Logs

3.  Failed Jobs

4.  Perfmon (Review Log Perfmon output if...

How about Union....

If space permits, I would suggest creating multiple Tempdb files, say 4x4GB , on a separate disk, of an equal size and disable autogrowth for datafile...

To add up to the above. If you have a single table of a huge size, you might need to increase the size of a temp db to fit it in.

I used it few times (DBCC REBUILD_LOG) and it worked for me

You didn't experience any space issues with that server....

In my test environment I was able to restore SQL Server 2000 Database (2 gb) on SQL Server 2005...

You can do it by using DBCC REBUILD_LOG

running "worst performing queries, traces and batches" can be an overkill for the busy production server, since SQLDIAG is running traces on a target server. The good part that you can...

shot in a dark. Do you have an Identity column? If not-try to add to your table...

I am thinking about getting Idera SQl Diag for certain servers. Nice tool, but on a busy server it looks like it creates some overhead ( by running server traces)

Do you run any batch jobs at this time?

Do you run DBCC Check DB or other maint jobs at this time?

What is the size of your Database?

How many total\concurrent...

What Rudy was saying above is the following:

Declare all variables, encompass the code in stored procedure and run it as job regularly on your master server.

The above code you can...