Going From SQL Server 2000 to 2005

It's been nightmarish and I need help fast!

Customers now have to buy 2005 and we've discovered that the migration isn't smooth.

I copied a 2005 and attached to it in 2005. Running under Windows XP Professional, I tried to run our application written in ColdFusion.

We discovered that a query fell over (seemingly) having to do with bit datatypes Error: 'Unspecified error occurred on SQL Server. Connection may have been terminated by the server.'), NULLs, or something. A programmer got around it, as a test, by converting all the bit fields in the table to int, which we naturally can't do as a real world solution.

I think upgrading the OS, including the ODBC driver SQL uses, applying Service Pack 1 as well as the B 9.0.2153 hot fixes, fixed that problem.

However a subsequent insert went from breaking with the above error message to break with "Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services." - that error refers to a fix for UNION which the query doesn't contain.

Lastly, when I went away from break, came back, and refreshed, I got the following error,"Cannot generate SSPI context". The application does have a timeout which previously under SQL 2000 would simply take them back to the login page. Nothing sort of rebooting my laptop allowed me back into the application.

This issues, and others no doubt lurking, strike me as something major and likely to affect a lot of people, but I have found nothing on the net about them.

I have run everything about compatibility I could find. Is it that few people are running SQL 2005 on dbs created in 2000

As far as I'm concerned, SQL 2005 is NOT ready for primetime.

Any solutions or ideas

Thank you.

Dan Keefer

Answer this question

Going From SQL Server 2000 to 2005

Chris Lovett
Have you ever checked your database for physical consistency by DBCC CHECKDB I received such message when my database had got corrupted (but it was MSSQL 2000).
Geeta Mudili
This db started out in 2000 and was restored under a new name and then attached in 2005. I just did run CHECKDB with no errors.

Dan
Going From SQL Server 2000 to 2005

Answer this question