|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL 2000 Std on Win 2003 Std R2 x64 bit?for memory - 4GB acts as a backup for the other 4GB RAM). The server has Dual Quad Core CPU's in it also. We run SQL 2000 Std with CPU licenses and I've limited SQL to 1.7GB RAM because the server is also a File/Domain Controller - Windows 2003 Std x32. I was wondering about the implications of moving to Win 2003 Std R2 x64 to be able to use the 8GB RAM and how, with SQL limited to being able to only access 2GB RAM normally, would the server benefit (SQL being the primary question) from switching to Win 2003 Std R2 X64 so that I could actually use the enture 8GB RAM (would take it out of fail over mode)? TIA. -- Leythos - Igitur qui desiderat pacem, praeparet bellum. - Calling an illegal alien an "undocumented worker" is like calling a drug dealer an "unlicensed pharmacist" spam999free@rrohio.com (remove 999 for proper email address) Leythos,
The only benefit I would see is that if you run a 64-bit O/S you don't need to format to move from 32-bit software (SQL) to 64-bit software. 32-bit SQL server will not use the extra memory. You cannot upgrade 32-bit O/S to 64-bit O/S. Chris Show quote "Leythos" <v***@nowhere.lan> wrote in message news:MPG.21b09b3e37a870e198983f@Adfree.usenet.com... >I have a IBM 3800 server with 8GB RAM (currently setup in Fail Over mode > for memory - 4GB acts as a backup for the other 4GB RAM). The server has > Dual Quad Core CPU's in it also. > > We run SQL 2000 Std with CPU licenses and I've limited SQL to 1.7GB RAM > because the server is also a File/Domain Controller - Windows 2003 Std > x32. > > I was wondering about the implications of moving to Win 2003 Std R2 x64 > to be able to use the 8GB RAM and how, with SQL limited to being able to > only access 2GB RAM normally, would the server benefit (SQL being the > primary question) from switching to Win 2003 Std R2 X64 so that I could > actually use the enture 8GB RAM (would take it out of fail over mode)? > > TIA. > > -- > > Leythos > - Igitur qui desiderat pacem, praeparet bellum. > - Calling an illegal alien an "undocumented worker" is like calling a > drug dealer an "unlicensed pharmacist" > spam999free@rrohio.com (remove 999 for proper email address) In article <OTMPqKeLIHA.4***@TK2MSFTNGP06.phx.gbl>,
anonym***@microsoft.com says... > Leythos, LOL, that was going to be my next question, since we have Open Licenses > > The only benefit I would see is that if you run a 64-bit O/S you don't need > to format to move from 32-bit software (SQL) to 64-bit software. 32-bit SQL > server will not use the extra memory. You cannot upgrade 32-bit O/S to > 64-bit O/S. with SA, if we could to an upgrade to Win 2003 64 and not have to wipe/reinstall. I actually bought SQL 2005 with 2 CPU licenses, but the application won't run properly with SQL 2005, so we downgraded to SQL 2000 and are stuck with it for a while. -- Leythos - Igitur qui desiderat pacem, praeparet bellum. - Calling an illegal alien an "undocumented worker" is like calling a drug dealer an "unlicensed pharmacist" spam999free@rrohio.com (remove 999 for proper email address) SQL 2000 sp4 can benefit from x64. Each instance can use a full 4GB. This
can be useful if you have proc cache or memtoleave issues. Even if it is just data pages, there is less overhead to thunk than hit AWE. Jason Massie www: http://statisticsio.com rss: http://statisticsio.com/Home/tabid/36/rssid/1/Default.aspx Show quote "Leythos" <v***@nowhere.lan> wrote in message news:MPG.21b0fe461cbf2aa6989841@Adfree.usenet.com... > In article <OTMPqKeLIHA.4***@TK2MSFTNGP06.phx.gbl>, > anonym***@microsoft.com says... >> Leythos, >> >> The only benefit I would see is that if you run a 64-bit O/S you don't >> need >> to format to move from 32-bit software (SQL) to 64-bit software. 32-bit >> SQL >> server will not use the extra memory. You cannot upgrade 32-bit O/S to >> 64-bit O/S. > > LOL, that was going to be my next question, since we have Open Licenses > with SA, if we could to an upgrade to Win 2003 64 and not have to > wipe/reinstall. I actually bought SQL 2005 with 2 CPU licenses, but the > application won't run properly with SQL 2005, so we downgraded to SQL > 2000 and are stuck with it for a while. > > -- > > Leythos > - Igitur qui desiderat pacem, praeparet bellum. > - Calling an illegal alien an "undocumented worker" is like calling a > drug dealer an "unlicensed pharmacist" > spam999free@rrohio.com (remove 999 for proper email address)  |
|||||||||||||||||||||||
Other interesting topics