Friday, March 30, 2012

How can i configure SQL Server for clustring servers?

Hi
We are developing bussiness software for tourism company. Our application is
using SQL DB on MSSQL Server. We have a new customer and they have 500 or
more users.Around 300 users will be work on local network and 200 users will
be connect from remote side. My problem is how can i configure the sql
server's for best performance. We have just one DB for apllication. Am i
configure the sql servers for clustring.? I am wating for your ansvers. Than
k
you"Batur KILI" <Batur KILI@.discussions.microsoft.com> wrote in message
news:CB47B648-A5DE-4F9D-A94F-00E5F4DE8972@.microsoft.com...
> Hi
> We are developing bussiness software for tourism company. Our application
is
> using SQL DB on MSSQL Server. We have a new customer and they have 500 or
> more users.Around 300 users will be work on local network and 200 users
will
> be connect from remote side. My problem is how can i configure the sql
> server's for best performance. We have just one DB for apllication. Am i
> configure the sql servers for clustring.? I am wating for your ansvers.
Thank
> you
Clustering is a fail-over mechanism, not a scalability mechanism.
May be simpler to tune your application and buy a bigger server.|||Batur KILI wrote:
> Hi
> We are developing bussiness software for tourism company. Our application
is
> using SQL DB on MSSQL Server. We have a new customer and they have 500 or
> more users.Around 300 users will be work on local network and 200 users wi
ll
> be connect from remote side. My problem is how can i configure the sql
> server's for best performance. We have just one DB for apllication. Am i
> configure the sql servers for clustring.? I am wating for your ansvers. Th
ank
> you
Hi
Knowing that the customer has 500+ users doesn't tell a lot about the
load on the system...;-).
The first thing is to make sure that you design your application
properly and make the correct indexes etc.
I assume that you have some sort of idea on how the application performs
so based on that you should have an idea on how big a server you should
buy. Depending on the size, usage, design, complexity etc. of the
application, a dual proc server can be either way to small or really
overkill. Basically you should have enough memory and processor power
and a decent disk configuration. Then you can go on from that.
A decent disk configuration in my opinion will be to have enough disks
to create seperate arrays for OS files, Databasefile(s), logfile(s) and
backup. I'd then avoid RAID 5 for the logfiles and maybe for the
databasefiles (depending how much money you can spend) and then put
these on RAID 1 (or 10/01). Then buy 15 K disks rather than 10K and keep
in mind that the more spindles you have to read from the better (read)
performance you get.
With the above in mind, you'll be starting on a decent level. Then you
can start looking into specific areas if the performance isn't sufficient.
Regards
Steen Schlter Persson
DBA

No comments:

Post a Comment