Link to home
Start Free TrialLog in
Avatar of r_i_x
r_i_x

asked on

SQL Server Configuration

SQL Server environment is 4 years old, looking to update/upgrade for performance, space, etc.

Hosts internal ERP solution. DB is about 50G in size and growing at about 15G/year. Between 150-200 users access site concurrently.

Current install is SQL Server Standard 2005, we do have license for SQL 2008 Enterprise.

Use Sage ACCPAC and DBs are also hosted there on same instance. (3 separate DBs) About 15 users making use of these DBs.

SQL Server Reporting Services is used and also on the same server instance.

Operation is 24/7 as it supports manufacturing environment. Some downtime is allowed for PM in slow season or some off weekends.

Looking for recommendations for configuration for ultimate performance. Budget is not determined at this point as the goal is performance. Let me know your thoughts/recommendations.
SOLUTION
Avatar of jogos
jogos
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of r_i_x
r_i_x

ASKER

What about recommended hardware? Infrastructure?

All on one server? Multiple servers? SAN? Cluster?
One server should not be a problem, but monitoring your server should learn you that: cpu, disk, memory.
Also for the sql itself you should monitor to see what's the bottleneck at the moment, how it slows down .  Maintenance (fragmentation), indexes, tuning querries, smaler lock-window .... there is a lot to gain but you have to measure first to see where you can improve.

Disk, general rule as much things you use together on different spindle. That goes for data-file, log-file, temp-db, backup-files (if you backup on disk first).
More than one temp-db (till one per CPU).

A cluster is always nice especialy when you want to keep the uptime high. If the small databases are on another sql instance you can put them default on the other node of the cluster. If a server upgrade has to be done you put them both instances on same node and you have your hands free on the other.

ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of r_i_x

ASKER

Not sure that hardware is the issue but here is what we're planning on.

What we're going to do:
- move reporting data (updated every night) to a SQL Express server.
- move another application's db to a different server
- start to archive  transactional data with a 13-month archive process
"Not sure that hardware is the issue " -> measure, measure, measure... even if you don't have a problem yet it's good to know the weakest part and a reference for when it's getting a problem or what the gain was of the moves of db's
 
Avatar of Mike McCracken
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.