It's there, but not as an option. If you are setting up a Maintenance Plan in 2005 you have to setup a Maintenance Cleanup Task.

This provides the ability to delete...

Just a guess here, but I suspect that the xp that SQL 2005 is calling is nowhere to be found in a SQL 2000 installation.

Try running a TSQL backup job...

As was stated previously, it appears that your backup is corrupt. Most likely by transferring the file via FTP in Text mode rather than Binary mode.

However, it could just flat...

Okay, all that automated scripting is great, but it assumes that you're msdb is fully intact and that the backups were made on the Server where the generation scripts are...

Technically, you can't. However, you can write a series of T-SQL commands...

Steve,

I was correct the first time, in this case. Gail further explained.

As long as the following do not occur, you are in the clear :cool::

1) The Recovery Model is changed...

I had this all sorted out in my head before reading the whole chain thing in the article. I understand the concept of chaining, but it was the portion that...

Gail,

That's how I thought it worked, but after reading the Microsoft MSDN for 2005 I was not sure

A continuous sequence of log backups is called a log chain. A log...

Well, I stand corrected.

Clearly I was incorrect given the information in the Microsoft Article (http://msdn.microsoft.com/en-us/library/ms190440.aspx).

I thought that the chain continued regardless of whether you took a Full backup...

Jim,

I understand what you are talking about. It's never fun to break new ground when it comes to DR. Of course, since you are the new DBA this affords you...

No.

A full backup is similar to a snapshot, it's point in time. You could take a full backup 4 or 5 times a day and still use Transaction Logs...

Monitoring is a good idea, of course. However, asking your end users to modify their practices is akin to extracting milk from granite. If the monitoring yields some deficiencies, then...

Reclaiming disk space by shrinking logs I think is okay. However, if Transaction Log backups are being taken frequently enough, that should stave off any unusual file growth.

Mike,

Yes, you make a valid point. Using a "quality" Network Interface that implements NDIS 6 correctly may be another approach. However, for the millions of Servers out there running various...

C:\ Drive - OS only (mirrored)

D:\ Drive - Applications, including SQL Server

E:\ Drive - Log files (RAID 5)

F:\ Drive - Data files (RAID 5)

G:\ Drive - tempdb database

H:\ Drive -...