4GB Database Limit - SharePoint Foundation 2010 with SQL 2008 Expres

Hi -

I'm using SharePoint Foundation 2010 SP2 with SQL 2008 Express on Server 2008 R2. All three applications are the 64-bit version. SQL and SharePoint are on the same box.

My problem, WSS_Content SQL database is at the 4GB limit.

I have ONE web application within SharePoint

What is the quickest resolution, even a temporary solution, and how would I do this?

Some ideas I came across:
1) I noticed SQL 2008 has a 4GB limit, and 2008 R2 has a 10GB limit.
2) I do have a SQL 2008 Standard Server (with all the proper licenses)
3) Can I split this up to multiple databases without doing any upgrades

Please keep in mind my total admin experience with SharePoint is about 15 minutes. So, all the details are helpful!
First LastAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
Those are SQL express limits not SQL Server where the maximum .mdf file size is 524,272 terabytes.. you can painlessly upgrade from express to standard or other versions by doing an edition upgrade
Deepak ChauhanSQL Server DBACommented:
Forget about point 3.

You can upgrade express to licenced version for a long term fix. If cost does matter you can move to SQL express 2008 R2 , your database size is 4 GB only.
ste5anSenior DeveloperCommented:
The others are right, back up your system and upgrade that SQL Server Express Instance.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Vitor MontalvãoMSSQL Senior EngineerCommented:
Upgrading your local EXPRESS instance is the fastest way to do it but I'ld go for moving the database to the SQL Server Standard instance and uninstall the EXPRESS instance since it's something more using the resources on the SharePoint box.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
First LastAuthor Commented:
This process was fairly simple. I wrote up the steps below for a co-worker. I'll share them here.

Upgrade SQL Express 2008 to SQL Express 2008 R2 – This will change the limit from 4GB to 10GB.

Steps took to do the upgrade. Each step involved a reboot. Total time about 3 hours (I spent a lot of time doing other things and rebooting)
Figure out how to prep the server for an upgrade of sql. I found a tool to disable all sql and sharepoint services in one click. This took 30 minutes.
Find the proper sql files to download.  This was annoying, but after 30 minutes I found the right two files.
Upgrade SQL Server, reboot. This took 30 minutes.
Upgrade SQL Management Studio, reboot. This took 30 minutes.
Use the SQL/SharePoint tool to disable all services. 1 minute.
Manually expand the database to 5GB. This was just a test, because I read earlier today sometimes there can be problems. 5 minutes.
I couldn’t get the SharePoint site to load in IE, but the SharePoint Central Admin tool worked. Looked at the easiest solutions first then went on to the ones which took longer.  Steps below took me 30 minutes of my time.
a.      Reboot server (tried twice for good luck). I wasn’t lucky.
b.      Restarted services manually     I wasn’t lucky.
c.      Took the content database offline and online.  I wasn’t lucky.
d.      In Central Administration, went to the Review Problems and Solutions section. I clicked on each problem for details, but they referred me to links with pages of info. I wasn’t up to reading all that because I remembered those errors from earlier today and figured they weren’t important at this time.
e.      run SharePoint Products Config Wizard again. I gave it a try and it worked. This worked.
ste5anSenior DeveloperCommented:
No points for my post please... It was just a kind of confirmation..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.