I think I wasn't clear. The initial question relates to upgrading the operating system from 2003 R2 Standard to 2003 R2 Enterprise, both 32-bit. The application will not run on 64-bit OS or SQL, per the publisher.
Phil From: Ziots, Edward [mailto:ezi...@lifespan.org] Sent: Thursday, February 24, 2011 9:47 AM To: NT System Admin Issues Subject: RE: 2003 R2 32-bit Std Edition Memory On SQL 2005? I know you can go for SQL 2008 Standard to Enterprise, In place. I do agree with slow queries are probably inefficient queries, Table scans, etc etc. Usually some work with Profiler, and Best practice analyzer, and looking at query plans for the batches that are sent to the server, are in order, before upgrading in to Enterprise Edition. Also DBCC MemoryStatus will tell you about what the memory specified on the server is doing. But I believe 4GB is the limit on 32bit Standard R2 edition, which is why we always did Enterprise Edition R2 (32bit) with SQL 2005 Standard and Enterprise, so we could go up to 32GB of RAM. Also you don't need to use PAE switch on X64bit systems. Z Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:ezi...@lifespan.org Cell:401-639-3505 From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Thursday, February 24, 2011 11:59 AM To: NT System Admin Issues Subject: RE: 2003 R2 32-bit Std Edition Memory You can upgrade in-place to enterprise edition. In almost every case, a properly tuned SQL 2005 database will run rings around a SQL 2000 database. Before you spend USD $3000 on an upgrade, you might should spend a little time with "DBCC UPDATE STATISTICS" and with SQL Profiler. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Phil Hershey [mailto:phers...@agia.com] Sent: Thursday, February 24, 2011 11:52 AM To: NT System Admin Issues Subject: 2003 R2 32-bit Std Edition Memory Is the limit for the 32-bit OS 32 GB on x64 processors with PAE enabled? (Been too long since I had to think about this.) We have internal applications that have been moved from an old Server 2000 system with SQL 2000 to a brand new HP G7 server with Server 2003 R2 32-bit (application won't run on 64-bit OS or Server 2008). Now that it's on the new hardware, OS and SQL 2005, the queries are super slow and timing out. Can you upgrade in place from Std Edition to Enterprise? Any ideas? J ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
