MIS Systems Thread, SQL setup for SIMS in Technical; Does anyone have any guidance on what settings should be implemented in SQL 2008 R2 Full to run a SIMS ...
19th July 2011, 03:26 PM #1
SQL setup for SIMS
Does anyone have any guidance on what settings should be implemented in SQL 2008 R2 Full to run a SIMS Database? I have a server ready with Server 2008 R2 and 16GB RAM and I just need to install SQL. Are there any tweaks I should be doing to enable it to use both Processors (2 quad cores) and as much RAM as it needs? I have bought 2 x Processor licence so am covered for 2 processors.
Any pointers would be greatly appreciated.
19th July 2011, 04:01 PM #2
To begin with just leave it as is. It should be able to use and manage all it needs. You'd only tweak if you were having problems.
On install, you'll probably get the warning about firewalls, you just need to let the sqlbrowser.exe through Setting up a test from backup
19th July 2011, 08:15 PM #3
I've been saying to install Capita's SQL Express then put the 2008 disc in the upgrade the edition then do a new install and install SQL Management studio. Once SQL management studio installed, enable AWE. Not recommending R2 yet. I've yet to hear of a good reason to install it.
20th July 2011, 08:22 AM #4
I have an install step by step for sql2008r2 but i dont have it with me. I'll mail it later. can you pm me your email.
20th July 2011, 08:24 AM #5
Dont think you need to do anything with processor or ram in sql.
Are there any tweaks I should be doing to enable it to use both Processors (2 quad cores) and as much RAM as it needs? I have bought 2 x Processor licence so am covered for 2 processors.
20th July 2011, 08:52 AM #6
SQL should use all the memory and cores by default anyway, most of the optimisation comes from designing the IO subsystems.
As for tweaking SQL itself, you should start with adding additional tempdb files of a reasonable but equal size, one for each core assigned to SQL. You should also ensure that the database file growth options are set correctly. I've seen SIMS databases set to 1MB growth which has terrible overhead and causes horrific OS level fragmentation. I'd recommend you set the database to a fixed size with room to spare, set a reasonable growth size (depends on your database size) and use windows defrag while sql is disabled to ensure the database files are contiguous before going live.
20th July 2011, 09:25 AM #7
Growth rate of about an eighth of the maximum you'd want i think is reasonable. My initial is 140MB with growth at 125MB. It doesn't often go crazy, but when it does it's easy to shrink it down again. This was with a nearing 4GB mdf file. I worked it out a while ago, based on best practise, and it seems to be okay.
If we're talking best practise now, you could look up the threads regarding the type of raid to use for each db, and where to put them, i.e. separate data partitions with temp db separate etc. but there's no point reiterating all that here.
By vikpaw in forum MIS Systems
Last Post: 18th September 2012, 08:42 AM
By hutchy in forum MIS Systems
Last Post: 27th July 2011, 07:54 PM
By chazzy2501 in forum General Chat
Last Post: 30th April 2010, 11:31 AM
By fox1977 in forum Thin Client and Virtual Machines
Last Post: 29th January 2009, 11:34 AM
By timbo343 in forum Windows
Last Post: 7th November 2007, 10:27 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)