Post reply

shrinkdatabase

  • October 8, 2003 at 10:30 am

    #59451

    I have a database with 12 GB, I executed the shrindatabase command by enterprise manager set the option "move pages of begining after shrink", and after the command the size of the database went to 26 GB. Did anybody already go by that?

    Agnaldo Silva


    Agnaldo Silva

  • October 8, 2003 at 2:18 pm

    #477633

    I always go to the file option and execute the shrinking of the specific file.First I move the data, then I delete the data file, or I shrink till the level I want.

    Try that way

  • October 8, 2003 at 2:59 pm

    #477638

    Well here is what I do if I want to shrink my database.

    

    BACKUP LOG <DBName> TO <LogBackupDevice> WITH Stats, NOINIT

    BACKUP LOG <DBName> WITH TRUNCATE_ONLY

    DBCC SHRINKDATABASE(<DBName>)

    BACKUP DATABASE <DBName> TO <BackupDevice or file>

    I've yet to have this fail to shrink my database. BUT, make sure to run the full backup after you are done!

    Gary Johnson

    Microsoft Natural Language Group

    DBA, Sr. DB Engineer




    Gary Johnson
    Microsoft Natural Language Group
    DBA, Sr. DB Engineer

    This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed in this post are my own and may not reflect that of my employer.

  • October 9, 2003 at 12:24 pm

    #477748

    If you are running SQL Server 7.0 with sp2 or sp3 and are trying to shrink a database that contains text or image data, there is a known bug that causes the db to expand. See the following link:

    http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q308/6/27.asp&NoWebContent=1

    I've had this happen to me. SP4 will fix the problem.

Viewing 4 posts - 1 through 3 (of 3 total)

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