32-bit SQL and 64-bit OS

  • Guys , I'd like to have your inputs. Our in-house web based application has a SQL back-end currently running on 32 bit SQL 2000 Enterprise / 32-bit Windows 2003 Enterprise. We will upgrade the app to current version; the current version will be 64-bit SQL 2008 Ent / 64-bit Windows 2008 Ent SP2. To bring the app to current version we need to do 5 separate upgrades:

  • upgrade 1: SQL 2005 required, 32-bit only
  • upgrade 2: same as upgrade 1
  • upgrade 3: 64-bit SQL 2005 is supported
  • upgrade 4: same as upgrade 3
  • upgrade 5: SQL 2008 required, both 32-bit and 64-bit are supported
  • The upgrades are not accumulated so we must complete one by one. My plan is to purchase a new server with 64-bit Windows 2008 server and:

  • upgrade 1:install 32-bit SQL 2005 on new 64-bit Windows 2008 server
  • upgrade 2 as normal
  • upgrade 3 as normal
  • upgrade 4 as normal
  • upgrade 5: install 64-bit SQL 2008 on the same server then remove SQL 2005 after the upgrade
  • My questions:

  • any known issue for having 32-bit SQL 2005 on 64-bit 2008 server as in upgrade 1?
  • any known issue for having 32-bit SQL 2005 and 64-bit SQL 2008 on the same server as in upgrade 5?
  • anything doesn't look right in my plan?
  • Thx

  • I haven't tried mixing them to that extent.

    Have you thought about running these in separate VMs or something like that?

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • GSquared (1/7/2011)


    I haven't tried mixing them to that extent.

    Have you thought about running these in separate VMs or something like that?

    VM is not supported by the vendor. The app is critical, we don't want to try something the vendor don't like 🙂

  • We went from a 32bit/32bit SQL 2000 environment last year to initially, a 32bit SQL /64 bit OS enviornment. It was not ideal. The server was constantly at 100% CPU and we were just getting poor performance all around. I did a little bit of research online and found a few articles that said SQL would not take advantage of available memory properly if the enviornment was 32/64. We worked with HP to try and see if we could fix the server and I messed around with sp_configure a lot trying to get the performance to come up but nothing worked.

    In the end we ended up reimaging the server and installing 64 bit SQL with the 64 bit OS. After that, it was purring like a kitten.

    So, I'm not sure if our problem really was the 32/64 or if the server was just a jacked install but putting it 64/64 did seem to help a lot.

  • I found this: http://www.sqlnewsgroups.net/sqlserver/t18795-32bit-sql-64bit-windows.aspx

    If Linchi has done it, you should be OK.

    Your plan should work, but I don't know that many people that have done it. Can I ask why not 64 bit SQL? The file formats are the same.

  • Steve Jones - SSC Editor (1/8/2011)


    I found this: http://www.sqlnewsgroups.net/sqlserver/t18795-32bit-sql-64bit-windows.aspx

    If Linchi has done it, you should be OK.

    Your plan should work, but I don't know that many people that have done it. Can I ask why not 64 bit SQL? The file formats are the same.

    I have no idea why they didn't support 64-bit SQL 2005 when they first required SQL 2005. The pain is the upgrades must be done one by one so we must do 5 long upgrades during the weekend. It is not just like we can do just 1 last upgrade to bring us to current.

  • Doing the upgrades one by one is fine. I would ask about 64bit and push a bit to get them to agree or give you concrete reasons. There were some things, like JET drivers, etc., but not many. If you can go all 64, I would.

  • I agree with Steve.

    You can do the upgrades one by one (do you remember the line 'You can live on it' in Crocodile Dundee?), but I would ask the vendor to give reasons why you cannot go direct to 64-bit SQL Server on your 64-bit OS. They should give real facts and figures, not just a general 'we recommend...' as a general recommendation probably means they simply don't know.

    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

  • thank guys for the input.

    I so far hit level 1 tech support. They just said that the version was tested only with 32-bit when released so they wanted us to use 32-bit for that version.

  • I think I might ask for a 64-bit test from then. The file formats, and many things are the same. Unless they have some 32 bit driver, it ought to work.

  • Viewing 10 posts - 1 through 9 (of 9 total)

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