SQL 2012 Installation Guide. Manually installing an SQL Server 2012 instance

Transcription

1 SQL 2012 Installation Guide Manually installing an SQL Server 2012 instance

2 Fig 1.2 Fig 1.1 Installing SQL Server Any version and edition of Microsoft SQL Server above 2000 is supported for use with the library system. Be mindful however, that SQL 2005 employs a 2GB database limit and we recommend that you use a later version. This means that if this limit is reached, no further transactions (i.e. books circulated, resources added etc.) will be stored in the data and will be discarded. As a result, it is recommended to use a full version of SQL server or an express version that has a higher database limit, such as 2008 or For a list of capability requirements for SQL 2012, visit this MSDN page. The instructions below explain how to install and configure SQL Server 2012 express ready for configuration with the library system. This is being demonstrated from a Windows Server 2008 R2 machine. 1. Launch the installation media from the downloaded file or from the installation disc. Once the files have been extracted, select the option of Install a new stand-alone installation or add features to an existing installation. 2. The license page will display, click to accept this agreement and click Next. 3. If a prompt displays advising to install a product update, click Next again. 1

3 Fig 1.4 Fig Any updates will then be installed. When this has finished, click Install. 5. The Feature Selection window should show next. 2

4 Fig 1.5 Many of the features in the window are optional and are not required for using the library system. The required features are listed below: Database Engine Services Full-Text and semantic Extractions for Search NOTE The Management Tools are not required but are highly recommended. This allows you to manually view the data and to take manual backups of the system when required. It may be desirable to install other features such as the reporting services or documentation, depending on your requirements. Click Next when you are ready to continue. 6. The next box shows the instance options. Here you can choose whether to use a named instance or use the default. The installation directory of the instance can also be chosen. To select a named instance, check the Named Instance radio button and enter the name of your instance. If you wish to use the default then check the Default Instance radio button. NOTE The instance name can be used to separate databases onto different segments. You may have many SQL instances installed onto one server (e.g. MISInstance, LibraryInstance, SQL2012Instance, DevelopmentInstance) each managing their own databases. The library application can belong on either a named instance or the default. 3

5 Fig 1.6 In this example, the instance is being labelled SQL2012. When specifying the SQL server details for the library application later, the format to use is servername\instancename so in this case we would enter WIN-10O3217NDBK\SQL2012. If you are not using a named instance and use the default then there is no need for the \instancename. Click Next when you are ready to continue. 7. The next set options that follow relate to the service accounts used to run the SQL Services. Note that by default, the Startup Type of the Full-text service is set to Manual. As this is a required component, we will need to start this service and change the startup type to Automatic later. This means that should the computer restart, the service will automatically start. The SQL Server browser service is required in a lot of environments (for instance, when using MLS Connect) so set this to Automatic. Click Next to continue. 4

6 Fig On the Server Configuration page, check the Mixed Mode option under the Authentication Mode heading. Enter a password for the SA account into the appropriate text boxes. IMPORTANT Keep this password safe as it is likely to be required for future interactions with your SQL instance. It can be difficult to gain any level of access to the instance without this password. It is not MLS s responsibility to maintain the SQL Server and MLS cannot recover this password for you in the event of it being lost. The SA account is SQL Servers built in super account. If necessary, it is possible to add other administrative accounts for use with SQL by using the Add Current User button. Click Next to continue. 9. Click Next on the Error Reporting window and then the software should then start to be installed. NOTE This may take a while to install even if few components were selected on the feature selection page. 5

7 Fig 1.9 Fig Once this has completed, a summary window will show showing the status of the installation. Click Close. 6

8 Fig 1.11 Fig 1.10 The next stage is to set the Full Text component / service to automatically start. 11. Open the Server Manager and select configuration then Services on the left menu. 12. Locate the SQL Full-text Filter Daemon Launcher and view the properties. In the Startup type drop down box, select Automatic then Apply. 7