Sharepoint 2010 Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint 2010       RSS Feeds

self-hosted Sharepoint 2010, SQL server, and interaction

  Date: May 30    Category: Sharepoint 2010    Views: 1335

I am thinking of hosting SP 2010 on our own server for our "company";
we have about 400 users. We will have 4.5mb of T1 bandwidth, and on a Windows
Server 2008 64bit machine.

For our company's main database, we have been using MS Access, but since we have
used QuickBooks for accounting, we inadvertently ended up with separate

I understand that we can use QuickBooks with SQL server, and I also understand
we can build front-ends to the SQL database using MS Access (or something else.

My question is, can I also use a self-hosted Sharepoint Foundation Services 2010
to create a web-interface to that same SQL database?



18 Answers Found

Answer #1    Answered On: May 30    

First take a look at the SPF 2010 Specs:

You can only use SQL 2008R2 or SQL 2008 Express.

In theory you can host multiple databases on 1 server, however there is a lot
more to think about before you proceed.
You should read through the Technet planning article:

SQL express is limited to 10GB databases.
The I/O impact of having multiple databases on 1 server.
The server specs itself.
Do you foresee the need to move to SP 2010 in the future?

Answer #2    Answered On: May 30    

Thank you very much! I will look at those links.

We haven't done anything yet; we have a 64bit Windows 2008 server, so I want
very much to use the 2010 sharepoint.

Presently, we have a hosted sharepoint services 2007 site (where the 400 users
go), but it is not connected to our main database in any way.

What I would like to do (I think) is to run a single SQL server (not express; I
would like to purchase one, I think) and access a single database from both the
in-office front end, as well as sharepoint. Does that sound weird?

Answer #3    Answered On: May 30    

We do want to move to sharepoint 2010. We also need another database
solution because we are outgrowing Access, and because we need a back end that
will work for both Quickbooks as well as custom front-ends build on Access.

Thus, we need to make them all work together: Sharepoint (for a web-front end),
QuickBooks, and Access.

Has anyone ever heard of doing that?

Answer #4    Answered On: May 30    

Access can use SharePoint 2010 as a back end. In fact, you can import the
whole thing and create a "web database" which can then be accessed either
through the browser or through Access. Furthermore, you can take the
resulting Access DB offline and then sync it later with the centralized
copy on the SharePoint server.

As for QuickBooks, I've never gone there -- but if it can use SQL Server as
a back end, then there should be no problem.

Answer #5    Answered On: May 30    

Okay, first, forgive me if I sound redundant... I want to create the SQL
database the way I want, then make QB match to the schema, then self-host the
sharepoint 2010 to use THAT database.

What do you think?

Answer #6    Answered On: May 30    

So you're saying you want SharePoint users to be able to pull data from the
QB DB? There are ways to do that. As for the QB schema scheme, I have no
input :)

Answer #7    Answered On: May 30    

Well, yes, in effect. I want a main database where QB, Sharepoint and Access
are all front-ends.

Answer #8    Answered On: May 30    

You can do that all on SQL, but not all in the same database. SharePoint has its
own schema and you're not allowed to change it. Pretty sure QuickBooks is the

Answer #9    Answered On: May 30    

that is the pith that I was looking for, with regards to sharepoint.
However, to accomplish my goal, then, what do you think of this:

Run sharepoint 2010 in its own SQL database, run QB in its own separate database
(if that is absolutely required), and then have a third SQL database that
queries the other two into something we can access from other sources, such as
Access or asp.net.

What would you do?

Answer #10    Answered On: May 30    

Probably easier to use BCS in SharePoint to access the QB database from
inside SharePoint. You can also load the Access database directly into
SharePoint or use BCS to access the third SQL database.

Answer #11    Answered On: May 30    

BCS? Is that a sharepoint function? Is it available to the Foundation or
Standard editions?

I understand about loading an access database into sharepoint.

Answer #12    Answered On: May 30    

Business Connectivity Services. Its in everything from Foundation up.

Answer #13    Answered On: May 30    

So, am I right to understand that I can't make Sharepoint run on a custom SQL

Answer #14    Answered On: May 30    

Correct. SharePoint creates its own database, and MS doesn't support any
direct meddling with it.

Answer #15    Answered On: May 30    

Thank you! That is what I suspected. So I understand that you can make
Sharepoint run on SQL server, but you can't create a SQL database and then
"attach" sharepoint to use your own fields and tables for certain data.

Okay, but I CAN create an access database and "move" it to sharepoint, and then
"attach" Sharepoint to that database to use my own fields and tables, right?
And this I can sync to my SQL database, right?

Answer #16    Answered On: May 30    

please don't touch the SharePoint SQL database in ANY case. Create another
database for your data if required. You can connect native SharePoint lists to
SQL Server or even Access tables or queries using Business Connectivity Services
(BCS) or (more sophisticated) 3rd party solutions like Business Data List
Connector (BDLC) without any programming, bi-directional if required.

See here fore more information:

Answer #17    Answered On: May 30    

You should never, ever mess with the SP database in a
production environment.

You can take your Access database and import it into SharePoint, which
essentially creates a SharePoint site where the tables are now lists, etc.
This functions as a web-enabled database and can be accessed by anyone with
a browser (or opened in Access). It does not, however, exist as actual
tables in the SQL database.

Answer #18    Answered On: May 30    

That depends on what you mean by custom SQL database

Didn't find what you were looking for? Find more on self-hosted Sharepoint 2010, SQL server, and interaction Or get search suggestion and latest updates.

Related Topics:



Related Post