September 15, 2008 at 6:32 am
Hi,
What version of Windows Server do I need to run SQL 2005 address 8GB + memory.
Can I install Windows Enterprise and run SQL 2005 Standard Edition?
Or do I have to spen extra money and go Win Enterprise and SQL Enterprise?
This will be used for our LIVE reporting Server (SSRS)
thanks,
September 15, 2008 at 8:14 am
Any edition of Windows that can handle 8GB of RAM is what you need.
You can run SQL enterprise on Windows standard. Not related.
September 15, 2008 at 8:21 am
Thanks, I was concerned about the 2GB memory restriction with Windows standard edition.
Ultimately, I want SQL 2005 to be able to address all the RAM in the machine.
September 15, 2008 at 8:21 am
Hi,
You may want to consider Windows x64 versions to future-proof your environment, as well as SQL Server 2005\2008 x64 edition. Windows x64 editions support higher memory configurations compared to 32-bit versions.
Thanks,
Phillip Cox
September 15, 2008 at 8:35 am
Phillip has a good idea. Assuming you're not using some of the things that don't work well with 64 bit (SQL Mail, etc.), looking at 64bit is a good idea. I'd honestly be looking to develop on 64 bit workstations then. Hate mixing environments.
September 15, 2008 at 8:43 am
Mixing environments has never sat well with me either. We do intend to use SQL Mail (or some better way to get notifications on data loads, backups and report jobs etc). So, I guess 32bit Enterprise for both WIN and SQL is the choice now.
64bit is way too much to convince the VP right now for Reporting server that has one in-house system approved so far. Other applications to be installed on it are purchased vendor applications.
September 15, 2008 at 10:30 am
Dana Bibeault (9/15/2008)
Can I install Windows Enterprise and run SQL 2005 Standard Edition?
that will be just fine, you'll need Enterprise edition of Windows server to address the extra RAM as Standard will only allow 4GB RAM. Anything over requires Ent and over 32GB requires Datacenter.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 15, 2008 at 11:32 am
Thank you for the confirmation.
September 15, 2008 at 1:26 pm
Dana Bibeault (9/15/2008)
Mixing environments has never sat well with me either. We do intend to use SQL Mail (or some better way to get notifications on data loads, backups and report jobs etc). So, I guess 32bit Enterprise for both WIN and SQL is the choice now....
You can send DB Mail from SQL 64-bit, just not SQL Mail (two different things). DB Mail is generally better at sending alerts and such anyway, so that's not an issue.
- 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
September 15, 2008 at 1:38 pm
also, SQL2005 is able to address as much RAM as the NOS will allow 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 16, 2008 at 7:09 am
Perry Whittle (9/15/2008)
also, SQL2005 is able to address as much RAM as the NOS will allow 😉
Depending on the edition of SQL Server, of course.
- 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
September 17, 2008 at 2:27 am
64-bit should be the default choice for new installations. If you think you need 32-bit you should justify why.
If you plan to install server hardware that supports more than 4GB memory (i.e. everything currently on the market!) the ROI is far better with 64-bit than with 32-bit.
If you have legacy applications that absolutely need 32-bit then fine, use it. If you do keep with 32-bit, then plan to install it as a guest server under Hyper-V or VMWare, etc. That way you can exploit the hardware to the full and still keep your old applications running.
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 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply