"SQL Server 97" ???

How about running QA with the following:

select @@version

Just remember to schedule a failover/failback to test it (you wouldn't want to find out at 3:00 AM on a Sunday morning that is did not take !)

I guess I have to install v6.0 and v6.5 on servers along with v7.0 ...

UNC file naming is the way to go from xp_cmdshell. Just make sure that the SQL Server service account has access if you are running from QA. If it's a...

Three things matter most overall. Database size and the type of disks you are using and whether o not your backupos go directly to tape or disk. First off, backups to...

Separation is another key point. Database data, Transaction Log(s) and Backups need to be on their own distinct LUNs/Mets-LUNs. Separation of database Data and Log is SQL 102.

I'm not familiar with EVA but I've worked extensively with Hitachi and EMC SAN and SQL Server. The underlying arrays are important but not paramount (RAID 5, 1+0, 1 more...

Have you considered the use of an 'MSX' server ? It can handle scheduling and execution (along with error reporting) for all 'enlisted' servers.

Also, if you are using a domain\username account for the SQL Agent service you might want to check in SQL Server that it is a valid account and has sysadmin...

Another option might me to utilize a reverse engeneering tool in a database design product like ErWin or PowerDesigner. Products such as these could take a rather large database and then tell...

Have you looked at the SQL Server error log ? The Windows System/Application/Security event logs ? They may provide more information. The spectrum of potential problems is just too large...

My rule of thumb is 1 and 1 for databases under 100-200 Gb. After that, it all depends ... on size, storage, activity, application availability ...

I do not know if this SQL2K extended stored priocedure exists in v7.0:

master..xp_readerrorlog

Have you checked the accounts used for executing the services on both servers (mainly the 2K3 server) to make sure that they have the proper permissions ? Just a thought...

I've had varying success with Maintenance Plans on MSDE. Some of them just do not work. While others save the plan but are missing parameters on the SQL JOB. Try...