Post reply

how to test a sql server's capability to withstand an additional database

  • June 5, 2008 at 4:10 pm

    #121798

    Hi,

    I have a existing SQL server which has a database around half a gig and around 100 users per day connect to it through a webserver. I am planning to add an another Database to this instance. My worry is whether this can affect my existing application. Could you give me some advice on how I can test/monitor current resource usage (stress test, etc), so that I can decide about adding the other database.

    Thanks.

  • June 5, 2008 at 5:01 pm

    #825186

    -

  • June 5, 2008 at 9:37 pm

    #825242

    Are you adding another database or an instance? Instances are more complicated.

    Adding a database means that you share tempdb, and there are some threads, data cache, procedure cache, being used by the other database. The amount of load? Depends on the activity on the other application/database. THe more activity, the more resources it will need.

  • June 6, 2008 at 12:37 am

    #825289

    I am adding a DB to an existing instance (the server has only one instance). If I can monitor the current load, resource usage using a tool, I may be able to decide whether it is sensible to add another DB.

    Thanks for your reply.

  • June 6, 2008 at 1:27 am

    #825300

    If its is SQL Server 2005 then you can find usage reports in Management Studion.

    Otherwise you can use SQL Diag. Manager from Idera comes with 15 days Eval..

    It will help you to findout your bottelnecks and growth Stats.

    Regards,

    Raj

  • June 6, 2008 at 2:18 am

    #825320

    Thanks, Raj. I will try that (sql server 2000).

  • June 6, 2008 at 7:40 am

    #825433

    You first need to baseline your current activity so you know if you're already running into bottlenecks or if you have room to grow. There are several products that you can do a trail install of to get this - Idera, Quest[/url], SQLSentry, etc. There's also SQLH2from Microsoft which is free but not as straightforward as the other paid products.

    Also, Kevin Kline did a good set of screencasts called "Perfmon Counters for the SQL Server DBA" which outlines some of the perfmon counters you should keep an eye on to guage performance.

    Once you have your baseline you can see if you have any issues to resolve. You've also now got a set of "before" numbers that you can use to compare against when you consolidate.

    Kendal Van Dyke

    http://kendalvandyke.blogspot.com/

    Kendal Van Dyke
    http://kendalvandyke.blogspot.com/[/url]

  • June 6, 2008 at 4:15 pm

    #825762

    Thanks guys for your advice.

  • June 7, 2008 at 5:38 pm

    #825844

    Great tip Kendal! Thanks



    My blog

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply