There is no way to ensure you have a relationally intact set of data by taking a backup.  This is because applications can continue to update the databases while the...

SQL Mail is not the most bug-free product that Microsoft have produced.  Even though it can work for weeks without trouble, it is not unusual for mail to stop working...

If you can get a RAM disk set up, you could put the log file on there.  If you do this, you may need to  reduce the checkpoint interval so...

The Windows Event Log could give you more details of why SQL will not start. 

If this does not help, add a startup parameter of -T3608 and try again.  (Search...

There are actually 2 reasons why Full recovery mode may be necessary.

1) To allow point in time recovery using transaction log backups.

2) Provide a full audit trail of all changes...

If sa24's idea does not work, copy and paste the code in sp_changedbowner into your own user sp.  Then locate the test for system databases and remove it.  Your amended...

This is by design.  Microsoft, in their infinite wisdom, added some code to the Agent startup process to set MSDB to simple recovery mode.  If you set up the right...

According to the Microsoft documantation, the /PAE switch is not needed in W2003 - it is effectively enabled as a default.

This means all you need to do is enable AWE...

Use DB2 or other DBMS (Yukon) that supports TIME as a datatype. 

You should be able to get SQL started. 

However, I would start to build this environment incrementally.  Start with a unclustered server at your primary and secondary, and debug all...

When SQL Server wants to expand any file, log or database, the operation can fail if the increment size is smaller than the space SQL needs to complete the active...

You should remove the -T3608 parameter when you are finished moving the system databases.  You will have to restart SQL after removing the parameter, as it affects the way SQL...

You should move Master via the SQL startup parameters.  Never try to detach Master, because if somehow it does succeed you will never get it back.

TempDB should only be moved...

It is not SQL that is taking the lock, it is the tape backup process.

If the success of tape backups is not properly checked, a failed backup may not get detected...

I have recently tried defragging a W2003 test server running SQL2K SP3a, while SQL was active and using the defrag tool supplied with W2003.

It worked.

Even so, I would not want...