Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Sql Server (Recommended) Configuration Settings : 2000 & 2005 Expand / Collapse
Author
Message
Posted Saturday, September 6, 2008 12:51 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 1, 2013 2:51 AM
Points: 283, Visits: 312
Kindly provide Sql Server (Recommended) Configuration Settings : 2000 & 2005.
I have gone through various resources available online. But unable to find complete list of Recommended Configuration Settings.

Server Details :
Intel(R) Core 2 DUO CPU E 6850 @ 3.00 GHz
2.99 GHz, 3.24 GB of RAM
160 GB HDD
OS : Windows 2003 Server

Rgds
Mohan Kumar
Post #564993
Posted Saturday, September 6, 2008 4:52 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:01 PM
Points: 40,390, Visits: 36,823
In general the defaults are pretty good and in most cases shouldn't be changed unless you have a good reason. The exception is the max memory if the server in question has lots of memory (which your doesn't)

It's usually recommended that the OS, the SQL data file and the log files all go onto separate physical drives. You only appear to have one drive, so that's not possible.

p.s. Please post in the appropriate forum next time



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #565007
Posted Saturday, September 6, 2008 8:22 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 11:23 AM
Points: 2,281, Visits: 4,233
Your post indicates a 160 GB HDD - is this a SATA, ATA, or IDE drive ?
In order to insure data integrity, the disk drive cache must be disabled or writes will be lost causing the database to become corrupt.

Please read "Description of using disk drive caches with SQL Server that every database administrator should know" at http://support.microsoft.com/kb/234656



SQL = Scarcely Qualifies as a Language
Post #565031
Posted Saturday, September 6, 2008 8:16 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 3:03 PM
Points: 31,276, Visits: 15,728
3.24GB of RAM? Is this a 3GB or 4GB machine?

There are no real configuration settings that you need to change. However it completely depends on what you are doing with the server and what performance you need.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #565088
Posted Sunday, September 7, 2008 11:16 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 3:36 PM
Points: 35,531, Visits: 32,114
You MUST change the defaults for TempDB or you'll end up having 73 fragments by the time it grows to 1GB.

I normally start out a new system with 1000MB allocated to the mdf and 200MB-250MB allocated to the ldf. I setup the growth on the mdf to 250MB and 100MB on the LDF. Then, I watch it for a month. After at least one "month-end crunch" has passed, I'll set the sizes to whatever the current sizes are + 20% and bounce the service so I have a nice contiguous TemDB where the growth isn't going to take anyone by surprise.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #565144
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse