SQL Slowdown...

  • Group;

    I've had a SQL 2000 Server running on Windows 2003 Server Standard SP2 R2 for quite a while now.  The only DB on the server has been there for about a year.  Suddenly the application that utilizes the information in the DB has started moving slowly between fields and when running reports.  It is happening to all PCs so I highly doubt it is a PC issue.  I have uninstalled any patch that was installed via Windows update hoping that would resolve w/ no luck.  We did have some third party software installed that shows up in Add/Remove programs as Microsoft SQL Server Desktop Engine.  Microsoft SQL Server 2000 shows up seperately.  Could it be this third party software that was installed and is utilized MSDE that could be causing the problems?  The server has 2 3.0GHz Software w/ 4GB of RAM and each workstation is over 2GHz w/ 2GB of RAM.

    The DB size is .5GB and the log file is 4Meg.

    Any suggestions/insight?

  • Did you check the execution plan of the slow reports' queries?

     

    Maybe there's just a small thing that changed the normal plan. 

    When did you update the stats?

    When was the last reboot?

    Did you change anything on the procs?

  • Sorry for my ignorance but how can I check the execution plan? along w/ the stats?

    The last reboot was yesterday.  It does seem the reboot corrects the problem but it re-occurs within an hour.

    No changes have been made the to the proc.  The only thing that has changed in the last year was that we added the 3rd party app that uses SQL Desktop Engine.  However I can't easily uninstall that to see if it is the problem but if I can justify it is the problem I can remove it.  But I haven't heard of anyone else having conflicts between the two. 

  • You may have to limit the amount of memory each server uses because each is looking for 2 gig for a total of 4 gig... no room for the apps or the operating system left...

    --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)

  • Can you point me in the right direction to do that?   The Server is 2-proc but only lice. for 1 proc.  The server also has 4GB of RAM.

  • Since you seem to be truly new to administering/monitoring/tuning sql server, I HIGHLY recommend you hire a performance consultant for a few hours to give your system the once over. You will otherwise waste a lot of your time cycling back and forth on the forum iterating through the various checks/tests that a knowledgeable person could perform in minutes. Add in that of the 20 or so things I can think of off the top of my head you may not know how to perform any of them and I hope you can see why I make this recommendation.

    I wouldn't be surprised if there aren't a number of other issues that would be uncovered by a review, such as security problems, backup/disaster recovery issues, poor indexing, little/no database maintenance, etc, etc.

    A good consultant would also be able to mentor you so that you would be in a much better position to look after your systems when he/she is gone.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • Ummm... I gotta agree with that... tampering with server settings without knowing the full ramifications of each setting is nearly certain death for the server.  I'd get some qualified help on site for this one...

    --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 7 posts - 1 through 6 (of 6 total)

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