You are testing the application on a different type of server than production? One point for testing before deployment is to verify that the application works with no problems on the OS. Different types of servers will have different patches, service packs, etc. The system may work fine on one system and give you unexpected errors on another. Save yourself the headaches and keep your testing and production servers on the same type of OS.

We are not rushing to deploy SQL2005.

Are there any documented compatibility issues for SQl Server on win2000 VS. SQL Server on Win 2003? Any articles/references?

1st: if there are any, they should be documented on product's sites, i guess ... I don't believe one would know them all by heart. Someone could know some of them, but then ... that's not enough isn't it?

2nd: There still one way you could do this, I think. Test it first for something like a month long ... Then you decide. You could test by using a virtual machine for example. Or create a minilab to simulate the development environment (well, that might sound kind of weired anyway :))

3rd: Do not change working systems!!

Cheers.

Hi ftacoukj,

For what it is worth I haven't experienced or noticed any differences with SQL2K running on the two different OS's.  The only obvious issue is that you REQUIRE sp3a for win2003, if your development box is not patched to this level then it will need to be.  If you are running sp3a on both then I would say you do not need to worry about upgrading the w2k on the development box from a SQL point of view.

Do not upgrade the Windows 2000 to 2003.  Wipe it and start over.  Certain MDAC files relating to SQL Server processes get overlooked in the upgrade and a few things may not work correctly.  The one specific thing I can think of is BULK INSERT running in a job.  Job will report success, but the insert never happens.

HTH,
Kevin3NF

Can be closed

Cool....you need to close it out your self by clicking Accept, or Split points to share the points across mutiple answers...thanks