I'm pretty sure you'll need a 64 bit driver for mysql on the box that hosts the 64 bit SQL Server 2000 instance.

Then use the OLEDB provider on...

hkhaar,

It seems like you could have the .asp code post the data to the mysql server right after it posts to the SQL Server. Basically you'd have two db...

So you are trying to pull data from SQL Server ???? to mysql version? (Querying SQL Server from mysql?)

My bad, read and comprehend Jim, SQL Server 2000 64 bit.

If...

I think the problem is the memory or timeout setting in the DSN or the provider

Are you using a SQL Server login or a Windows Login. I've had trouble when mapping SQL Server Logins to Linked Servers, but the Windows Logins work well. ...

Tools->Options->Query Results->SQL Server->Results To Grid

Look for Maximum Characters Retrieved -> Non XML data

Change the value as you see fit.

Or if you're spitting the results to Text

Tools->Options->Query Results->SQL Server->Results To Text

Look...

Did the .mdf grow or the .ldf? If it was the log file, it was probably due to the transactions required to populate the new instance.

Just to make sure you get good data:

RIGHT(RTRIM(LTRIM(column_name)), 2)

With the previous example, you could have gotten a space instead of the desired two characters.

I've had the best luck with the Backup/Restore method for upgrading 2000 to 2005, it has proven to be the simplest and most reliable method from my experience.

There should be...

When you backup to a network share make sure you use a full UNC path to the target.

For example \\MyServerName\MyFolder\MySubFolder\MyBackupFile.BAK

Have you re-indexed, and / or updated the statistics? If not, it's worth a shot.

In any case, definitely push for a re-write with no cursors.

It sounds to me like you need to upgrade your SQL Server 2000 SP3 instance to SP4, run the instacat.sql file to update the system tables, and you should be...

I've done the SQL 2000 to SQL 2005 quite a few times, with a few different methods.

Copy Database Wizard, http://msdn2.microsoft.com/en-us/library/ms190775.aspx,

Detach / Attach, http://msdn2.microsoft.com/en-us/library/ms189625.aspx,...

Stay away from RAID 5 and SQL Server data, it would be better to have the SQL Server data on single drives with a good Full Recovery Mode backup strategy....

Mr. Moden and Gilamonster are correct.

I strongly suggest using sp_who and sp_who2, Activity Monitor, or SQL Server Profiler to see what is blocking.

Then look at the suspect...