SharePoint Foundation – Database > 10GB; Also How to Create a New Web Application and Site Collection

Posted: January 25, 2012 in Default web site, IIS, SBS 2008, SBS 2011, SharePoint Foundation 2010, SQL Server 2008
Tags: , , ,


The SBS implementation of SharePoint Foundation relies on SQL 2008 R2 Express and any database has a size limitation of 10GB. Because I am a SharePoint bigot, I encourage my clients to take advantage of SharePoint and use it instead of shared files.  It certainly offers lots of benefits:

  • Version control
  • File granularity for permissions
  • Remotely accessible without the need for a vpn connection
  • Check-out and check-in for editing protection
  • Discussion groups and custom lists
  • Blogs and wikis
  • And lots more

SharePoint is also easily managed once you get the hang of it.

(Anyway, I will do another post on how users are taking advantage of SharePoint to do things for their businesses.  But this post focuses on what to do when they have done things too well and grown up to the maximum database size.  It equally applies if you just want a new web application – perhaps because you want different permissions on it from the standard site.)

Mulltiple Databases

While the maximum size of a single database is 10GB, a SharePoint installation can have multiple databases.  You can create a new web application with a new database in a single step.  SharePoint does all the heavy lifting for you.

These steps are done in SharePoint 2010 Central Administration.  Lacnch it on your SBS Server and see the home screen:

Farm Management Home Page

Under Application Management, choose the first item, Manage Web Applications:

You should see your SharePoint site and Central Administration.  On the ribbon, click on New and the following page opens.  I have filled it out with information to create both a new web application and a database to support it.  The fields I added or changed are highlighted in yellow.

Fields I Changed

The first field I changed was the suggested value for creating a new IIS web site.  SharePoint proposes the name

SharePoint – <random port number>.  You can use any name you wish if it is unique among existing web site names (see IIS display if you don’t know).  I decided to pick port 988, one above the SharePoint 987 for //companyweb.  So I changed the port number to 988.

SharePoint also suggest a database name of WSS_Content, which I changed to NewDataBase.  You can, and probably should, use a name that is relevant to your site like AdminData, HistoryData, etc.

If you want to use the SBS server for searching, click on the drop down box and select it.  Then click ok; you can leave the other fields as is. Once the processing screen finishes – it can take a few minutes to create the web site, application pool and update SharePoint configuration – you get the following notification

Application Created

Now Create a New Site Collection

Click Ok, and then Central Administration to go back to the home page.

While you have created a new web application, it is not yet a site that you can browse to.  You first have to create a new site collection.

Now click on Create site collections to see the site collection page.  The first thing to do is to select the web application.  On the upper right of the page you would see Web Application: and probably http:<something>.  Hopefully the something ends in :988 or whatever port you chose.  If not, click on the drop down arrow, chose change web application and then select the one you just created.

New Site Collection

Enter a site collection name in Title and a description of you wish.  Pick the type of site you want to create by choosing a template.  Then enter names for the site administrator; click on the book icon to search or type it in directly and check the name withe the person + check mark icon.  Set a quota if you have them defined and want to.

Then click ok,  and as if by magic you have a new site for your new web app and database.

Repeat the process as you need to.  In another post to come, I will go over how to customize the sites to have them all accessible from the same broswer.

What Has Just Happened?

SharePoint was busy doing some behind the scenes work for you.  It created a new Applicaiton Pool and Web Site you can see in IIS:

ApplicationPool Created

New Web Site Created

SharePoint also created a new database for you:

New SQL Database

Don’t  Forget

If you want to have this site available outside the LAN, open the port on your router and point to the SBS server. The internet URL is http://remote.<domainname&gt;.com:988 or whichever port you chose.

