Post reply

SQL express 2008 R2 - DB size

  • October 1, 2012 at 12:16 am

    #267409

    I am using express edition of SQL 2008 R2. As per the microsoft sites we can have max DB size as 10GB. But in my sql server current size is 15GB

    I dont know how this is possible. Do you have any idea?

  • October 1, 2012 at 1:13 am

    #1543790

    How big's the data file, how big's the log file?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 1, 2012 at 1:35 am

    #1543798

    db file size is 6 GB and log is 9 gb

  • October 1, 2012 at 1:51 am

    #1543802

    You're within the size limits then. The size limit is on the data files, the log file does not count. so 6 GB used out of 10 GB allowed.

    p.s. Got proper log management in place? Log files aren't usually larger than the data files.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 1, 2012 at 2:08 am

    #1543820

    I just took Full backup but still the log file size is showing 9GB? I did it using sqlcmd command and the procedure sp_BackupDatabases

  • October 1, 2012 at 2:16 am

    #1543825

    Backups don't change file sizes.

    I suspect you may need to read this: Managing Transaction Logs[/url]

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 1, 2012 at 3:35 am

    #1543861

    thanks for the link. After shrinking the log file now DB size has reduced to 6GB.

  • October 1, 2012 at 3:44 am

    #1543871

    I take it you missed the section in that article about not shrinking the log then.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 1, 2012 at 10:34 am

    #1544052

    On a related note, I've discovered a hole in the 10GB limit. We have a user with a SQL 2008 R2 Express instance on his workstation whose been adding tables to the Master database and importing data to them. He's up past 50GB now.

    I'm NOT recommending that anyone do this. I'm suggesting that if anyone from the Microsoft SQL Dev team is reading you might want to take a look at this.

  • October 8, 2012 at 1:40 am

    #1546582

    The log file size had increaded due to BCP operaiton. Hence i did the shrink. Is it ok to do dhrink in this case?

  • October 8, 2012 at 1:58 am

    #1546593

    As a once-off operation, shrink's OK. See the article I referenced.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 14, 2012 at 9:36 am

    #1559018

    can u suggest any other method other than shrink to reduce the log size?

  • November 14, 2012 at 10:08 am

    #1559031

    No, there is no other method.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 13 posts - 1 through 12 (of 12 total)

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