Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Delphi
  4. Slow Performance of SQL Server 2005...

Slow Performance of SQL Server 2005...

Scheduled Pinned Locked Moved Delphi
databasehelpdelphisql-serversysadmin
6 Posts 3 Posters 6 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    vijay victory
    wrote on last edited by
    #1

    Hi Experts... I am developing a Database application using Delphi 6 using SQL Server 2005 as backend. Its a working Live project now at my customer end. But Now the SQL Server getting slow as the Database and its Log file size increases. It becomes very critical situation that the customer some times feels like Server gets Hang and they Restart them. After Restart it will again works fine. I dont realize the actual problem..Can you Help me out..Its very Urgent. My server configuaration is : Xeon Quad Processor 8 Gb RAM 1 TB HDD and total 30 CLients are accesing the data as well as Updating the Database. PLEASE PLEASE PLEASE HELP ME.....

    I have never failed,I just found 1000 ways that never works. Regards, Victory.

    S D 2 Replies Last reply
    0
    • V vijay victory

      Hi Experts... I am developing a Database application using Delphi 6 using SQL Server 2005 as backend. Its a working Live project now at my customer end. But Now the SQL Server getting slow as the Database and its Log file size increases. It becomes very critical situation that the customer some times feels like Server gets Hang and they Restart them. After Restart it will again works fine. I dont realize the actual problem..Can you Help me out..Its very Urgent. My server configuaration is : Xeon Quad Processor 8 Gb RAM 1 TB HDD and total 30 CLients are accesing the data as well as Updating the Database. PLEASE PLEASE PLEASE HELP ME.....

      I have never failed,I just found 1000 ways that never works. Regards, Victory.

      S Offline
      S Offline
      Stryder_1
      wrote on last edited by
      #2

      Unfortunately, this is a huge issue to try to tackle on a forum. To adequately diagnose, I'd need to review your entire application. Unless your willing to contract for my services, that will not be possible here. Other than that, you might look to see how your handling your db connections - make sure they are all being closed after use. Another possibility is that you are locking db resources which make it impossible for other users to access at the same time. Rebooting the database, while not the recommended solutions, would free up both of these conditions. Just a few things to look into. Hope this helps.

      V 1 Reply Last reply
      0
      • V vijay victory

        Hi Experts... I am developing a Database application using Delphi 6 using SQL Server 2005 as backend. Its a working Live project now at my customer end. But Now the SQL Server getting slow as the Database and its Log file size increases. It becomes very critical situation that the customer some times feels like Server gets Hang and they Restart them. After Restart it will again works fine. I dont realize the actual problem..Can you Help me out..Its very Urgent. My server configuaration is : Xeon Quad Processor 8 Gb RAM 1 TB HDD and total 30 CLients are accesing the data as well as Updating the Database. PLEASE PLEASE PLEASE HELP ME.....

        I have never failed,I just found 1000 ways that never works. Regards, Victory.

        D Offline
        D Offline
        dan_fish
        wrote on last edited by
        #3

        Stryder_1 is quite right - this is too-big an issue to get a simple answer to. However, a good place to start may be with SQL Server Profiler (on the Tools menu of you Management Studio). Use this to set up a trace and identify what's happening when things are starting to go wrong. Two other (easy) things to check are: In your code, make sure you aren't opening new connections all over the place (the trace will tell you this) and, if you have stored procedures, make sure you are deallocating cursors correctly. Good luck!

        V 1 Reply Last reply
        0
        • S Stryder_1

          Unfortunately, this is a huge issue to try to tackle on a forum. To adequately diagnose, I'd need to review your entire application. Unless your willing to contract for my services, that will not be possible here. Other than that, you might look to see how your handling your db connections - make sure they are all being closed after use. Another possibility is that you are locking db resources which make it impossible for other users to access at the same time. Rebooting the database, while not the recommended solutions, would free up both of these conditions. Just a few things to look into. Hope this helps.

          V Offline
          V Offline
          vijay victory
          wrote on last edited by
          #4

          Thankx Stryder_1... I already checked it..and.. By the way.. as soon as the command gets executed and result get back. If I close the connection every time then for new command I think it will take some time to reopen the connection. If the command object is a local then after the Procedure is exited the command object will be free..then connection will also get Reset??? please correct me....

          I have never failed,I just found 1000 ways that never works. Regards, Victory.

          1 Reply Last reply
          0
          • D dan_fish

            Stryder_1 is quite right - this is too-big an issue to get a simple answer to. However, a good place to start may be with SQL Server Profiler (on the Tools menu of you Management Studio). Use this to set up a trace and identify what's happening when things are starting to go wrong. Two other (easy) things to check are: In your code, make sure you aren't opening new connections all over the place (the trace will tell you this) and, if you have stored procedures, make sure you are deallocating cursors correctly. Good luck!

            V Offline
            V Offline
            vijay victory
            wrote on last edited by
            #5

            hi dan_fish, I have checked it on SQL profiler..

            But I dont understand it. I found some procedures get executed at background and some of my queries take time (apporx 123455), whats does it mean??
            Is it take more time than expected?
            then what should I do??

            Please help me. I will check in my Source code.. and all the queries having Select * will replaced with only needed Column name. Will it do anything to performance???

            I have never failed,I just found 1000 ways that never works. Regards, Victory.

            D 1 Reply Last reply
            0
            • V vijay victory

              hi dan_fish, I have checked it on SQL profiler..

              But I dont understand it. I found some procedures get executed at background and some of my queries take time (apporx 123455), whats does it mean??
              Is it take more time than expected?
              then what should I do??

              Please help me. I will check in my Source code.. and all the queries having Select * will replaced with only needed Column name. Will it do anything to performance???

              I have never failed,I just found 1000 ways that never works. Regards, Victory.

              D Offline
              D Offline
              dan_fish
              wrote on last edited by
              #6

              Hi Vijay

              vijay.victory wrote:

              some of my queries take time

              then what should I do??

              Identify where the queries are coming from in your code, then run them in Management Studio and take it from there. Right-clicking in the query pane and selecting 'Display Estimated Execution Plan' may be of help in identifying where your problem lies.

              vijay.victory wrote:

              Is it take more time than expected?

              I can't tell you that - it's your database and code, so only you can know.

              vijay.victory wrote:

              all the queries having Select * will replaced with only needed Column name.

              That's a good idea - you should always do that anyway because it reduces network traffic, but your problem here is the time of execution, not the time of retrieval. Cheers, Dan

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups