As what seems like the only vendor to not chime in yet, I'll throw my hat in. I work for Quest, and given the requirements you've laid out (server...

Build 9.00.1399.x of SQL Server 2005 is the RTM build (no service pack). You need to upgrade to build number 9.00.3042 (I recommend at least 9.00.3050) which will put...

When you restore a database WITH NORECOVERY the database is not accessible until you finish the restore sequence WITH RECOVERY.

You must complete the final diff or log restore WITH RECOVERY...

Backing up every table in a database is equivalent to a full database backup.

If you are looking to backup only a few tables and not the whole database...

If restarting the SQL Agent causes the problem to go away, your load is most likely coming from a scheduled SQL Server Agent job. When CPU is at 100%...

You should definitely either compress the backup file using any standard zip utility or one of the many 3rd party backup products.

In addition to this you can try backing up...

INIT only works when backups have the same name. Using the INIT flag simply deletes the previous backup before writing to the file (as long as the names are...

If you only want 5 decimal places to show up you can use the following as your format string.

#.#####

The pound sign indicates that only 5 numbers should be shown after...

Do you know how the debugger handles temporary tables and/or table variables. Can you watch the contents of these table objects while a script is debugging and monitor their...

You should check the properties of the datasource. Most likely the credentials for the datasource are not stored on the report server. In report manager, find the datasource...

Also make sure you close out of SSMS while connecting with SQLCMD.

Changing the compatibility level will not work.  There is no way to restore a SQL 2005 backup to a SQL 2000 server.

The account that you connect to SQL Server with is irrelevant.  The account that needs access to the network resource is the account that is running SQL Server. 

You can...

Here you go:

USE master

BACKUP DATABASE northwind TO DISK='c:\northwind.bak'

RESTORE DATABASE northwind_new FROM DISK='c:\northwind.bak' WITH MOVE 'logical data file name' TO 'new physical file name', WITH MOVE 'logical log name' TO 'physical...

Your best bet is to restore the database to a SQL Server 2005 server and then use the copy database utility in Management Studio to copy the database to a...