September 6, 2008 at 12:51 am
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
September 6, 2008 at 4:52 am
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 6, 2008 at 8:22 am
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
September 6, 2008 at 8:16 pm
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.
September 7, 2008 at 11:16 am
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
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply