Can anyone be so green?

  • Leave it to Microsoft to bundle two products together that don't play well together!

    Funny how their accounting application (over 6 GB in size), also SQL based, performs normally through all of this, even in the worst of times for the other app...

     

  • SQL unfortunatly likes to be on a server of its own. It doesn't like sharing resources with anything. It could be worse. I've seen someone put SQL on the same server as their domain controller. The resulting mess wasn't pretty

    If there's another SQL database that's not slowing down, then I'm less likely to think hardware and mre likely to think badly written app. It could still be hardware.

    At the moment though I'm just guessing. It's very hard to pinpoint a cause without stats.

    Unfortunatly performance tuning is an art and is difficult enought with a couple years experience

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Notwithstanding the previous posts and sorry to duplicate this but I agree that profiler is the choice of weapon here, however difficult or painful it may be to get used to it (plenty of practice required).

    Run profiler to output proc/sql info and get users to tell you when the 'slow' down occurs and correlate the time with profiler to see what was running at that time. Alternatively find the long queries, ie those with long execution times and attack those first.

    Most probable cause is a query that is doing table scan(s) and is getting progressively worse as more data is inserted and may be hogging resources.

    An I have seen this kind of problem create problems for an individual database or the whole server and found performance monitor inconclusive.

    Far away is close at hand in the images of elsewhere.
    Anon.

  • Absolutely agree with that!

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 4 posts - 31 through 33 (of 33 total)

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