• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1715
  • Last Modified:

SBS 2008, SharePoint 3.0 content database, and upgrade to SharePoint 2010

I'm running Small Business Server 2008 Standard with SharePoint 3.0. I'm intending to upgrade to SharePoint 2010 Foundation. I ran the stsadm preupgradecheck and the only remaining issue is "Databases within this farm are hosted on Windows Internal Database and are larger than or close to 4GB in size." Then it lists ShareWebDb, and ShareWebDb.mdb is indeed around 4GB.

Point 1: I installed SQL Server Express 2008 R2, upgrading the SQLEXPRESS instance. I moved ShareWebDb to this instance following the instructions under "Moving the Windows SharePoint Services content database" at http://technet.microsoft.com/en-us/library/cc794697%28WS.10%29.aspx. Companyweb and the one sub-site are working fine. In SQL Server Management Console I see the ShareWebDb database under SQLEXPRESS and the SQLEXPRESS version is 10.50.1600. So don't I now have a 10GB limit and the preupgradecheck is raising a false alarm?

Point 2. I applied a huge quota template to companyweb, which is the only SharePoint site other than SharePoint 3.0 CCentral Administration, which is using a different content database. Under Storage Space Allocation the entire site and its sub-site is using 119.9 MB.That's all the content I have. Why is the ShareWebDb.mdb file 4GB, and is there any way to shrink it? (I regularly shrink the log file).
0
JonFleming
Asked:
JonFleming
  • 7
  • 5
1 Solution
 
zephyr_hex (Megan)DeveloperCommented:
point 1:  sql express 2008 still has the 4 GB storage limitation.  express is also limited to 1GB RAM, and 1 CPU.

0
 
zephyr_hex (Megan)DeveloperCommented:
at some point EE will fix my default comment setting so it's not admin.  sorry about that.

point 1:  sql express 2008 still has the 4 GB storage limitation.  express is also limited to 1GB RAM, and 1 CPU.
0
 
JonFlemingAuthor Commented:
SQL 2008 Express R2 has a 10GB per database storage limitation, see http://www.microsoft.com/express/Database/ under "Powerful" I already ran into the 4GB limit on another server; users couldn't upload files. Installed SQL Server 2008 Express R2, moved the content database, users could upload, no problem.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
zephyr_hex (Megan)DeveloperCommented:
ah, well there you go.

i bet the preupgradecheck isn't aware of it either.

the only way to make the db smaller is to get rid of data, or shrink the db file.
0
 
JonFlemingAuthor Commented:
Sure seems crazy that the database file is 34 times larger than the actual data stored in it. A little overhead, yeah, but ...
0
 
zephyr_hex (Megan)DeveloperCommented:
the thing is... there's no way to make that size smaller... unless it's reducing the content or shrink the db file.  there's not another tool that magically compresses the size of the file.

imo, M$ may have planned some overhead.... in order to make SQL Express a less viable option.
0
 
JonFlemingAuthor Commented:
32 times overhead? Even the Evil Empire wouldn't do that. I bet if I restored one of my backups into a new database that database would be very small ...
0
 
zephyr_hex (Megan)DeveloperCommented:
the point is that there isn't a way to "change" that unless you shrink the db or remove content.  you can't magically make the size smaller.  it is what it is.

if it were a log file, the story would be different.
0
 
JonFlemingAuthor Commented:
Well, I'm going to try importing the baqckup into a new DB. Just to see.
0
 
JonFlemingAuthor Commented:
OK, I did some more investigation and it turns out that the log file is the size issue. What I thought was automatically shrinking the log files wasn't shrinking them. I tried shrinking the log files but they won't shrink because the initial size of the log file is 4,529MB. From "DBCC SHRINKFILE (ShareWebDB_log, TRUNCATEONLY)" I get "Cannot shrink log file 2 (ShareWebDb_log) because of minimum log space required.". From "DBCC SQLPERF(LOGSPACE)" I get 1.4% of that space being used. T I've tried a lot of variations and nothing seems to affect the size of the log file. I can see the initial size in the database properties, and I can change the number, but when I click OK the change is lost.
0
 
JonFlemingAuthor Commented:
Finally fixed the log file size. I removed ShareWebDB as a content database in SharePoint 3.0 Central Administration. In SQL Server Management Studio I created an empty database named ShareWebDB2. I used DBCopyTool to copy ShareWebDB to ShareWebDB2 (which just did a backup of one and a restore to the other). THe resulting database had a small initial log file size and a small log file size. I then attached ShareWebDB2 as the content database for my SharePoint site, and Bob's your uncle.
0
 
JonFlemingAuthor Commented:
Figured it out on my own.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now