Overview This white paper assumes that you have installed SharePoint Server 2013 and that you have configured it for apps. The instructions in this paper apply to a configuration where SQL Server 2012 Enterprise is the ContentDB and the application database server for SharePoint Server 2013. If you are using a separate instance of SQL Server 2012 for Access Services, see the section Set a new application database server. To install, set up, and provision Access Services in SharePoint Server 2013, you must perform the following major steps: Configure SQL Server 2012 Enterprise software for Access Services Configure SharePoint Server 2013 for SharePoint apps Configure Access Services Create a SharePoint Site collection for Access apps Because an Access app is a SharePoint app, you must first configure SharePoint Server 2013 as a SharePoint app server so that Access Services can successfully run Access apps. In addition, Access Services setup requires specific SQL Server 2012 configurations so that SQL Server 2012 can successfully store and manage the data for Access apps. Note: Software prerequisites for Access apps The following are the software prerequisites for Access Services in SharePoint Server 2013: SharePoint Server 2013 on at least Windows 2008 R2 SQL Server 2012 Standard or SQL Server 2012 Enterprise Components on the SharePoint Server: Microsoft SQL Server 2012 Local DB (SQLLocalDB.msi) Microsoft SQL Server 2012 Data-Tier Application Framework (Dacframework.msi) Microsoft SQL Server 2012 Native Client (sqlncli.msi) Microsoft SQL Server 2012 Transact-SQL ScriptDom (SQLDOM.MSI) Microsoft System CLR Types for Microsoft SQL Server 2012 (SQLSysClrTypes.msi) The following are the software prerequisites for creating and modifying Access apps: Access 2013 (required for Access app design) A web browser (required for viewing and updating data)
Overview This white paper assumes that you have installed SharePoint Server 2013 and that you have configured it for apps. The instructions in this paper apply to a configuration where SQL Server 2012 Enterprise is the ContentDB and the application database server for SharePoint Server 2013. If you are using a separate instance of SQL Server 2012 for Access Services, see the section Set a new application database server. To install, set up, and provision Access Services in SharePoint Server 2013, you must perform the following major steps: Configure SQL Server 2012 Enterprise software for Access Services Configure SharePoint Server 2013 for SharePoint apps Configure Access Services Create a SharePoint Site collection for Access apps Because an Access app is a SharePoint app, you must first configure SharePoint Server 2013 as a SharePoint app server so that Access Services can successfully run Access apps. In addition, Access Services setup requires specific SQL Server 2012 configurations so that SQL Server 2012 can successfully store and manage the data for Access apps. Note: Software prerequisites for Access apps The following are the software prerequisites for Access Services in SharePoint Server 2013: SharePoint Server 2013 on at least Windows 2008 R2 SQL Server 2012 Standard or SQL Server 2012 Enterprise Components on the SharePoint Server: Microsoft SQL Server 2012 Local DB (SQLLocalDB.msi) Microsoft SQL Server 2012 Data-Tier Application Framework (Dacframework.msi) Microsoft SQL Server 2012 Native Client (sqlncli.msi) Microsoft SQL Server 2012 Transact-SQL ScriptDom (SQLDOM.MSI) Microsoft System CLR Types for Microsoft SQL Server 2012 (SQLSysClrTypes.msi) The following are the software prerequisites for creating and modifying Access apps: Access 2013 (required for Access app design) A web browser (required for viewing and updating data)
AccessServices2013OnPremInstall.docx