1.3 Configuring SQL Server 2012
SQL Server must be correctly configured
to support the demands of Access Services 2013. The first of the
following required steps requires the installation media to be
available.
Adding Required SQL Server Features
Run the setup (or rerun the setup to
adjust an existing installation), and ensure that the following
features are enabled in the development environment:
- Database Engine Services
- Full-Test and Semantic Extractions for Search
- SQL Management Tools (Basic and Advanced)
- Client Tools Connectivity
This step requires the original installation
media and may require the reinstallation of service packs. Follow
proper protocols when updating production machines!
Enabling Contained Databases
SQL Server 2012 helps to isolate
databases from other databases via the concept of contained databases.
The containment of databases in SQL Server 2012 is required by Access
Services to not only protect each database but also the SQL Server
instance. SQL Server implements database isolation from the instance in
four ways:
- Meta data describing the database is maintained in the database rather than in the master database.
- All meta data is stored with the same collation.
- User authentication is performed by the database rather than by SQL Server.
- SQL Server support reporting on containment information.
Activating containment is as simple as setting
the Enable Contained Databases flag to True in the SQL Server’s
Advanced Properties dialog. Open SQL Server Management Studio,
right-click the server, and choose Properties. On the Advanced page is
the option to Enable Contained Databases. Set this to True.
Enabling the Mixed Authentication Security Mode
Access Services 2013 supports both
Windows and SQL Server authentication, so SQL Server must be configured
to support both as well. In SQL Server Management Studio, right-click
the server and choose Properties. On the Security page is the option to
allow SQL Server and Windows Authentication Mode.
Ensuring Appropriate Service Account Permissions
SharePoint 2013 continues the long
tradition of service accounts available previously in SharePoint 2010
and 2007. When an Access Services 2013 service application is created,
a service account must be either assigned or created. This service
account must be a pre-existing Active Directory account and must have
been granted the dbcreator, public, and securityadmin
roles for the server. Open SQL Server Management Studio and locate the
service account in the Security ⇒ Logins section. Right-click the
account, and select the Server Roles page to ensure the required server
roles have been granted.
Enabling Required Networking Protocols
Open the SQL Server Configuration
Manager tool, and expand the SQL Server Network Configuration group to
select Protocols for MSSQLSERVER. By default, only Shared Memory is
enabled. Right-click Named Pipes and select Enabled. Right-click TCP/IP
and select Enabled. At this point, all available network protocols
should be enabled.
1.4 Configuring the Windows Development Environment Firewall
Now that SQL Server has been properly
configured, the Windows environment hosting SQL Server must be prepared
to receive HTTP traffic on ports 1433 and 1434 for TCP and UDP.
1. Open the Windows Firewall with the Advanced Security utility.
2. Right-click the Inbound Rules option and select New Rule.
3. The New Inbound Rule Wizard pops up and asks which type of rule should be created.
4. Select Port and click Next.
5. The wizard advances to the Protocols and Ports screen. Select TCP and type 1433, 1434 into the Specific Ports field; then click Next.
6. The wizard advances to the Action screen. Select Allow the Connection and click Next.
7. The wizard advances to the Profile screen. Leave Domain and Private, clearing the checkmark from Public, and click Next.
8. The wizard advances to the Name screen. Type SQL TCP into the Name field, and click Finish.
Repeat the previous steps with the following changes for the UDP incoming rule:
- On the Protocols and Ports screen, select UDP and type 1433, 1434 into the Specific Ports field; then click Next.
- On the Name screen, type SQL UDP into the Name field, and click Finish.
1.5 Configuring SharePoint 2013
At this point, SQL Server is fully
configured, the firewall is ready to accept inbound traffic on the SQL
Server environment, and an isolated app domain has been created. The
final prerequisite step is to create and configure the Access Services
2013 service application.
Starting Required Services
In Central Administration, go to Manage
Services on Server to ensure the following services are started. Start
them if they are not already running:
- Access Services 2013
- Access Services (Access Database Service 2010 for viewing and modifying existing 2010 Access web databases)
- App Management Service
- Microsoft SharePoint Foundation Subscription Settings Service
- Secure Store Service
Creating a Secure Store Service Application
Open Central Administration and go to
Manage Services on Server. In the Service Applications Ribbon tab,
click the New drop down, and select to create a new Secure Store
Service Application. The default settings are all valid, so click OK to
create the new service application. After the new application has been
created, run an IISRESET to ensure enough memory is available for the
next step. Click the Generate New Key button on the Ribbon to fully
activate the Secure Store Service. This last step takes a while; don’t
be alarmed if nothing happens for a few minutes.
Creating the Access Services 2013 Service Application
The final step is to create the actual
Access Services 2013 service application. Open Central Administration,
and go to Manage Services on Server. On the Service Applications Ribbon
tab, click the New drop-down, and select the Access Services option
(not the Access Services 2010 option, which is used to support legacy
Access Services 2010 instances).
The Create New Access Services
Application dialog opens and asks for the Application Database Server.
This server is used to create new application databases and is expected
not to be the same SQL Server instance that SharePoint is using;
although that configuration is supported. If a new SQL Server is
brought online for Access Services databases in the future, opening the
Access Services Application configuration offers an opportunity to
change the database server.
