Re: Shrink problem
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 09/29/04
- Next message: Andrew J. Kelly: "Re: Inconsistent Performance of Insert"
- Previous message: Nigel Rivett: "RE: OpenQuery"
- In reply to: inamori: "Re: Shrink problem"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 18:17:52 -0400
Chances are that it Auto Grew immediately after it shrunk since there was no
room for any changes.
-- Andrew J. Kelly SQL MVP "inamori" <test@test.com> wrote in message news:cjc0gp$5t54@imsp212.netvigator.com... > why it has unused space again after 3 hours shrinking? > > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> ¦b¶l¥ó > news:eFwyquOpEHA.1992@TK2MSFTNGP09.phx.gbl ¤¤¼¶¼g... > > No don't turn on Auto Shrink. A database needs lots of free space to > > operate properly and if you don't have enough space it will grow. Chances > > are someone kicked off an Index Rebuild (or a scheduled job) that grew it > > again. > > > > -- > > Andrew J. Kelly SQL MVP > > > > > > "inamori" <test@test.com> wrote in message > > news:cj5h5u$j2a1@imsp212.netvigator.com... > > > In sql 2000, i have shrinked the database > > > 17Gb used data, 13 GB free data(need to be dhrinked) > > > > > > then i shrinked it... > > > that 13 GB is minmized, become only 17GB > > > so it should be fine. > > > > > > but few hourse later > > > that 13GB is come out again > > > > > > how can i solve it > > > > > > can I tick Auto-shrink function? > > > > > > and what is that 13Gb space for? > > > > > > > > > > > >
- Next message: Andrew J. Kelly: "Re: Inconsistent Performance of Insert"
- Previous message: Nigel Rivett: "RE: OpenQuery"
- In reply to: inamori: "Re: Shrink problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|