Posted by Jack Vamvas on 08/07/07 06:11

Another thing you could try , which is inexpensive, is to take a Trace of
the various dbs at their busy periods.
See if you can idebtify the very slow sql statements , e.g over 5000 , and
work to enhance these statements.


--

Jack Vamvas
___________________________________
Need an IT job? http://www.ITjobfeed.com




"Fox1977" <foxj77@gmail.com> wrote in message
news:1186438670.488303.93160@d55g2000hsg.googlegroups.com...
hi there,

Just wondering if anyone can offer any advice on an a SQL performance
issue i have repeatedly come up against in work. I am a sys admin for
an internet company and we are having problems with SQL eating up too
much of the CPU on a brand new server. I am new to SQL so apologies
is my questions sound a bit simple. I have recently migrated one of
our databases to a new server (2 x CPU, 4gb RAM) and things were
running sweet. Recently we have launched a few new websites running
off the back of the database. The average CPU utilisation is now
hovering at about 50%. The problem is that we have a number of other
sites ready to launch off the database. We are running SQL 2000 on
windows 2003 standard x64 R2.

Obviously the first port of call would be to look at the database/
websites and try and optimise the code in order to improve the
performance but it is proving really difficult to squeeze any
resources out of the company. The directors of the company think that
because they have spent �22k on a new SQL server they do not have to
put any more effort in. Whilst things have been pretty easy for a few
months as usual everyone has taken their eye off the ball. I can
quite easily see a situation arising in a couple of months were we
have a database that requires more power that the server it is running
on.

Can anyone offer any advice on the way forward with this one? I know
I need to looking into putting in a solution that will scale but it is
going to go down like a lead ballon after spending 22k 8 months ago.

I am looking at a number of different options:
short term: what could be done to improve the situation
long term: what type of solution could i put in place? I am looking
at SQL clustering but it looks very pricey. Do i need the enterprise
version to do active/active clustering and how many servers does an
enterprise licence cover me for. I have also though about having some
kind of virtual cluster of machine with the virtual machine running
acorss several servers.

Is there any performance gains to be made by upgrading to SQL 2005?

Any tips/ideas/pointers gratefully received.

[Back to original message]