Asif Rehmani, SharePoint MVP and MCT, in a video tutorial titled Creating a SharePoint 2013 testing environment – Part 2 – Installing SQL Server 2012, demonstrates in a condensed tutorial less than 5 minutes in length how to set up a SQL Server 2012 backend for a SharePoint 2013 test environment.
Administrators should first verify that the test environment includes the hardware and software required to support this backend. Once the administrator is satisfied that necessary supporting components are in place, the set up program for the installation should be run. For a test environment, the installation type should be set for standalone.
The set up program will prompt the user to enter a product key, and, subsequently to accept the license terms. If Service Pack 1 is available, the set up program should configure this critical update to run after the initial installation.
If only one server is available for the test environment for SharePoint 2013, then the set up program will report a warning that SQL Server 2012 is configured to be added to a domain controller, but the warning can be safely ignored specifically for a test environment only. If possible, it makes sense to install the database on a different server than the one used for Windows Server 2008 R2.
Asif Rehmani notes that “Database Engine Services” and “Full Text and Semantic Extractions for Search” should be selected and added to the database feature set. As well, the “Management Tools Basic” and “Management Tools Complete” should be added, as well.
Set up will then load a number of configuration settings for the installation.
Once the installation settings have been successfully added to the installation procedure by the set up program, the user should then configure the “SQL Server Agent” service to start “Automatically”.
“Windows Authentication Mode” should be used. The administrator for the test environment should be added as the administrator for this backend.
“Enable FILESTREAM” from the Filestream tab should be selected. As well FILESTREAM should be enabled for “file I/O access” and the Windows Share name entered.
Once all of the installation settings have been finalized, the installation should be run. Post installation it makes sense for the administrator to confirm that all of the settings have been correctly produced by the installation before restarting the server.
© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved