|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:51 AM
Points: 127,
Visits: 277
|
|
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?
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
How big's the data file, how big's the log file?
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:51 AM
Points: 127,
Visits: 277
|
|
| db file size is 6 GB and log is 9 gb
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
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 2008, MVP 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
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:51 AM
Points: 127,
Visits: 277
|
|
| 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
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
Backups don't change file sizes.
I suspect you may need to read this: Managing Transaction Logs
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:51 AM
Points: 127,
Visits: 277
|
|
| thanks for the link. After shrinking the log file now DB size has reduced to 6GB.
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
I take it you missed the section in that article about not shrinking the log then.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Yesterday @ 11:09 PM
Points: 328,
Visits: 939
|
|
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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:51 AM
Points: 127,
Visits: 277
|
|
| The log file size had increaded due to BCP operaiton. Hence i did the shrink. Is it ok to do dhrink in this case?
|
|
|
|