Known issues of upgrading from SQL 2000 to SQL 2005

We are looking at upgrading from SQL 2000 ent to SQL 2005 ent and was wondering if there are any known issues, hotfixes, and compatibility with code that was done in VB6. If any one has any information on what known issues are out there that would be great.

Should work fine. If you'd like to see a list of known issues/workarounds/notes/etc. for SQL 2005, go to the support.microsoft.com site and search for SQL Server 2005 articles. There are some considerations to take into account when migrating from 2000 to 2005, but those are more on the server side of things, not the client.

Obviously, there is no guarantee, but this is definately supported and being done elsewhere, so implement a sound testing plan prior to rollout and you should be good to go.

HTH

Key export: exception

Recently as part of the process of upgrading to RS SP2 I followed the
normal procedure to export my crypto keys. Unfortunately instead of
providing me with the key file, it gave me an "External component has
thrown an exception" message on the console. At the same time the RS
service shut itself down.
As it turns out, I already have the crypto key tucked away on a CD. I
went ahead and updated to RS SP2 successfully, but the key export is
still giving me trouble.
The trace log isn't doesn't appear to contain any error information.
Has anyone run into this before? How did you resolve it?I've googled and looked through the knowledgebase, but still haven't
found a solution to this.|||We also had this problem. The solution for us was to amend the
web.config file to <customErrors mode="Off"> (we were using a custom
error handler). If you have custom errors "On" then turn them off and
seeing what happens. It didn't fix the problem but it did give a
proper error page showing what the actual problem was and on what line
of code, etc. Good luck.