Results 1 to 4 of 4

Thread: Strange fix

  1. #1
    Join Date
    Oct 2003
    Posts
    16

    Unanswered: Strange fix

    Hi,
    I have table in my db thats used as a temporary table. At the end of the day it contains thousands of records which get summarized then all are deleted. I recently moved the application over to a new server with pretty much the same hardware config and noticed a big performance hit when running queries on this temp table (455 milliseconds as opposed to 1) In short, the fix was dropping the table and re-creating it.
    Anybody know how this could be? I know that even if you delete records from a table, the table still seems to retain its physical size on the hard drive, could this have something to do with it?

    Thanks

  2. #2
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    What "fix"? You just moved the application to a new server. You don't say that you changed the code or the process in any way, so it makes no sense that it would suddenly start dropping the table.
    Do you know for a fact that the table is being dropped and recreated?
    How many records are in it at the end of the day? I wonder if the statistics aren't just out of date.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  3. #3
    Join Date
    Oct 2003
    Posts
    16
    Basically, I have a table that gets 1000's of rows added to it per day then at the end of the day the records are all deleted. It seems that after 9 months of performing this task on this certain table, queries on the table started taking 450+ milliseconds to complete rather than 0-2 milliseconds (which it should be) Im wonding if anyone knows why this happens or has experienced anything similar.

    Thanks

  4. #4
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    Well first of all, if this is a process that runs once a day during off-hours, why is 450 milliseconds a big deal?

    Second, post the code that is being executed against the table so we can review it for efficiency.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •