I suspect an issue with an index. Are you running CHECKDB on here?

you definitely need logging for all packages as mentioned above. Job history doesn't give much info.

It's hard to lightly edit and help someone. It takes a lot of work. Most editors get fiarly heavy handed, pushing the work to be more standard and taking the...

Leave it to Jeff to come up with a solution. It's a good one as well.

You want to think pattern, working all rows at once from the pattern perspective, as...

Thanks, I assume the color codes mean something?

I'll see if I can get #s 1-4 up there.

sorry for the delay.

Absolutely, time for lunch. Right after I put my daughter to bed.

There's still some v65 and v7 servers out there running fine.

Gus,

Don't forget plenty of third party products, like SQL Backup, can give you compression, at a substantial savings over upgrading.

Good points on the tail wagging the dog, and I'd forgotten service packs can extend out support. I'm not sure you'll get a GDR for your SQL Server 2000 SP4...

I'd call MS support. Not sure anyone else can help you here.

Moved to SQL 2000.

It builds a package in Integration Services. You can save it and then open it up in BIDS.

What do you mean by getting killed?

Have you benchmarked? Any counters changed? Possible workload changes?

21GB might take some time to run up to 44GB. Can you run some larger queries...

datecreated on installation folder? (/binn)

I might also be sure that the spacing is there. If you might have more than one space, I'd consider using charindex/patindex to find the parens and go from there.

I'll add my reasons in here why I approved this question. I think it's good, and I see the arguments why log shipping might be seen a easy.

However, getting rights...