Results 1 to 4 of 4

Thread: DBCC SHRINKFILE taking 3 times more in SQL Server 2000 than in 7

  1. #1
    Join Date
    Mar 2003
    Posts
    2

    Angry DBCC SHRINKFILE taking 3 times more in SQL Server 2000 than in 7

    Hi Folks:

    We´ve migrated from SQL Server 7.0 EE to SQL Server 2000 in a 8processors, 8 GB RAM server, using W2000.

    All seems go ok, but after reorganizing indexes, when we want to recover free space in the differents files using DBCC SHRINKFILE, that recovers are taking the triple of time than with previous SQL Server 7.0.

    Shrinking big files (6GB to recover 1.5 GB), previously taking 3 hours now are needing 9 hours.

    Any suggestion or help will be appreciated.

    Best Regards.

  2. #2
    Join Date
    Nov 2002
    Location
    New Jersey, USA
    Posts
    3,932
    Is it a data file or log file?. Shrinking a log file may not complete immediately because sql server can't shrink the active virtual log file, so it may be waiting for it to fill up before it could shrink.

    Did you use the option to release unused space to OS in both cases? Is the disk configuration similar? Also check if there was a queue in disk requests.

  3. #3
    Join Date
    Mar 2003
    Posts
    2
    It's a data file.

    We don't use the "Auto Shrink" options to preserve a good response time to the users, if this is what you mean with: "Did you use the option to release unused space to OS..."

    We didn't find anything wrong with the disks.

    The SQL is SQL Server 2000 EE SP1. We haven't yet decided to upgrade to SP2 since all our apps are tested with SP1.

  4. #4
    Join Date
    Sep 2002
    Posts
    5,938
    You can do it in sql2k em, worked great for me.

Posting Permissions

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