sql server 2k on win2000 in development and sql 2K on win 2003 in production?

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

    We are migrating our production SQl Server from Windows 2000 to Windows 2003. There is a debate wether our Development Sql server needs to be migrated as well. Does any one know of compatibility issues when we develop against sql 2000 on Win2000 and then deploy in production to SQL Server on win2003? I would also be interested in any potential issues with Sql 2005 (having development database on win2000 and production database on windows 2003)
  • Not only would I recommend upgrading the dev server, I would actually do that first and test whether there are any issues with your existing code. If there are any issues with a new OS (or SP, or patch) then you want to find out about them on your test kit, not in the live environment. Not all issues may be documented in knowledge base articles. We install and test any upgrades on a like-for-like copy of our production system before rolling it out to live.

  • If you upgrade your production environment to W2003 before you upgrade Dev, you are asking for downtime.

    We had some application coding issues when we upgraded, but these got found and fixed in Dev.  Depending on your use of SQL Server features, you may need to allow the service account to have the 'Impersonate client after authentication' right in W2003.  This is not in BOL but is in a KB.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • the network admin where I work wants to migrate our sql server from win2k to windows 2003 as well.  I'm just wondering, what kind of coding issues did you experience from doing this?

  • eDvASSIVE,

    What coding problems are you experiencing?

  • There were some MDAC issues, as W2003 MDAC is at a higher level than we were migrating from.  There were also some problems with a few apps moving from VB6 to .Net, but we were not surprised about this.  Because we upgraded Dev first, all these problems were trapped and fixed before UAT.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply