Upgrade from SQL 6.5 to SQL 2k 1

[lpedde]

We have been running SQL 6.5, VB6 and Crystal Reports 7 on an NT4 server.
We just purchased a Win 2003 server. I understand that I have to upgrade to SQL 2000 with SP3.
Does any one know if VB6 and Crystal Reports 7 play nicely with SQL 2000?
Are there any major issues that I need to be aware of when upgrading the SQL?
Thanks,
Linda

 

[JayKusch]

I know they "play" nicely BUT You may still have some conversion issues w/ maybe some stored procs, table definitions and such going from SQL Server 6.6 to SS2K.

Thanks

J. Kusch

 

[RobertT687]

My two cents worth.
You MAY run into issues in stored procedures, views etc. depending on the compatability level you set for the SQL2K server.
After I upgraded a v6.5 db to v7.0 and set the compatability level to 7.0, several stored procedures and views stopped working because I had used double quotes around strings instead of single quotes. This worked fine on v6.5 itself and on v7.0 with a compatability level of 6.5. I think SQL2K has the same issue. Haven't gone directly from 6.5 to 2K so I can't say for sure.

 

[itsp1965]

Apparently the upgrade from SQL 6.5 to 2K is a lot more seamless than going from 6.5 to 7.0. Quote from a course I took recently
1. Verify user connections parameter in sp_configure has a run time value of 25
2. As always backup your databases
3. Run DBCC checks on your DBs
4. Make sure that the temp DB is at 10MB
5. All startup stored procs should be disabled
6. Stop replication services and empty out the replication log.
7. Of course have SQL 6.5 SP5 installed

When you begin the upgrade process through the wizard, select both the Validate successful object data transfer and the Exhaustive data integrity verification check boxes.

Now I haven't tried this myself but you can always try this in a test environment first. Hope this helps.