Installing Microsoft SQL Server

This chapter will guide you through installing the required Microsoft SQL engine for Patriot 6 deployment. This document covers all supported versions of SQL with sections to help the non-automated full version installations. (when not using the provided SQL express engine). If at any time you run into any unexpected problems during any part of this installation guide, try the Patriot 6 installation trouble shooting guide, or contact your software supplier. Alternatively you can contact Patriot support directly at support@Patriotsystems.com

As an alternative, Patriot is allowed to freely distribute SQL Express to anyone using Patriot. The express version is purely a SQL database engine; it has some advanced functionality removed, and has some size restrictions. But these should only affect users of Patriot with a large client base. If you are trialing Patriot, SQL express will be more than adequate. Comparisons of the different versions of SQL with respect to Patriot are available on the Patriot website, hardware specification page.Patriot 6 requires that either Microsoft SQL Server 2005/2008/2012 Database Engine, or Microsoft SQL 2005/2008/2012 Express Edition be installed on the server machine. The full version of the Database Engine is recommended, but requires separate licensing through Microsoft. For ease of use it strongly recommended you use the patriot supplied installation package for express SQL for easy configuration.

Depending on which version of SQL you have opted to install. Follow the relevant sections that follow to confirm installation and configure the version of SQL you are running. Once complete, continue installation with the section entitled. Installing Patriot 6 on a server. Previous versions of SQL server such as SQL server 2000 or MSDE are no longer supported in Patriot 6

For larger monitoring stations, read the SQL Server System Setup document for more information on setting up an SQL server using recommended settings.

Installing SQL Server 2005 express

If you are using the supplied installation package or directed by patriot support to download the distributed version of SQL from the website this is the version you will be installing. The 2005 express edition has some features removed, does not include the management studio and has an approximate database limitation of 4Gb per database. Although this is usually more than enough for new installations and well into the future for new monitoring operations where years of data can be held.

Installing SQL Server 2005 (full version)

You must uncheck ‘Hide advanced configuration options’ to get access to some required settings.

Setup will run a system configuration check, once complete, check to see if any status warnings are reported. If so you may need to check them with your system administrator or I.T department to discern if these warrant concern. However, IIS is a possible exception as it is not necessary and indeed recommended to be absent from your Patriot server.

2005 Configuration Check

For problem free performance of your SQL database and Patriot software, please ensure to complete the following sections after installation.

Configuring SQL 2005 for Workstation and Remote workstation Connections.

Installing Microsoft SQL 2008 R2

Database Engine Services - SQL database itself

Management Tools Basic - SQL Management Studio

Installing Microsoft SQL 2012

Follow the steps below to install and configure SQL 2012

•Database Engine Services

•Client tools Connectivity

•Management Tools - Basic

•Management Tools - Complete

When installing SQL 2012 on Windows 7 on a 64-bit PC you may have to add system account NT AUTHORITY\SYSTEM as SQL sysadmin. After installation of SQL 2012 is finished follow steps below: Please contact patriot support if you are unsure how to do this.

USE master

GO

SELECT p.name AS [loginname] ,

p.type ,

p.type_desc ,

p.is_disabled,

CONVERT(VARCHAR(10),p.create_date ,101) AS [created],

CONVERT(VARCHAR(10),p.modify_date , 101) AS [update],

s.sysadmin

FROM sys.server_principals p

JOIN sys.syslogins s ON p.sid = s.sid

WHERE p.type_desc IN ('SQL_LOGIN', 'WINDOWS_LOGIN', 'WINDOWS_GROUP')

-- Logins that are not process logins

AND p.name NOT LIKE '##%'

-- Logins that are sysadmins

-- AND s.sysadmin = 1

GO