Here's an example of a forum with it. They show a paragraph or so. The only bad thing is that it only displays for 5 seconds or so. It should...

Our DB is only 300 G, but we use Idera and backup to a local RAID 0 drive for performance, then put that to tape.

I think you're the first person who has anything positive to say about "in-place" upgrade. Perhaps it depends on the environment ... some installations are more suited to it, and...

Thanks for all the feedback !

I think I'll make a test instance of SQL 2000, copy over a backup of our big Prod database to test with, and run the...

Thanks for all the feedback

What went wrong ?

" ... If you upgrade in place, some of the configuration tools do not work.  My guess is they expect a file format in the SQL 2005 format of \MSSQL.n\,...

A 30 Gig log file is huge !  Why don't you shrink the log file first.

I hadn't considered uninstalling SQL 2000 prior to installing 2005. If so, 2005 would have the same default instance name that 2000 had, so I wouldn't have connectivity issues with...

The articles & documentation make it sound as though upgrade in place is the thing to do ....    Why is it such a bad idea ?? 

If I install a...

Currently, I have 300 Gig for the Developement DB, and another 300 Gig for a copy of the Developement DB, but I don't have any more than that.

"..... Always side by side upgrade is best approach... "

I had been reading that the "Upgrade" was the easiest method, not side by side migration, because all your setting, logins,...

You can try:

sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1 

That's what I've done, but to solve a slightly differnt problem. I...

Most tables could be copied via linked server, but a few were getting an OLEDB error.

The problem ended up being that there were triggers on the target tables. I had to...

You might get better feedback if you post in one of the SQL subfolders instead of the Notification Services area.