Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2003-05-23 : 09:17:29
|
| Well, I've done a search, and got a lot of hits, on SQL Prod Configuration", but not really what I'm looking for. So lets me pose this for comments :Given:Windows 2000 SP3SQL 2000 SP2 + slammer8 x 1.4G XEON4GB RamOLTP environmentData sverer pre-dominantly dedicated to SQL server, but some application code resides there (not IIS etc. but the system has an batch component, and the batch controller runs on the data server)Data server dedicated prod box for only 1 environment (not shared).220 GB "primary " database, with 3 x 200 MB metadata and other databases, as part of system.C: OS ( 10 gb partition on raid local scsi) d: OS ( 10 gb partition on raid local scsi) e: data (external storage - fibre channel to HBA) 345 GBf: log (external storage - fibre channel to HBA) 45 GBg: Backup (external storage - fibre channel to HBA) 345 GBh: remainder of scsi available - 50 gb - dump and transfer etc.What we've set up :Autostart sql, agent and msdtc (all used)DYNAMIC memory 0-4096. NO physical memory reserved for SQL - this is one specific popint I'm looking for commentary on.Boost SQL pri on Windows.SQL uses all 8 processorsNOT using Fibre'sWe have /3GB switch in the Windows .ini file.swap file (page file) 2 GB on C: 4 GB on D:Usage:4000 to 10000 connections from up to 500 distinct users during 12 hours online day. Largely sequential batch jobs running through 8+ hour batch window. OLTP predominant usage read, thou large percentage is CUD as well, probably split around 65-35 or so, during OLTP, 35-65 during batch.Some questions:So what are people with vaguely similar config's doing regards the AWE /3gb settings. Our OS guys is saying 1 GB isn't enough for OS, whereas I say give SQL all the memory it wants - the OS is only there to serve the DBMS. If a server needs 50% of system memory to run the applications, then why evn have the /3gb switch ?Other commentary ?CiaO*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-05-23 : 12:55:30
|
| 1GB is plenty for the OS. Typically, the OS only needs about 128MB. We use the AWE switch and have it the same as you. As far as the memory reserved for SQL Server, we allow SQL Server to use whatever it wants (minus 128MB - we set the max to total RAM - 128MB) on systems where only one instance is installed. On systems where we have multiple instances, we split up the memory between the instances to whatever makes sense.Tara |
 |
|
|
|
|
|
|
|
Prod Box Configuration