| Author |
Topic |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
 Posted - 2005-10-06 : 12:26:15
|
Don't flame me for posting this because I'm sure its been answered somewhere in the forums.  I'm just not good at searching. We have a SQL Server 2000 Ent Edt server set up on Windows 2003 Std Edt with 4GB of RAM. I found this quote on the Microsoft KB website. Are they saying that I can or cannot use /3GB on the SQL Server? At the moment the server is has a 1.5GB of RAM free. The SQL service is only using 2GB. Can I safely configure it with /3GB in the boot.ini and have SQL Server use 3GB of RAM. If so, do I need the /PAE option too? I don't need /AWE, that's only for > 4GB, right?quote:
Quote from Microsoft:
Caution Microsoft supports using the /3GB switch in Windows Server 2003, Standard Edition in a production environment for use by Active Directory. For other applications, Microsoft supports using the /3GB switch in Windows Server 2003, Standard Edition only in a production environment if the application vendor has tested in this environment and if the vendor is willing to support the customer who is using this functionality. Microsoft Exchange Server 2003 and Microsoft SQL Server 2000 are supported in production using this functionality. Contact your application vendor regarding their application. The /3GB switch can cause some applications to have problems that are related to address dependencies or to a reduction in kernel space. Except in the cases described here, the /3GB switch in Windows Server 2003, Standard Edition is only for development and testing purposes.
Thanks, |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-10-06 : 13:54:40
|
"I'm just not good at searching." I'm pretty sure there's a link to use thread in the "Frequently Given Answers" topic at the top of the "New to SQL Server" forumKristen |
 |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-10-06 : 14:40:13
|
quote:
Originally posted by Kristen
"I'm just not good at searching."I'm pretty sure there's a link to use thread in the "Frequently Given Answers" topic at the top of the "New to SQL Server" forumKristen
Yeah those are 100% not useful and are unrelated to my question. My questions are: Does any one know of any issues in regards to running /3GB on Windows 2003 Standard Edition with SQL Server 2000 Enterprise? and Will /3GB work on Windows 2003 Standard Edition? (The quote from Microsoft was a bit puzzling).EDIT:One other question: Should I run /3GB if SRS (Sql Reporting Services) is also on this box?* Please ignore the /PAE and AWE questions. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2005-10-06 : 17:16:38
|
| You need the /3GB switch without /PAE or /USERVA. SQL Server will take up to 3GB (2.7GB really) of memory.Be careful though. This can cause the kernel to run low on memory for PTE, which could blue screen the system. Usually this isn't a problem, but don't ask me how I know this one . Since this one comes up a lot, I should make a blog entry for it. Oh wait, I'd have to have a blog first. Can anyone help with that?Like a kidney stone, this too shall pass. |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-10-06 : 20:45:49
|
ec, what you talking about man????Here's a quote from the KB:quote:
Microsoft supports using the /3GB switch in Windows Server 2003, Standard Edition in a production environment for use by Active Directory. For other applications, Microsoft supports using the /3GB switch in Windows Server 2003, Standard Edition only in a production environment if the application vendor has tested in this environment and if the vendor is willing to support the customer who is using this functionality. Microsoft Exchange Server 2003 and Microsoft SQL Server 2000 are supported in production using this functionality.
MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-10-07 : 00:41:49
|
quote:
Originally posted by derrickleggett
ec, what you talking about man????
I must have picked the wrong day to stop sniffing glue.somehow I read this as win2k standard edition, not win2k3 standard ed. -ec |
|
|
|
franco
Constraint Violating Yak Guru
255 Posts |
Posted - 2005-10-07 : 05:14:57
|
| Hi SQLServerDBA_Dan,I found a very interesting note in a RedBooks Paper from IBM:Tuning Windows Server 2003:"The /3GB switch works for all version of Windows Server 2003, but you should use it only when runnin Enterprise or Datacenter edition.Standard Edition can allocate to user-mode application at most 2GB.If the /3GB switch is used in the Boot.ini file, then the privileged-mode kernel is restricted to 1GB of addressable memory without the corresponding increase of user-mode applications.This effectively means 1GB of address space lost."HTHFranco |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-10-07 : 09:09:39
|
quote:
Originally posted by franco
Hi SQLServerDBA_Dan,I found a very interesting note in a RedBooks Paper from IBM:Tuning Windows Server 2003:"The /3GB switch works for all version of Windows Server 2003, but you should use it only when runnin Enterprise or Datacenter edition.Standard Edition can allocate to user-mode application at most 2GB.If the /3GB switch is used in the Boot.ini file, then the privileged-mode kernel is restricted to 1GB of addressable memory without the corresponding increase of user-mode applications.This effectively means 1GB of address space lost."HTHFranco
Ah, ok. Thats what I was looking for. Microsoft's statement about it being supported in this environment but not in that one and then it only being supported if the server is a 1u or 3u but not a 2u or 4u except when the 2u is the color red or the 4u was in the rack with a 1u was quite silly and confusing. Seriously though, the articles I found on Win2k3 including this one seemed to flip flop more than John Karry.Thanks for the info. I'll choose to keep my 1GB of RAM.  |
|
|
|
|
/3GB in boot.ini on Win2003 standard