Thanks, Brian and Dan. I think I'll take the leap!

Thanks Viacoboni, that looks great! I especially like your point about SQL Backup error detection. I found some code on the Red Gate site that helps with this, but your's...

We recently ran tests of SQL Litespeed, SQL Safe, and SQL Backup. I found minimal differences with compression and performance of the 3 products. I could not find any justification...

No luck getting this to output. Eventually got everything to run, but email output simply reads: THETEXT

If you're referring to T-logs on the subscriber dbs, you might want to think about setting recovery mode on those dbs to "simple".

You can also get it from EM.  Right click the instance - Properties - Network Configuration - TCP/IP - Properties.

You could start here...

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#XSLTsection126121120120

Good luck!

If your hardware has "hot-add" memory, I don't think you need either switch - just AWE.

We can't use it on most of our production servers because of the problem with AWE.

We usually don't rush to install SPs.

If you have identity columns, they don't replicate, so I don't think you can use replication as a fail over instance. You'd have to use log shipping or clustering.

From MSDN:

On 32-bit versions of Windows, PAE is disabled by default. You must use the /pae boot parameter to enable PAE.

However, PAE is automatically enabled when the computer is...

You'll then have an Active-Active cluster.

If it's a large text file, you may have to change the 'max text repl size'.

My bad. You're right, the first script is best. My test db was restored from last night's backup after today's updates were applied.

Thanks

Thanks Greg. I tried that, but it doesn't work.

select * from table

where DBDate between '01/28/2005' and '01/29/2005'

Doesn't return any records.

If I change it to:

select * from table

where DBDate...