I use a customized version of this MS code which is from the Pro SQL Server 2005 High Availability book. I like it because it verifies the databases are on...

The IDENTITY property behaves that way intentionally, to minimize blocking and deadlocking when trying to assign the next value in a sequence. If you're trying to maintain a consistent column...

BACKUP LOG with TRUNCATE_ONLY was deprecated in SQL 2008. To obtain the same functionality, you have to set the database to SIMPLE RECOVERY, CHECKPOINT and then put it back in...

A couple of things to add:

1. Here's a free tool you can use to aggregate the data for you: http://www.scalesql.com/cleartrace/. I use it to load my trace...

You should be able to reference the linked server to start the job on the remote server as long as the account you've created it with has sufficient privileges:

exec linkedserver.msdb.dbo.sp_start_job...

You should be able to use the fn_trace_gettable function to load data directly into a table.

I have an automated profiler trace that kicks off every morning and I use something...

For this, I would do a backup and a restore to get a full copy of each database on the second server.

The only "bad" that I can think of is that if you need to restore a backup of this database to another location, then that location would also need to...

That being the case, then I believe you need to be looking at log shipping or database mirroring instead. Transactional replication (assuming that's what you're using) is really meant to...

I'd also look at the option of selecting the data that you want to retain out, either into a BCP file or another table, then drop the original table, re-create...

Agree that duration is the best measure to use when performance tuning with two exceptions:

1.) If a process is being blocked, the duration reported will be a misleading representation...

Here's the link to an MS URL that explains how to do this: http://support.microsoft.com/kb/555128

But as Steve Jones indicated, I'm not sure it's a good idea to do this...

You should definitely run DBCC UPDATEUSAGE after upgrading from SQL 2000 to SQL 2005 and I'd also run sp_updatestats in each database, then include the databases in whatever your standard...

You can do it with a Visual Basic Script task. Here's an example of some code to get you started. It creates a new folder based on the current date.

...

One question I haven't seen asked in this post is "Are the log and data files on the same drive?". If they are, then in theory the log could be...