You can also create  apublic URL and put it in your root DNS provide that you configure alternate access messages.  Again, in another post on how to customize your new site and link the original, if you wish to.  Although you might want to have entirely different permissions on the two sites for application reasons.

  1. Robert says:

    Followed this great how-to and was able to create a new SP site (named sample) at port 989. It’s running (can access on server with http://localhost:989) but client computer fail (IE8 under XP Pro) when try http://sbs2011:989. Of course, http://companyweb works from the client PC as does http://sbs2011:25932 to reach SharePoint Central Administration. What piece of the puzzle am I missing to achieve a connection? Ultimate goal is accessing other SP site(s) from companyweb (perhaps with a simple link?) AND remotely with SSL (e.g. or, even better, Of course, getting a local LAN connection is step 1. Any help / direction you can provide will be greatly appreciated.


  2. Can you post an image from IIS Manager of the bindings associated with the web site? Did you also try https://sbs2011:987? I assume SBS2011 is in your local DNS as resolving to the server’s IP address. It is difficult for me to percieve what the bindings are.

    Try clicking on the browse links in IIS and see if the site opens. If it does, note what the URL is.

    Just mnake sure that after you created a new web application that you also create a site collection. Otherwise, you will get nothing when you try to browse to it.


  3. Robert says:

    IIS Manager shows the bindings as just “http” under Type and “989” under Port.
    “browse: 989 (http)” works perfectly from inside IIS Manager (yields http://localhost:989) and using http://sbs2011:989 from IE running at the server console brings up the Sample site with its default library, “welcome to your site” announcement, lists, etc. so it seems clear the site exists and is responding correctly, once you get a connection to it.
    This is a brand new Dell server setup specifically for development and testing situations exactly like this and, at the moment, only has 1 client PC running XP Pro. It has IE8, connects flawlessly to the “companyweb” (http://companyweb) and even to SP Central Admin (http://sbs2011:25932). But http://sbs2011:989 yields the generic “unable to display web page” error.
    “Extending Web Application” has nothing to do with this, right?
    When “Create New Web Application” ran, in the “Public URL” section, I left the “Zone” setting as “Default” per your how-to screen shot. Maybe my “Default” your “Default”?
    The bindings of the SP Central Admin are the same as Sample (just a different port #) so was surprised it connects when Sample does not.
    Certainly frustrating when all the complicated stuff (creating the site, app pool, database, etc.) goes so well and then some network setting somewhere throws a monkey wrench into the works.


  4. If it opens from IIS Manager, it is equally likely that it will open from a browser on the server; but from what you are telling me, it doesn’t work from a browser on a LAN desktop. That makes me suspect a firewall is blocking the port. Turn off firewalls on the server and desktop and try again. If you can now browse, then turn one of them back on, try browsing, and if successful, turn the other on: if you can no longer browse, there is your culprint. Or it may be that both are blocking, so investigate that as well.

    Depending on your router, it may also be the cause of blocking. If it is a simple router with just port blocking for incoming packets, it is unlikely to be the cause. However, more sophisticated routers can have rules on LAN->LAN traffic that might blpck port 989.

    In other words, there seems to be nothing wrong with your new web app and site; the propblem is not getting to it properly from off the server. That is what to focus on.


  5. Robert says:

    Got it to work by adding a new rule to the Windows Firewall on the server. Based it on the rule associated with the SP Central Admin port. Previously added a port-forwarding rule to the router for when remote access to this new SP side is attempted (don’t I have to run the “Extend Site…” process for that?). Just tried “” and browser could not connect.

    Getting the site to run under an SSL and from the outside world is the final goal – all mentioned as possibilities in the “Don’t Forget” section of your blog entry. Are their other sections of your blog I have not found that relate to this project? And thanks for your help and direction today!


  6. You are on the right track by openeing firewall ports.

    For SSL, you need to set that up in IIS by adding another binding. Realize that unless you get another third party certificate that matches the URL (like remote.) that you already have, browswer users will get a certificate mis-match warning. You also need to set up approprate exteral DNS entries.


  7. Robert says:

    Yep, essentially I am trying to make a new SharePoint site (with its separate 10GB limit) that acts like good ole companyweb: from LAN, http://companyweb; from WAN, Requires port 987 be forwarded to SBS2011 by router and have a Cname record in DNS connecting to my specific IP address. Purchase and install an SSL cert for rather than use the default self-issued one. Fairly usual SBS 2011 Standard stuff.

    In this first effort, LAN access is happy with http://SBS2011:989 but no remote access (both and don’t work, didn’t think it would). From what I’ve read over the years about SharePoint, “Extend an existing Web application” does alot of this configuring for you (see I’m pretty sure you can’t have http AND https traffic on the same port so maybe 989 for LAN and 1989 for WAN? Remote access would likely use something like (not sure if I must have the user include the port or if the Cname record could handle, either way is OK). Purchase another SSL cert for to make https happy.

    Hopefully, I am not too far off the track on this project. Will likely have a dozen or so of these separate sites running on the production server (once I have the proper set-up steps figured out). As always, any direction or help will be greatly appreciated.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s