avaya workforce optimization sql server · avaya workforce optimization sql server installation and...

Avaya Workforce Optimization SQL ServerInstallation and Upgrade GuideRelease 15.1

Issue 22016

© 2016 Avaya Inc.

All Rights Reserved.

NoticeWhile reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.Documentation disclaimer"Documentation" means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User.

Link disclaimerAvaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya.Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them.Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages.

WarrantyAvaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya's standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website: http://www.avaya.com/support or such successor site as designated by Avaya. Please note that if you acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to you by said Avaya Channel Partner and not by Avaya.

LicensesTHE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO, OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ("AVAYA").Avaya grants you a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to you. Software" means Avaya's computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed, or remotely accessed on hardware products, and any upgrades, updates, bug fixes, or modified versions thereto. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Instance" means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ("VM") or similar deployment.

License typesShrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as “shrinkwrap” or “clickthrough” license accompanying or applicable to the Software (“Shrinkwrap License”).

CopyrightExcept where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya.Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.

VirtualizationEach product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered.

Third Party Components"Third Party Components" mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ("Third Party Components"), which contain terms regarding the rights to use certain portions of the Software ("Third Party Terms"). As required, information regarding distributed Linux OS source code (for thoseProducts that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya's website at: http://support.avaya.com/Copyright or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components.

Note to Service Provider The product may use Third Party Components subject to Third Party Terms that do not allow hosting and require a Service Provider to be independently licensed for such purpose. It is your responsibility to obtain such licensing.

Preventing Toll Fraud"Toll Fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya Toll Fraud interventionIf you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://support.avaya.com, or such successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: [email protected].

TrademarksThe trademarks, logos and service marks ("Marks") displayed in this site, the Documentation, Hosted Service(s), and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party.Avaya is a registered trademark of Avaya Inc.All non-Avaya trademarks are the property of their respective owners.Linux® is the registered trademark of Linus Torvalds in the U.S. andother countries.

Downloading DocumentationFor the most current versions of Documentation, see the Avaya Support website: http://support.avaya.com, or such successor site as designated by Avaya.

Contact Avaya SupportSee the Avaya Support website: http://support.avaya.com for Product or Hosted Service notices and articles, or to report a problem with your Avaya Product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya.

1 How to Use This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7How to use this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Install SQL Server 2014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Microsoft links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Verify prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Verify user rights assignments to SQL Services account . . . . . . . . . . . . . . . . . . . 12Verify minimum software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Install .Net 3.5 Framework SP1 on Windows 2012. . . . . . . . . . . . . . . . . . . . . 14Calculate max memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Install SQL Server 2014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Post-installation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Modify the SQL Server port (mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . 28Keep Model DB size at 128 MB or lower . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Grant Database Administrator permissions . . . . . . . . . . . . . . . . . . . . . . . . . 30Install the latest SQL Server 2014 service pack . . . . . . . . . . . . . . . . . . . . . . . 34Install the latest SQL Server 2014 hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . 34Disable CEIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Configure the SQL Server 2014 online help . . . . . . . . . . . . . . . . . . . . . . . . . 35Install SQL Server 2005 backward compatibility components . . . . . . . . . . . . . . . . . 36

Example: Install SQL Server 2005 backward compatibility components . . . . . . . . . . . 36Add SQL Server trace flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Enable Optimize for Ad Hoc Workloads option . . . . . . . . . . . . . . . . . . . . . . . . 41Enable remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Manually configure remote SQL Server 2014 . . . . . . . . . . . . . . . . . . . . . . . . 42

Remote SQL Server configuration settings . . . . . . . . . . . . . . . . . . . . . . . . 42Remote SQL Cluster configuration settings . . . . . . . . . . . . . . . . . . . . . . . . 44

Update ServerName attribute for multiple instances/cluster configuration of remote SQL server 46Set SQL Server Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Install SQL Performance Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3 Upgrade to SQL Server 2014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Microsoft links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Upgrade checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Verify prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

C o n t e n t s

Contents

SQL Server Installation and Upgrade Guide 4

Confidential and Proprietary Information of Verint Systems Inc.

Verify user rights assignments to SQL Services account . . . . . . . . . . . . . . . . . . . 54Verify minimum software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Prepare SSRS for an SQL Server upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Post-upgrade SQL Server 2014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Grant Database Administrator permissions . . . . . . . . . . . . . . . . . . . . . . . . . 56Install latest SQL Server 2014 service packs & hotfixes . . . . . . . . . . . . . . . . . . . 59Keep Model DB size at 128 MB or lower. . . . . . . . . . . . . . . . . . . . . . . . . . . 59Disable CEIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Configure the SQL Server 2014 Online Help. . . . . . . . . . . . . . . . . . . . . . . . . 60Verify SQL Server trace flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Verify Ad Hoc Workloads and remote access settings . . . . . . . . . . . . . . . . . . . . 62Manual configuration for remote SQL Server 2014. . . . . . . . . . . . . . . . . . . . . . 62

Remote SQL Server configuration settings . . . . . . . . . . . . . . . . . . . . . . . . 63Remote SQL cluster requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Update ServerName attribute for multiple instances/cluster configuration of remote SQL server66

Update statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Modify database compatibility level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Run DBCC UPDATEUSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Update system environment path variable . . . . . . . . . . . . . . . . . . . . . . . . . 70Verify SSRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Redistribute the EM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4 Install SQL Server 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Microsoft links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Verify prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Verify user rights assignments to SQL Services account . . . . . . . . . . . . . . . . . . . 75Verify minimum software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Install .NET 3.5 Framework SP1 on Windows 2012 . . . . . . . . . . . . . . . . . . . . 77Calculate max memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Install SQL Server 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Post-installation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Modify the SQL Server port (mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . 91Keep Model DB size at 128 MB or lower. . . . . . . . . . . . . . . . . . . . . . . . . . . 93Grant Database Administrator permissions . . . . . . . . . . . . . . . . . . . . . . . . . 93Install the latest SQL Server 2012 service pack . . . . . . . . . . . . . . . . . . . . . . . 97Install the latest SQL Server 2012 hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . 97Resolve out of memory error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Disable CEIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Configure the SQL Server 2012 help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Install SQL Server 2005 backward compatibility components. . . . . . . . . . . . . . . . . 99

Example: Install SQL Server 2005 backward compatibility components . . . . . . . . . . . 99Add SQL Server trace flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Enable Optimize for Ad Hoc Workloads option . . . . . . . . . . . . . . . . . . . . . . . .103Enable remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104SQL Server 2012 local and remote SQL configurations . . . . . . . . . . . . . . . . . . . .105

Remote SQL Server configuration recommendations . . . . . . . . . . . . . . . . . . .107

Contents



Remote SQL cluster requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Remote SQL Server with multiple instances or cluster configuration . . . . . . . . . . . .110Install Management Client and Shared Management Objects on DBMS . . . . . . . . . . .111

Set SQL Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Install SQL Performance Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

5 Install SQL Server 2008/R2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Microsoft links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117Verifying prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Verifying user rights assignments to SQL Services account . . . . . . . . . . . . . . . . . .119Verifying minimum software requirements . . . . . . . . . . . . . . . . . . . . . . . . .119

Install .NET 3.5 Framework SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Calculate max memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Install SQL Server 2008/R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Post-installation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Modify the SQL Server port (mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . .134Keep Model DB size at 128 MB or lower. . . . . . . . . . . . . . . . . . . . . . . . . . .136Grant Database Administrator permissions . . . . . . . . . . . . . . . . . . . . . . . . .137Installing the latest SQL Server 2008/R2 service pack . . . . . . . . . . . . . . . . . . . .140

Example: Install SQL Server 2008/R2 SP1 . . . . . . . . . . . . . . . . . . . . . . . .140Install the latest SQL Server 2008/R2 hotfix . . . . . . . . . . . . . . . . . . . . . . . .145

Example: Install latest SQL Server 2008/R2 hotfix . . . . . . . . . . . . . . . . . . . .145Resolve out of memory error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Disable CEIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Configure the SQL Server 2008/R2 online help . . . . . . . . . . . . . . . . . . . . . . .150Install SQL Server 2005 backward compatibility components. . . . . . . . . . . . . . . . .152

Example: Install SQL Server 2005 backward compatibility components . . . . . . . . . . .152Add SQL Server trace flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Enable Optimize for Ad Hoc Workloads option . . . . . . . . . . . . . . . . . . . . . . . .157Enable remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158SQL Server 2008/R2 local and remote SQL configurations . . . . . . . . . . . . . . . . . .159

Remote SQL Server configuration recommendations . . . . . . . . . . . . . . . . . . .161Remote SQL Server cluster recommendations . . . . . . . . . . . . . . . . . . . . . .163Remote SQL Server with multiple instances or cluster configuration . . . . . . . . . . . .164Install Management Client and Shared Management Objects on DBMS . . . . . . . . . . .166

Set SQL Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

6 Install and Configure SSRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170SSRS Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Install SSRS Reporting Service (Remote SQL) . . . . . . . . . . . . . . . . . . . . . . . . .172Add SSRS to an existing SQL Server Instance . . . . . . . . . . . . . . . . . . . . . . . . .178

Verify the SQL service pack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Configure SSRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181

Connect to the Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Configure the Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183Configure the Web Service URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Contents



Configure the Report Server database . . . . . . . . . . . . . . . . . . . . . . . . . . .185Test the Report Manager URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Configure SSRS E-mail Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Configure Database Server Name Change in SSRS . . . . . . . . . . . . . . . . . . . . .191

Verify SSRS configuration post SQL upgrade. . . . . . . . . . . . . . . . . . . . . . . . . .192SSRS Encryption Keys Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . .193

7 Set Database Management Permissions . . . . . . . . . . . . . . . . . . . . . . . . . 194Database Management Account (DMSA). . . . . . . . . . . . . . . . . . . . . . . . . . . .195DMSA preparation workflow scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Assign DB permissions automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Access the Database Permissions Configuration Tool . . . . . . . . . . . . . . . . . . . . .197Verify tool user credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198Verify Windows PowerShell functionality . . . . . . . . . . . . . . . . . . . . . . . . . .198Run the Database Permissions Configuration Tool . . . . . . . . . . . . . . . . . . . . . .198

Assign DB permissions manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Verify user credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Set account permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Create or modify SQL credential object . . . . . . . . . . . . . . . . . . . . . . . . . . .201Assign MSDB permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Assign I360 databases permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204Create a new proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Modify database user name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207

SQL Permissions for Service Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Table A: Management Service account permissions . . . . . . . . . . . . . . . . . . . . .209Table B: Database Management Service account permissions . . . . . . . . . . . . . . . .210Table C: SQL public server role permissions . . . . . . . . . . . . . . . . . . . . . . . . .212

Post-system configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

C h a p t e r 1

How to Use This Guide

Topics How to use this guide, page 8

Chapter 1 - How to Use This Guide How to use this guide


How to use this guideThis guide provides step by step instructions for customer Database Administrators responsible for the SQL Servers used in the system.

The guide includes instructions on how to:

Install the SQL Server

Upgrade the SQL Server

Install a stand-alone Reporting Service in the data center when there is a remote SQL Server deployment

Configure database permissions for the service account managing the databases.

Follow the chapters that are relevant to your deployment.

Guide usage

Task Required For... Section to Use

Prepare

Prepare the site for SQL Server, SSRS, service accounts

All deployments Technology, Security & Network Integration Deployment Reference Guide

Install and Configure

Install the SQL Server

All deployments Install SQL Server 2014, page 9Install SQL Server 2012, page 72Install SQL Server 2008/R2, page 115

Install SSRS on the DB Management Platform

L3-L6 deployments with remote SQL only

Install SSRS Reporting Service (Remote SQL), page 172

Configure SSRS All deployments Configure SSRS, page 181

Upgrade

Upgrade the SQL Server

Customers upgrading SQL Servers

Chapter 3 “Upgrade to SQL Server 2014”

Verify SSRS post SQL Server upgrade

For customers upgrading SQL Servers

Verify SSRS configuration post SQL upgrade, page 192

Set Database Permissions

All deployments Set Database Management Permissions, page 194

C h a p t e r 2

Install SQL Server 2014

This section provides detailed instructions for installing SQL Server 2014 Enterprise or Standard Edition (ENT/STD), according to system requirements and the customer license.

Topics Microsoft links, page 10

Installation checklist, page 11

Verify prerequisites, page 12

Install SQL Server 2014, page 17

Post-installation procedures, page 28

Chapter 2 - Install SQL Server 2014 Microsoft links



Microsoft linksMicrosoft links to help you prepare and install SQL Server.

Latest SQL Server 2014 downloads, including feature pack:

http://www.microsoft.com/en-us/download/search.aspx?q=sql+2014

Change SQL Server Port:

https://msdn.microsoft.com/en-us/library/ms177440(v=sql.120).aspx

Opening the firewall ports for SQL Server:

http://support.microsoft.com/kb/968872




Chapter 2 - Install SQL Server 2014 Installation checklist



Installation checklistThe checklist provides a list of SQL Server 2014 installation procedures and an estimate of the time required to complete each procedure.

Status Step Procedure Estimated Time (minutes)

1 Verify prerequisites, page 12 5

2 Install SQL Server 2014, page 17 40

3 Modify the SQL Server port (mandatory), page 28

10

4 Grant Database Administrator permissions, page 30

5

5 Install the latest SQL Server 2014 service pack, page 34

20

6 Install the latest SQL Server 2014 hotfix, page 34

10

7 Disable CEIP, page 34 1

8 Configure the SQL Server 2014 online help, page 35

5

9 Install SQL Server 2005 backward compatibility components, page 36

10

10 Add SQL Server trace flags, page 38 2

11 Enable remote access, page 41 10

Chapter 2 - Install SQL Server 2014 Verify prerequisites



Verify prerequisitesBefore installing SQL Server 2014, you must meet the site and software requirements.

Workflow1 SQL Server requirements

The customer must prepare the site for the SQL Server installation according to the Technology, Security, & Network Integration Deployment Reference Guide. See the SQL Server Requirements section in the Third-Party Products chapter.

2 Open firewall ports for SQL Server

3 Verify user rights assignments to SQL Services account, page 12: Verify the user rights assignments for the SQL services account running the SQL Server Database Engine service.

4 Verify minimum software requirements, page 14

5 Calculate max memory, page 16

Related informationHow to open the firewall port (http://support.microsoft.com/kb/968872)

Verify user rights assignments to SQL Services accountVerify the user rights assignments for the SQL services account running the SQL Server Database Engine service.

Procedure1 In Windows 2012, navigate to Control Panel > System and Security >

Administrative Tools > Local Security Policy.

2 In the Local Security Policy window, click Local Policies, and then click User Right Assignment.


Chapter 2 - Install SQL Server 2014 Verify user rights assignments to SQL Services account



3 Double-click each of the following items, and verify that the list includes the service account running the SQL Server Database Engine service:

a. Lock pages in memory

b. Log on as a servicec. Perform volume maintenance tasks

Related informationSQL Services Account Requirements (Technology, Security, & Network Integration Deployment Reference Guide)

Chapter 2 - Install SQL Server 2014 Verify minimum software requirements



Verify minimum software requirementsEnsure that you meet the minimum software requirements before installing SQL Server 2014.

Requirements Microsoft Windows

For operating system requirements, see the Customer Furnished Equipment Guide.

Microsoft Windows Installer 4.5 or a later version

Install Windows Installer 4.5 using the Installation Wizard. If you are prompted to restart your computer, restart it, and then run setup to install SQL Server 2014.

.NET Framework 3.5 SP1 or higher.

Note that .NET Framework 4.0 is automatically installed when installing SQL Server 2014. You need to enable .NET 3.5 SP1

Windows PowerShell 2.0

Related topicsInstall .Net 3.5 Framework SP1 on Windows 2012, page 14

Install .Net 3.5 Framework SP1 on Windows 2012

You must install .Net 3.5 Framework SP1 on the database server. The procedure used to install the framework varies depending on the version of Windows server currently running.

Procedure1 Insert the Windows Server installation DVD in the drive.

2 Open a command prompt as an administrator.

3 Type the following command:

dism /online /enable-feature /featurename:NetFX3 /all /Source:d:\sources\sxs /LimitAccess

where d:\sources\sxs is your Windows installation DVD.

Chapter 2 - Install SQL Server 2014 Install .Net 3.5 Framework SP1 on Windows 2012



Upon completion, the following message is displayed.

Enabling feature(s)

[=======================100.0%======================]

The operation completed successfully.

4 Open Server Manager.

5 On the Manage menu, click Add Roles and Features.

6 On the Before you begin page, click Installation Type.

7 On the Select installation type page, click Role-based or feature-based installation, and then click Next.

8 On the Select destination server page, select the server that SQL Server 2012 will be installed on, and then click Next.

9 Click Features.

10 On the Select features page, under Features, select .NET Framework 3.5 Features.

You do not need to select HTTP Activation or Non-HTTP Activation.

11 Click Next.12 On the Confirm installation selections page, click Specify an alternate source

path, and then enter the source path specified in Step 3.

Once the installation is complete, the following is displayed under Features.

Chapter 2 - Install SQL Server 2014 Calculate max memory



Calculate max memoryThe maximum memory required for the SQL Server in GB, is calculated according to this formula:

(total - (2048 + (APP + IFA + ITS) * 4096 + REC * 10240 + IAS * 2048)) * factor

where

total is the total RAM on the server in GB.

APP, IFA, ITS, REC and IAS are the server roles that can be configured on the server, and can be set to either 1 (configured) or 0 (not configured).

APP is Framework Applications

IFA is the Speech Application Server

ITS is a Speech Transcription Server

REC is the Recorder Integration Service

IAS is the Interaction Analytics Service

factor is a predefined value based on the SQL Server version, and is either 0.7 for SQL Server 2008, or 0.8 for higher versions.

Automatic memory calculationFor local SQL Servers on consolidated platforms only, the CommonSB plugin automatically calculates and sets the SQL Memory based on this formula.

Override memory calculationA customer can manually override the automatic max memory calculation, and set the maximum memory according to their own calculation.

To override the automatic max memory calculation, configure the registry and commondb database settings. Registry:

Locate the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6423Node\Impact360\DatabaseSDK

Set IsSqlServerLocal to False.

commondb database:

Locate the SERVER_DISABLE_MEMORY_ALLOCATION parameter:

Set MAXIMUM SERVER MEMORY to 1, indicating that the memory should be configured manually.

Chapter 2 - Install SQL Server 2014 Install SQL Server 2014



Install SQL Server 2014The SQL Server Installation Wizard guides you through the steps required to install SQL Server 2014.

Procedure1 Run Setup

a. Insert the SQL Server 2014 installation media into the DVD drive.

b. Open the drive and run setup.exe.

2 Installation TypeSelect Installation, and then select New SQL Server stand alone installation or add features to an existing installation.

3 Product KeyEnter the product key, and then click Next.

4 License Terms

Accept the license terms, and then click Next.5 Global Rules

The global rules check runs automatically and does not require any action on your part.

6 Product UpdatesLeave the settings unselected, and then click Next.




7 Install RulesVerify that all rules have a status of Passed, and click Next.

8 Setup RoleClick SQL Server Feature Installation, and click Next.




9 Feature Selectiona. Select the Mandatory Instance Features, page 19.

b. Select the Mandatory Shared Features, page 19.

c. Change the Shared Features directory (if required).

d. Click Next.

Instance Features Database Engine Services

SQL Server Replication

Required for customers using Key Management Servers (KMS) for End-to-End Encryption, as each KMS server contains its own copy of the SQL database.

Reporting Services Native (SharePoint is not supported):

Required on servers hosting the Reporting server role only. That includes, consolidated servers and deployments where the SQL Server and Reporting roles are hosted together.

Shared Features Client Tools Connectivity

Integration Services

Management Tools - Basic

Management Tools - Complete

NOTE The feature list may change for different SQL server editions. The remaining features are optional.




10 Feature Rules

a. Wait for the operation completed message, and then click Show Details.

b. Verify that all rules have a status of Passed, and click Next.

11 Instance Configurationa. Select one of the following:




Default Instance: you can have one default instance per machine. The default instance name is MSSQLServer.

Named Instance: you can set a named instance, such as Impact360 to replace the default instance name, or if there are multiple instances on the same machine.

Follow Microsoft's guidelines when defining the Named Instance, and ensure that it:

- Begins with a letter

- Does not include more than 16 characters

Setting a named instance automatically adds the instance name to SQLServerAgent (computer name) and to MSSQL Service as follows:

- SQLServerAgent: SQLAgent$<instance name>

- MSSQL Service: MSSQL$<instance name>

b. Instance Root Directory: Use the default path; change only if needed.

12 Server Configuration > Service AccountsFor each service, define the Account Name and Password, the Startup Type, and additional settings.

For the SQL Server Agent service:

Set the Startup Type to Automatic.

NOTE For reasons of security, use Named Instance as a best practice.




For servers hosting Application and Contact Database, set Share Permissions for the following folders:

Read/Write permissions:

ApplicationDataMigration

ContactDataMigration

Tools\Binn directory located in %ProgramFiles%\Microsoft SQL Server (exact path is dependent on SQL Server version)

Read permissions:

CommonDBShare

NOTE An SQL Credentials service if defined, should have the same shared permissions for the same folders as the SQL Server Agent service account.

NOTE Services Account requirements: Refer to the Technology, Security, & Network Integration Deployment Reference Guide.SQL Server Installation on domain controllers: If you are installing SQL Server 2014 on the domain controller, refer to limitations outlined in the Technology, Security, & Network Integration Deployment Reference Guide.Manually configure remote SQL Server 2014, page 42: For service account configurations for remote or cluster SQL servers.




13 Server Configuration > Collation tab.

a. For the Database Engine, click Customize, and select Windows collation designator and sort order.

b. Define the collation using these guidelines:

Collation designator: Set the collation according to what is specified in the Site Preparation Checklist (SPC), or according to your database administrator.

Case-sensitive: Clear (do not select).

Accent-sensitive: Select.

Remaining options (Binary, Binary-code point, Kana-sensitive, Width-sensitive) options should be clear (not selected). If there is a specific reason to select one of these options, consult your database administrator.

c. Click OK, and then click Next.

14 Database Engine Configuration > Server ConfigurationDefine the authentication mode and the built-in SQL server administrator account.

a. Below Authentication Mode, click Windows Authentication Mode. Mixed mode is also supported.

b. Below Specify SQL Server administrators, click Add, and then select the Database Management Account.

IMPORTANT SQL collation is not supported.




15 Database Engine Configuration > Data DirectoriesDo one of the following:

If the SQL Server is installed locally, continue from Step 16.

If the SQL Server is installed remotely, modify the Temp DB directory and Temp DB log directory fields according to the requirements specified in the Customer Furnished Equipment (CFE) Guide.

16 Reporting Services Configuration Below Reporting Services Native Mode, click Install only, and then click Next.




17 Feature Configuration Rules

The rule check runs automatically and when completed, the Ready to Install page appears.

18 Ready to Installa. Verify that the settings for Prerequisites, General Configuration, and

Instance Configuration are correct.

b. If needed, click Back to access the settings you want to change.

c. Click Install.

19 Installation ProgressMonitor the progress of the installation.

20 CompleteDo the following:

a. Verify that each feature shows a status of Succeeded.

b. Click Close.

Chapter 2 - Install SQL Server 2014 Post-installation procedures



Post-installation proceduresAfter installing SQL Server 2014, you must perform post-installation procedures:

Workflow1 Modify the SQL Server port (mandatory), page 28

2 Keep Model DB size at 128 MB or lower, page 30




6 Disable CEIP, page 34

7 Configure the SQL Server 2014 online help, page 35


9 Add SQL Server trace flags, page 38

10 Enable Optimize for Ad Hoc Workloads option, page 41

11 Enable remote access, page 41

12 Manually configure remote SQL Server 2014, page 42

13 Set SQL Server Security Features, page 48

14 Install SQL Performance Dashboard, page 50 (optional)

Modify the SQL Server port (mandatory)The system does not support dynamic ports. If the SQL Server was installed with a named instance, you must modify the SQL Server port.

In general, the default instance of SQL Server listens for requests from SQL Server clients on port 1433.

Procedure1 For Windows 2012, from the Start desktop, click SQL Server Configuration

Manager.2 In the left pane, expand SQL Server Network Configuration, and select

Protocols for Impact360.

3 In the right pane, verify that Shared Memory and TCP/IP protocols are enabled.

NOTE The example illustrations show SQL 2012.

Chapter 2 - Install SQL Server 2014 Modify the SQL Server port (mandatory)



4 Double-click TCP/IP.

5 In the TCP/IP Properties window, click the IP Addresses tab.

6 Scroll down to IP All, and do the following:

a. Clear the TCP Dynamic Ports field.

b. Set the TCP port to 1433.

c. Click OK.

NOTE For TCP/IP Sockets, data transmissions are more streamlined and have less overhead. Data transmissions can also take advantage of TCP/IP Sockets performance enhancement mechanisms, such as windowing and delayed acknowledgements, which can be very beneficial in a slow network. Depending on the type of applications, such performance differences can be significant.TCP/IP Sockets also support a backlog queue, which can provide a limited smoothing effect compared to named pipes, which may lead to pipe busy errors when you are attempting to connect to SQL Server.

IMPORTANT Use 1433 as the default TCP port unless you need to set a different port for security reasons. You must verify that the port you set is not used by other services.

Chapter 2 - Install SQL Server 2014 Keep Model DB size at 128 MB or lower



7 Restart all SQL services.

Keep Model DB size at 128 MB or lowerIf you have increased the Model DB size, you must return its size back to 128 MB (the default size) or smaller before proceeding with the WFO installation. WFO fails to install if the Model DB size is greater than 128MB. If you require a larger DB model, please contact Technical Support for assistance.

Grant Database Administrator permissionsYou can add Management Service Accounts (MSA) and/or Database Management Service Accounts (DMSA). The Database Management Service Account requires Database Administrator permissions.

Procedure1 For Windows 2012, from the Start desktop, click SQL Server Management

Studio.

2 In the Connect to Server window, do the following:

a. In the Server type list, select Database Engine.

b. In the Server name list, select the SQL server name.

c. In the Authentication list, select Windows Authentication. Mixed mode is also supported.

Chapter 2 - Install SQL Server 2014 Grant Database Administrator permissions



3 Below Object Explorer, expand Security > Logins.

4 Below Logins, verify that the Management Service Account and/or the Database Management Service Account exists in the list, and do one of the following:

If the required Service Account exists, continue from Step 6.

If the required Service Account does not exist, continue with Step 5.

5 Do the following:

a. Right-click Logins, and click New Login.

b. In the Login name field, type the name of the Management Service Account or the Database Management Service Account, or click Search and select the account.

NOTE Group names are not supported as Login names.




c. Click OK.

The Management Service Account or the Database Management Service Account is added to the Logins list.

6 Double-click the Service Account you added.

7 In the Login Properties window, verify that the Default language is set to English.




8 From the list of Select a page options on the left, click Server Roles.

9 Do one of the following:

For a Management Service Account, continue from Step 10.

On the Server Roles page, select the sysadmin server role.

10 Under Select a page, click the Status page.

11 Under Permission to connect to database engine, select the Grant option.

12 Click OK.

Chapter 2 - Install SQL Server 2014 Install the latest SQL Server 2014 service pack



Install the latest SQL Server 2014 service pack At the time of publication, Service Pack 1 is available for SQL Server 2014, and must be installed.

Procedure1 Download the latest service pack for SQL Server 2014, as specified in the Customer

Furnished Equipment (CFE) Guide, or in the Microsoft Update Bulletin Support Cumulative Update Bulletin, which is updated and released on a monthly basis.

2 Install the latest service pack for SQL Server 2014.

Install the latest SQL Server 2014 hotfixYou must download the latest hotfix for SQL Server 2014.

Procedure1 Find the latest service pack and hotfixes for SQL Server 2014 on Microsoft Support.

SQLSecurity.com.

2 Download the relevant file. Make sure to select a platform with x64 suffix.

3 Run the downloaded file.

Disable CEIPCustomer Experience Improvement Program (CEIP) collects information about how customers use Microsoft programs and about some of the problems they encounter. Microsoft uses this information to improve the products and features customers use

IMPORTANT Make sure to select a platform with x64 suffix.

http://www.sqlsecurity.com/faqs-1/sql-server-versions/sql-server-2012

Chapter 2 - Install SQL Server 2014 Configure the SQL Server 2014 online help



most often and to help solve problems. The system requires that you disable the CEIP feature.

Procedure1 From the notification area, click the Customer Feedback icon.

2 In the Microsoft SQL Server Customer Feedback Options window, click the No. I don't wish to participate option, and then click OK.

Configure the SQL Server 2014 online helpBy default, the SQL Server online help first searches for help topics on the Internet. If the topic is not found, the system searches the local machine. Configuring local help avoids delays when the Internet connection is disabled on the machine.

Procedure1 In Microsoft SQL Management Studio, on the Help menu, click Manage Help

Settings.

2 Click Choose online or local help.

3 Select I want to use local help and click OK.

Chapter 2 - Install SQL Server 2014 Install SQL Server 2005 backward compatibility components



Install SQL Server 2005 backward compatibility components

The backward compatibility components are used by the system’s troubleshooting tools (%impact360softwaredir%\DBTools). They are not mandatory during runtime, but may be required for troubleshooting purposes.

Procedure1 Browse to the Microsoft site download page.

http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

2 Download the SQLServer2005_BC_x64.msi file.


Example: Install SQL Server 2005 backward compatibility components

The backward compatibility components work with SQL Server 2008/R2 and 2012.

Procedure1 Double-click the SQLServer2005_BC_x64.msi file.

2 In the Welcome window, click Next.

3 In the License Agreement window, click the I accept the terms in the license agreement option, and click Next.

IMPORTANT Make sure to select the file with the x64 suffix.


Chapter 2 - Install SQL Server 2014 Example: Install SQL Server 2005 backward compatibility components



4 In the Registration Information window, type the Name and Company, and click Next.

5 In the Feature Selection window, without changing the default settings, click Next.

Chapter 2 - Install SQL Server 2014 Add SQL Server trace flags



6 In the Ready to Install Program window, click Install.

7 In the Completing Setup window, click Finish.

Add SQL Server trace flagsSQL Server trace flags are used to change SQL Server behavior, and help diagnose performance issues.




Trace flag descriptions Trace Flag 9481 enables backward compatibility for the cardinality estimator. This

trace flag is mandatory to ensure that the databases use the older and not the new version of the cardinality estimator introduced in SQL Server 2014 which may adversely affect query performance. For detailed information, see Microsoft’s article on Cardinality Estimation (SQL Server).

Trace Flag 1118 forces uniform extent allocations instead of mixed page allocations. This trace flag is commonly used to assist in TEMPDB scalability by avoiding SGAM and other allocation contention points.

Trace Flag 1117 enables increasing all data files simultaneously, and by the exact same size.

Trace Flag 2371 enables the auto update statistics feature so that the larger the table, the lower the threshold to trigger an update of the statistics. This is best practice when there are tables that contain more than several million records.


Manager.2 Click SQL Server Services.

3 On the right pane, right-click the SQL Server service, and click Properties.

IMPORTANT It is mandatory to add Trace Flag 9481 to ensure the best query performance.

https://msdn.microsoft.com/en-us/library/dn600374.aspx




4 In the SQL Server Properties window, click the Startup Parameters tab.

5 In the Specify a startup parameter field, enter each flag in turn, and click Add.

-T9481 -T1118 -T1117 -T2371

6 Click the Advanced tab, and verify that the Startup Parameters row contains the keys. Each flag is delimited by a semicolon. Select the right column in order to view the full list. Open and close the window to refresh the list.

7 After entering the new flags, press Enter to close the parameters panel, review the panel for confirmation of your changes, then click Apply.

8 On the Warning dialog informing you the changes will not take effect until the service is restarted, click OK.

9 Restart the SQL Server service.

Chapter 2 - Install SQL Server 2014 Enable Optimize for Ad Hoc Workloads option



Enable Optimize for Ad Hoc Workloads optionThe TSQL code enables the Optimize for Ad Hoc Workloads option by changing the setting to 1.

Procedure1 Open the SQL Server Management Studio and connect to the database.

2 Click on New and select Query with Current Connection.

3 Paste the following TSQL code into the new query window:

sp_configure 'show advanced options', 1

go

reconfigure

go

sp_configure 'optimize for ad hoc workloads', 1

go

reconfigure

go

4 Click Execute.

The query results panel displays a message indicating that the option was configured successfully, as in the following message:

Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

Configuration option 'optimize for ad hoc workloads' changed from 0 to 1. Run the RECONFIGURE statement to install.

Enable remote accessThe remote access server configuration option, when set to 1, allows local stored procedures to be run from a remote server or remote stored procedures to be run from the local server.

Procedure1 Open the SQL Server Management Studio and connect to the database.

2 Click on New and select Query with Current Connection.

Chapter 2 - Install SQL Server 2014 Manually configure remote SQL Server 2014



3 Paste the following TSQL code into the new query window, and click Execute.


go

reconfigure

go

sp_configure 'remote access', 1

go

reconfigure

go

4 Click Execute.

The query results panel displays a message indicating that the option was configured successfully, as in the following example:



Manually configure remote SQL Server 2014For remote SQL Servers, configured either as separate servers or as SQL server clusters, you need to manually configure several settings. These settings are automatically configured as required on installation for local SQL Servers. It is the customer’s responsibility to configure the settings for remote SQL Servers, and to modify the settings as required for local SQL installations.

For remote SQL configuration settings, see:

Remote SQL Server configuration settings, page 42

Remote SQL Cluster configuration settings, page 44

Remote SQL Server configuration settings

The table describes the settings you must configure manually after installing remote SQL Server 2014.

Chapter 2 - Install SQL Server 2014 Remote SQL Server configuration settings



Settings/operations not relevant for remote SQL Server installations are indicated as such at the end of the table.

SQL Server Setting Recommended Value for Remote SQL Installation

max degree of parallelism

1Required when SQL Server runs on a computer with more than one microprocessor or CPU to detect the best degree of parallelism (that is, the number of processors employed to run).

cost threshold for parallelism

15

xp_cmdshell By default, the xp_cmdshell option is disabled.It is recommended that you do not change the default value.xp_cmdshell is an essential mechanism to execute arbitrary calls in the system using either the SQL Server context (i.e. the Windows account used to start the service), or a proxy account configured to execute xp_cmdshell using different credentials.

optimize for ad hoc workloads

true (for SQL 2008 and higher)See Enable Optimize for Ad Hoc Workloads option, page 41.

tempdb devices Define four tempdb devices. The tempdb is a global resource available to all users connected to the instance of SQL Server.Recommended pre-allocation configuration:

Data file: Four files of equal size; value calculated using the storage calculator divided by four.Auto grow = true, incremental = 1GB, max size = 150% of file size

Log file: One file of 10 GB; auto grow = true, incremental = 1GB, max size = 10 GB.

remote SQL server account configurations

Set according to individual company policies since the system does not use the SQL Server Browser.

SQL Server trace flags

Add the following trace flags:-T9481-T1118-T1117-T2371See Add SQL Server trace flags, page 38.

network protocols Enable shared memory and TCP/IP

Chapter 2 - Install SQL Server 2014 Remote SQL Cluster configuration settings



Remote SQL Cluster configuration settings

If remote SQL server clusters are configured, verify that the configuration meets software requirements.

security flag Validate the SQL Credential object’s ability to run scripts on the server. The object is created on assigning database permissions to the service accounts. Perform these steps for the SQL Credential or for the default user:1 In the Registry Editor browse to

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings\HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Script Host\Settings\

2 Validate that there is a Settings folder. If not create one.

The following settings or operations are not relevant for remote SQL Server installations:

clr enabled: Must be enabled for local SQL Servers to enable the database to log information in log files for audit and debugging purposes.

Add maintenance group

Deploy UltraLoggerCLR.dll

Ultra Logger Registration (.lmf +.dll) on a machine which contains DB-related roles

Confirm Allow Updates is set to 0 (default) during installation and configuration


Remote SQL Cluster Required Configuration

Windows 2012 64-bit Database server

Configure as cluster

SQL Server Standard/Enterprise 2014 64-bit


Free disk space on the SQL cluster shared storage

Must meet requirements in the CFE Guide.

Chapter 2 - Install SQL Server 2014 Remote SQL Cluster configuration settings



Related informationMicrosoft Download Center: SQL Server Management Studio Express

SSIS component Install on each SQL cluster node.On installing SQL cluster, SSIS is automatically installed only on the active node. After installation, you must manually install SSIS, Management Studio and Development tools on every other node in the cluster.

SQL service packs and hotfixes

Install all the latest service packs and hotfixes.

ServerName attribute in the SSIS configuration file

Must point to the company-installed SQL server instance, for remote SQL Server with multiple instances or cluster configuration. See Update ServerName attribute for multiple instances/cluster configuration of remote SQL server, page 46.

User rights assignments to SQL services account

See Verify user rights assignments to SQL Services account, page 12.

Database administrator permissions

See Grant Database Administrator permissions, page 30.

Set SQL Service accounts

See Step 12 in Install SQL Server 2014.

Create directory on cluster shared storage for Database platform installation

The directory is used during the Database platform installation for the Database and Transaction Log directory destinations.For example, T:\Impact360\Databases

Management Client on DBMS

Install the SQL Server Management Studio (SQLManagementStudio_x64_ENU.exe) or SQLManagementStudio_x86_ENU.exe) on the Database Management Server. When and if remote connection is required, the customer can provide credentials. This file is available for download from Microsoft.

Shared Management Objects on DBMS

Install and deploy the Shared Management Objects installer package (SharedManagementObjects.msi) on the Database Management Server. The file is available for download from Microsoft.


http://www.microsoft.com/en-us/download/details.aspx?id=42299

Chapter 2 - Install SQL Server 2014 Update ServerName attribute for multiple instances/cluster configuration of remote SQL



Update ServerName attribute for multiple instances/cluster configuration of remote SQL server

If a remote SQL Server is configured with multiple instances or is configured as an SQL server cluster, the ServerName attribute in the SQL Server Integration Services (SSIS) configuration file must point to the company-installed SQL server instance, instead of to the customer-installed instances.

Company-installed: single SQL Server instance

Customer-installed: multiple SQL Server instances

To modify the SSIS configuration file:1 On the remote SQL server, from the folder %ProgramFiles%\Microsoft SQL

Server\110\DTS\Binn, access the following configuration file: MsDtsSrvr.ini.xml

2 In the <ServerName> XML element in the configuration file (see example below), replace the period (.) with one of the following values:

NOTE This configuration is only relevant when multiple SQL server instances are running on the remote SQL server. If only one SQL server instance is running on the remote SQL server or if using a local SQL server, this attribute should not be modified.

Chapter 2 - Install SQL Server 2014 Update ServerName attribute for multiple instances/cluster configuration of remote SQL



If the remote SQL server hosts multiple SQL server instances, replace the period in the <ServerName> XML element with the following:

<Machine Name>\<SQL Server Instance Name>

where:

<Machine Name> is the name of the server hosting the multiple SQL server instances

<SQL Server Instance Name> is the name of the company-installed SQL server instance

If the remote SQL server hosts an SQL server cluster, replace the period in the <ServerName> XML element with the following:

<IP of SQL Server or Name of Cluster>\<SQL Server Instance Name>where:

<IP of SQL Server or Name of Cluster> is the IP address of the SQL server managing the SQL services, or the name defined for the cluster


SSIS configuration file (Example)

3 Restart the SSIS.

Chapter 2 - Install SQL Server 2014 Set SQL Server Security Features



Set SQL Server Security FeaturesThis table lists the SQL Server security settings. The settings recommended by Microsoft are listed in comparison to what is required by the system.

When the system requires a different setting than is recommended by Microsoft, ensure to change the setting from the default Windows value to what is required by the system.

Policy Setting Microsoft Recommended Security Settings

System Security Settings

Ad Hoc Distributed Queries off off

CLR enabled (Used for logging)

off (if not used) on - for local SQL Serversoff - for remote SQL Servers

Cross database ownership chaining

off off

Database Mail XPs off off

Ole Automation Procedures

off off

Remote admin connections(Allows DAC connections from remote servers)

off off

Replication XPs off off

SQL Mail XPs off off

xp_cmdshell off off

Direct catalog updates off off

audit logon failed logins or all logins failed logins only

Built-in /Administrator remove remove

Database ownership chaining

off off

Guest in user database remove remove

EXECUTE permissions on extended stored procedures that are documented

remove from public remove from public

Remove all permission from public


Chapter 2 - Install SQL Server 2014 Set SQL Server Security Features



Service accounts Run SQL Server services with dedicated account

Run SQL Server services with dedicated account

Authentication mode Require Windows Authentication

Require Windows Authentication Mode

Strong passwords Always assign a strong passwords

Always assign a strong passwords

SA login disable(System Administrator cannot be removed or renamed)

Disable the SA account Disable the SA account.Enable during installation only

Choose static ports for named instances

Assign static ports to named instances


Remove sample databases Remove sample databases Remove sample databases

Surface and feature reduction(SQL browser service is not needed. The system work with address and port, and not with SQL instance name)

Run services and features needed in your environment only


Administrator reduction(SysAdmin role is required by the Database Management service account during install/upgrade until first successful enterprise configuration)

Restrict membership of the SysAdmin fixed server role to a few trusted individuals


Agent XPs(The Agent node is not displayed unless these extended stored procedures are enabled)

not specified off



Chapter 2 - Install SQL Server 2014 Install SQL Performance Dashboard



Install SQL Performance DashboardOptional. Installing the SQL Server Performance Dashboard can help with diagnostic evaluations of CPU issues, when and if needed.

At present, there is no Performance Dashboard for SQL 2014. You can use the Microsoft download for SQL 2012 to install the dashboard on the SQL Server.

Related informationMicrosoft® SQL Server® 2012 Performance Dashboard Reports

remote access (Applies to servers added using sp_addserver. Included for backward compatibility.)

not specified on

allow updates Option allow updates option should be removed from all scripts

allow updates option should be removed from all scripts




C h a p t e r 3

Upgrade to SQL Server 2014

The upgrade to SQL Server 2014 chapter details instructions for in-place upgrade from SQL Server 2008/2008 R2/2012 to SQL Server 2014 Enterprise or Standard Edition (ENT/STD), according to system requirements and the customer license.

Once the upgrade is complete, the previous management tools remain on the server.

SQL Server Configuration Manager and SQL Server Profiler is replaced.


Upgrade checklist, page 53


Post-upgrade SQL Server 2014, page 56

Chapter 3 - Upgrade to SQL Server 2014 Microsoft links



Microsoft linksMicrosoft links to help you prepare and upgrade SQL Server. Click a link based on the information you are looking for.

Upgrade to SQL Server 2014

https://msdn.microsoft.com/en-US/library/bb677622(v=sql.120).aspx

Supported Version and Edition Upgrades

https://msdn.microsoft.com/en-US/library/ms143393(v=sql.120).aspx

Upgrade to SQL Server 2014 Using the Installation Wizard (Setup)


Latest SQL Server 2014 downloads, including feature packs:


https://msdn.microsoft.com/en-US/library/ms143393(v=sql.120).aspx



https://msdn.microsoft.com/en-US/library/bb677622(v=sql.120).aspx

Chapter 3 - Upgrade to SQL Server 2014 Upgrade checklist



Upgrade checklistThe checklist provides a checklist for upgrading to SQL Server 2014 and an estimate of the time required to complete each step in the upgrade procedure.

* The estimated time is based on a lab test with the following configuration:

Server type - Consolidated (deployment level L1)

CPU - 2 x Quad Core

Memory-16GB

Disks - HP System Smart Array, RAID 1 (Transaction Log), RAID 5 (DB files).

SQL Server - version 2014 with max memory 2 GB

Status Step Procedure Estimated Time

1 Verify prerequisites, page 54 5 minutes

2 Create SQL Server database backup

Make sure that you have a valid backup of SQL Server system (master, msdb) and the system databases participating in the upgrade process.

Depends on the database size and data storage type

3 Upgrade to SQL Server 2014

Follow Microsoft guidelines.

40 minutes

4 Post-upgrade SQL Server 2014, page 56

Depends on the database size.

For example, for a Central Contact Database with 5 million calls, it takes 10 minutes.*

Chapter 3 - Upgrade to SQL Server 2014 Verify prerequisites



Verify prerequisitesVerify that you meet the prerequisites before you install SQL Server 2014.

Workflow1 SQL Server 2014 requirements

The customer must prepare the site for the SQL Server 2014 upgrade according to the Technology, Security, & Network Integration Deployment Reference Guide. See the SQL Server Requirements section in the Third-Party Products chapter.

2 Verify user rights assignments to SQL Services account, page 54

3 Verify minimum software requirements, page 54

4 Prepare SSRS for an SQL Server upgrade, page 55

Verify user rights assignments to SQL Services accountVerify that you have the necessary permissions for the Database Service Account.

Each of the following policies must include the service account running the SQL Server Database Engine service:

Lock pages in memory Log on as a service Perform volume maintenance tasks policy

Verify minimum software requirementsVerify that you meet the minimum software requirements before upgrading to SQL Server 2014:

Microsoft Windows



Windows Installer 4.5 is installed by the Installation Wizard, if not already installed on the computer. If you are prompted to restart your computer, restart it, and then restart SQL Server 2014 setup.exe.

.NET Framework 3.5 SP1 or higherNote that .NET Framework 4.0 installs automatically during the installation.


Related topicsInstall .Net 3.5 Framework SP1 on Windows 2012, page 14

Chapter 3 - Upgrade to SQL Server 2014 Prepare SSRS for an SQL Server upgrade



Prepare SSRS for an SQL Server upgradePrior to upgrading SQL Server, modify the SSRS configuration to disable custom settings that can block the SQL server upgrade.

Perform this task only when SSRS is hosted together with the SQL Server instance you are upgrading.

Procedure1 Identify the SQL Server Instance ID targeted for upgrade.

a. Launch the Reporting Services Configuration Manager.b. Connect to the Report Server Instance.

c. In the Report Server Status screen copy the Instance ID.

2 Navigate to %IMPACT360SOFTWAREDIR%\SSRS\Util using a command line.

3 Run the following command:

4 ReportingServicesUtils.Shell.exe /ssrspreupgrade ssrsinstancename:<Instance ID>

5 Perform the procedures to configure SSRS.

Related topicsConfigure SSRS, page 181

Chapter 3 - Upgrade to SQL Server 2014 Post-upgrade SQL Server 2014



Post-upgrade SQL Server 2014After upgrading to SQL Server 2014, perform the post-upgrade procedures according to the workflow.

Workflow1 Grant Database Administrator permissions, page 56

2 Install latest SQL Server 2014 service packs & hotfixes, page 59



5 Configure the SQL Server 2014 Online Help, page 60

6 Verify SQL Server trace flags, page 60

7 Manual configuration for remote SQL Server 2014, page 62

8 Update statistics, page 68

9 Modify database compatibility level, page 68

10 Run DBCC UPDATEUSAGE, page 69

11 Update system environment path variable, page 70

12 Verify SSRS, page 70

13 Redistribute the EM configuration, page 70



Studio.





Chapter 3 - Upgrade to SQL Server 2014 Grant Database Administrator permissions







5 Do the following:




Chapter 3 - Upgrade to SQL Server 2014 Grant Database Administrator permissions



c. Click OK.




Chapter 3 - Upgrade to SQL Server 2014 Install latest SQL Server 2014 service packs & hotfixes









12 Click OK.

Install latest SQL Server 2014 service packs & hotfixesInstall the latest service pack and hotfixes available for SQL Server 2014.

Keep Model DB size at 128 MB or lowerIf you have increased the Model DB size, you must return its size back to 128 MB (the default size) or smaller before proceeding with the WFO installation. WFO fails to install

Chapter 3 - Upgrade to SQL Server 2014 Disable CEIP



if the Model DB size is greater than 128MB. If you require a larger DB model, please contact Technical Support for assistance.

Disable CEIPCustomer Experience Improvement Program (CEIP) collects information about how our customers use Microsoft programs and about some of the problems they encounter. Microsoft uses this information to improve the products and features customers use most often and to help solve problems.

If this feature is not disabled, make sure you disable it. See Disable CEIP, page 34.

Configure the SQL Server 2014 Online HelpBy default, the SQL Server online help searches for help topics on the Internet first. If the topic is not found, the system searches the local machine. When the Internet connection is disabled on the machine, the internet search causes a long delay.

Procedure1 From the Microsoft SQL Management Studio’s Help tab, open Manage Help

Settings.

2 Click Choose Online or Local Help.

3 Select the Local radio button, and click OK.

4 Select I want to use local help and click OK.

Verify SQL Server trace flagsSQL Server trace flags are used to change SQL Server behavior, and help diagnose performance issues.

Configure the following trace flags:

Trace Flag 9481 enables backward compatibility for the cardinality estimator. This trace flag is mandatory to ensure that the databases use the older and not the new version of the cardinality estimator introduced in SQL Server 2014 which may adversely affect query performance. For detailed information, see Microsoft’s article on Cardinality Estimation (SQL Server).

Trace Flag 1118 forces uniform extent allocations instead of mixed page allocations. This trace flag is commonly used to assist in TEMPDB scalability by avoiding SGAM and other allocation contention points.

IMPORTANT It is mandatory to add Trace Flag 9481 to ensure the best query performance.

https://msdn.microsoft.com/en-us/library/dn600374.aspx

Chapter 3 - Upgrade to SQL Server 2014 Verify SQL Server trace flags







3 On the right pane, right-click the SQL Server service, and click Properties.

4 In the SQL Server Properties window, click the Startup Parameters tab.

5 In the Specify a startup parameter field, verify that each of the following flags are defined:

-T9481 -T1118 -T1117 -T2371

Chapter 3 - Upgrade to SQL Server 2014 Verify Ad Hoc Workloads and remote access settings



Verify Ad Hoc Workloads and remote access settingsVerify that Optimize for Ad Hoc Workloads and remote access are enabled for SQL Server 2014. The Optimize for Ad Hoc Workloads option is relevant if you are upgrading from SQL Server 2012.

Procedure1 Open the SQL Server Management Studio.

2 To verify that Optimize for Ad Hoc Workloads option is enabled, do the following:

a. Type the following query:

SELECT name, value_in_use FROM sys.configurations WHERE name = 'optimize for ad hoc workloads'

b. Verify that the value is set to 1.

c. If not, enable the option as described in Enable Optimize for Ad Hoc Workloads option, page 41.

3 To verify that remote access is enabled, do the following:

a. Type the following query:

SELECT name, value_in_use FROM sys.configurations WHERE name = 'remote access'

b. Verify that the value is set to 1.

c. If not, enable remote access as described in Enable remote access, page 41.

Manual configuration for remote SQL Server 2014For remote SQL Servers, configured either as separate servers or as SQL server clusters, you need to manually configure several settings. These settings are automatically configured as required on installation for local SQL Servers.It is the customer’s responsibility to configure the settings for remote SQL Servers, and to modify the settings as required for local SQL installations.

For remote SQL configuration settings, see:

Remote SQL Server configuration settings, page 63

Remote SQL cluster requirements, page 65

Chapter 3 - Upgrade to SQL Server 2014 Remote SQL Server configuration settings



Remote SQL Server configuration settings

The table describes the settings you must configure manually after upgrading to remote SQL Server 2014. Settings/operations not relevant for remote SQL Server upgrades are indicated as such at the end of the table.


max degree of parallelism

1Required when SQL Server runs on a computer with more than one microprocessor or CPU to detect the best degree of parallelism (that is, the number of processors employed to run).

cost threshold for parallelism

15

xp_cmdshell By default, the xp_cmdshell option is disabled.It is recommended that you do not change the default value.xp_cmdshell is an essential mechanism to execute arbitrary calls in the system using either the SQL Server context (i.e. the Windows account used to start the service), or a proxy account configured to execute xp_cmdshell using different credentials.

optimize for ad hoc workloads

true (for SQL 2008 and higher)See Verify Ad Hoc Workloads and remote access settings, page 62.

tempdb devices Define four tempdb devices. The tempdb is a global resource available to all users connected to the instance of SQL Server.Recommended pre-allocation configuration:

Data file: Four files of equal size; value calculated using the storage calculator divided by four.Auto grow = true, incremental = 1GB, max size = 150% of file size

Log file: One file of 10 GB; auto grow = true, incremental = 1GB, max size = 10 GB.

remote SQL server account configurations

Set according to individual company policies since the system does not use the SQL Server Browser.

Chapter 3 - Upgrade to SQL Server 2014 Remote SQL Server configuration settings



SQL Server trace flags

Add the following trace flags:-T9481-T1118-T1117-T2371See Verify SQL Server trace flags, page 60.

network protocols Enable shared memory and TCP/IP

security flag Validate the SQL Credential object’s ability to run scripts on the server. The object is created on assigning database permissions to the service accounts. Perform these steps for the SQL Credential or for the default user:1 In the Registry Editor browse to

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings\HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Script Host\Settings\

2 Validate that there is a Settings folder. If not create one.

The following settings or operations are not relevant for remote SQL Server installations:

clr enabled: Must be enabled for local SQL Servers to enable the database to log information in log files for audit and debugging purposes.

Add maintenance group

Deploy UltraLoggerCLR.dll




Chapter 3 - Upgrade to SQL Server 2014 Remote SQL cluster requirements



Remote SQL cluster requirements

If remote SQL server clusters are configured, verify that the configuration meets software requirements.


Windows 2012 64-bit Database server


SQL Server Standard/Enterprise 2014 64-bit


Free disk space on the SQL cluster shared storage

Must meet requirements in the CFE Guide.

SSIS component Install on each SQL cluster node.On installing SQL cluster, SSIS is automatically installed only on the active node. After installation, you must manually install SSIS, Management Studio and Development tools on every other node in the cluster.

SQL service packs and hotfixes

Install all the latest service packs and hotfixes

ServerName attribute in the SSIS configuration file

Must point to the company-installed SQL server instance, for remote SQL Server with multiple instances or cluster configuration. See Update ServerName attribute for multiple instances/cluster configuration of remote SQL server, page 66.

User rights assignments to SQL services account

See Verify user rights assignments to SQL Services account, page 54.

Database administrator permissions

See Grant Database Administrator permissions, page 56.

Set SQL Service accounts

See Step 12 in Install SQL Server 2014.

Chapter 3 - Upgrade to SQL Server 2014 Update ServerName attribute for multiple instances/cluster configuration of remote



Related informationMicrosoft Download Center: SQL Server Management Studio Express

Update ServerName attribute for multiple instances/cluster configuration of remote SQL server

If a remote SQL Server is configured with multiple instances or is configured as an SQL server cluster, the ServerName attribute in the SQL Server Integration Services (SSIS) configuration file must point to the company-installed SQL server instance, instead of to the customer-installed instances.

Company-installed: single SQL Server instance

Create directory on cluster shared storage for Database platform installation

The directory is used during the Database platform installation for the Database and Transaction Log directory destinations.For example, T:\Impact360\Databases

Management Client on DBMS (optional)

Install SQL Server Management Studio Express on the Database Management Server to save time on support queries for remote SQL Server deployments. When and if remote connection is required, the customer can provide credentials.



Chapter 3 - Upgrade to SQL Server 2014 Update ServerName attribute for multiple instances/cluster configuration of remote



Customer-installed: multiple SQL Server instances

To modify the SSIS configuration file:1 On the remote SQL server, from the folder %ProgramFiles%\Microsoft SQL



If the remote SQL server hosts multiple SQL server instances, replace the period in the <ServerName> XML element with the following:

<Machine Name>\<SQL Server Instance Name>where:

<Machine Name> is the name of the server hosting the multiple SQL server instances


If the remote SQL server hosts an SQL server cluster, replace the period in the <ServerName> XML element with the following:


<IP of SQL Server or Name of Cluster> is the IP address of the SQL server managing the SQL services, or the name defined for the cluster



NOTE This configuration is only relevant when multiple SQL server instances are running on the remote SQL server. If only one SQL server instance is running on the remote SQL server or if using a local SQL server, this attribute should not be modified.

Chapter 3 - Upgrade to SQL Server 2014 Update statistics



3 Restart the SSIS.

Update statisticsTo update statistics in user-defined tables, do one of the following:

Option 1 - Run a stored procedure:This option provides a minimal log at the end of the process.

For each Impact360 SQL Server database, run the sp_updatestats stored procedure.

Option 2 - Run a script:This option provides a minimal log at the end of the process.

Run the following script:EXEC sp_MSforeachtable 'UPDATE STATISTICS ? WITH FULLSCAN'

Option 3 - Run a script with progress status:This option provides a detailed log for each table during the process.

To run the update statistics with a progress status for each table, run the following script:SET NOCOUNT ONDECLARE @database_name sysname, @tablename NVARCHAR(128), @sql NVARCHAR(300),

@from_table int, @to_table int SET @from_table =1IF OBJECT_ID('tempdb.dbo.#tables') is not Null drop table #tables SELECT table_name into #tables FROM information_schema.tables WHERE

TABLE_TYPE = 'BASE TABLE' AND table_name NOT IN (SELECT DISTINCT object_name(id) as exclude_name

FROM sys.sysindexes WHERE name like '_WA_Sys_%') ORDER BY 1ALTER TABLE #tables ADD seq INT IDENTITYSELECT @to_table= max(seq) FROM #tablesWHILE @from_table<=@to_tableBEGIN SELECT @tablename= table_name FROM #tables where seq=@from_table SET @sql = 'UPDATE STATISTICS [' + @tablename + '] WITH FULLSCAN' EXEC sp_executesql @sql SET @sql='UPDATED STATISTICS for table: ' + @tablename RAISERROR (@sql, 0, 1) WITH NOWAIT SET @from_table=@from_table+1END

Modify database compatibility levelTo optimize the execution plan of each stored procedure, it is the recommended best practice to change the Compatibility level of the upgraded database.

Chapter 3 - Upgrade to SQL Server 2014 Run DBCC UPDATEUSAGE



Procedure1 Open the SSMS 2014, connect to the Impact 360 instance.

2 From Object Explorer, click Databases, and for each Impact 360 user database (not System Databases), do the following:

a. Right-click the database, and select Properties.

b. On the Properties page, select Options.

c. From the Compatibility level, select SQL Server 2014.

Run DBCC UPDATEUSAGEDBCC UPDATEUSAGE updates page or row counts or both for all objects in the current database. Run DBCC UPDATEUSAGE for each database, in turn.

Procedure Type:

DBCC UPDATEUSAGE (0);

GO

where 0 indicates to update the current database.

Chapter 3 - Upgrade to SQL Server 2014 Update system environment path variable



Update system environment path variable After upgrading from the SQL Server 2008/2008 R2/2012 to 2014, the value of the Path variable in the Windows system Environment Variables is updated with the SQL Server 2014 path. To enable database tools utility work with the correct path order, you must move the SQL server 2014 path before that of SQL server 2008/2008 R2/2012.

The following SQL Server 2014 path is added:

C:\Program Files\Microsoft SQL Server\120\DTS\Binn\ C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\

The new path is added after the SQL server 2008/2008 R2/2012 path:

C:\Program Files\Microsoft SQL Server\<100 or110>\DTS\Binn\ C:\Program Files (x86)\Microsoft SQL Server\<100 or110>\DTS\Binn\

Procedure1 Open System Properties > Advanced tab and click Environment Variables.

2 In System Variables, double-click the Path variable to edit and move the SQL server 2014 path to the top of the list.

Verify SSRSAfter upgrading SQL Server, verify the SSRS configuration has adopted the new instance ID and new SQL server version.

Related topicsVerify SSRS configuration post SQL upgrade, page 192

Redistribute the EM configurationAfter upgrading to SQL Server 2014, you must re-distribute the configuration for each server role hosting a database in the Enterprise Manager (EM).

Procedure1 Log on to the WFO application.

2 Click System Management > Enterprise Management > Settings.

3 In the Installations tree (left pane), select the server role you want to configure.

4 Change the server role as needed, and then click Save. The Server Role Restart window displays if any services or applications require a restart.

NOTE In this example, the installation folder is C:\Program Files\.

Chapter 3 - Upgrade to SQL Server 2014 Redistribute the EM configuration



5 Click Continue to save all settings data, and then manually restart any services or applications listed in the Server Role Restart window.

6 Repeat for each database server role.

C h a p t e r 4

Install SQL Server 2012

This section provides detailed instructions for installing SQL Server 2012 Enterprise or Standard Edition (ENT/STD), according to system requirements and the customer license.




Install SQL Server 2012, page 79


Chapter 4 - Install SQL Server 2012 Microsoft links




Latest SQL Server 2012 downloads, including feature pack:



http://msdn.microsoft.com/en-us/library/ms177440.aspx

Opening the firewall ports for SQL Server on Windows Server:

https://msdn.microsoft.com/en-us/library/cc646023.aspx



https://msdn.microsoft.com/en-us/library/cc646023.aspx

Chapter 4 - Install SQL Server 2012 Installation checklist



Installation checklistThe checklist provides a list of SQL Server 2012 installation procedures and an estimate of the time required to complete each procedure.

Status Step Procedure Mandatory Estimated Time (minutes)

1 Verify prerequisites, page 75 5

2 Install SQL Server 2012, page 79 40


10


5


20


10


8 Configure the SQL Server 2012 help, page 98

5


10


2

11 Enable remote access, page 104 10

Chapter 4 - Install SQL Server 2012 Verify prerequisites



Verify prerequisitesPrerequisites must be met before you install SQL Server 2012.

Workflow1 SQL Server requirements

The customer is required to prepare the site for the SQL Server installation according to the Technology, Security, & Network Integration Deployment Reference Guide. See the SQL Server Requirements section inside the Third-Party Products chapter.

2 Open firewall ports for SQL Server

3 Verify user rights assignments to SQL Services account, page 75: Verify the user rights assignments for the SQL services account that is running the SQL Server Database Engine service.

4 Verify minimum software requirements, page 76: Ensure that the minimum software requirements are met before you install SQL Server 2012.

5 Calculate max memory, page 78: Install SQL Server 2012


Verify user rights assignments to SQL Services accountVerify the user rights assignments for the SQL services account that is running the SQL Server Database Engine service.

Procedure1 In Windows 2012, go to Control Panel > System and Security >

Administrative Tools > Local Security Policy.



Chapter 4 - Install SQL Server 2012 Verify minimum software requirements



3 Double-click Lock pages in memory and verify that the list includes the service account running the SQL Server Database Engine service.

4 Double-click Log on as a service and verify that the list includes the service account running the SQL Server Database Engine service.

5 Double-click Perform volume maintenance tasks and verify that the list includes the service account running the SQL Server Database Engine service.

Related informationSQL Services Account Requirements (Technology, Security, & Network Integration Deployment Reference Guide)

Verify minimum software requirementsEnsure that the minimum software requirements are met before you install SQL Server 2012.




Windows Installer 4.5 can be installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then restart SQL Server 2012 setup.exe.

.NET Framework 3.5 SP1 or later.

.NET Framework 4.0 installs automatically during the installation.


Related topicsInstall .NET 3.5 Framework SP1 on Windows 2012, page 77

Chapter 4 - Install SQL Server 2012 Install .NET 3.5 Framework SP1 on Windows 2012



Install .NET 3.5 Framework SP1 on Windows 2012

Install .NET 3.5 Framework SP1 on the database server. The procedure used to install the framework varies depending on the version of Windows server currently running.

Procedure1 Insert the Windows Server installation DVD in the drive.

2 Open a command prompt as an administrator.

3 Type the following command:

dism /online /enable-feature /featurename:NetFX3 /all /Source:d:\sources\sxs /LimitAccess

where d:\sources\sxs is your Windows installation DVD.

Upon completion, the following message is displayed.

Enabling feature(s)

[=======================100.0%======================]

The operation completed successfully.

4 Open Server Manager.

5 On the Manage menu, click Add Roles and Features.

6 On the Before you begin page, click Installation Type.

7 On the Select installation type page, click Role-based or feature-based installation, and then click Next.

8 On the Select destination server page, select the server that SQL Server 2012 will be installed on, and then click Next.

9 Click Features.

Chapter 4 - Install SQL Server 2012 Calculate max memory



10 On the Select features page, under Features, select .NET Framework 3.5 Features.

You do not need to select HTTP Activation or Non-HTTP Activation.

11 Click Next.12 On the Confirm installation selections page, click Specify an alternate source

path, and then enter the source path specified in Step 3.

Once the installation is complete, the following is displayed under Features.

Calculate max memoryFor local SQL Server installations on consolidated platforms only, the CommonSB plugin automatically calculates the memory required according to a predefined formula. Customers can override the automatic calculation by changing the value of the registry key.

Formula for max memory calculationThe maximum memory required for the SQL Server is calculated according to the formula:

((APP * (total - (6144 + (IFA + ITS) * 4096))) + (1 - APP) * (total - 2048) * 0.75)where:

total is the total RAM on the server in MB.

APP, IFA, and ITS are the server roles that can be configured on the server, and must be set to either 1 if configured, or 0 if not configured.

APP is a Framework Applications server role


ITS is the Speech Transcription Server

Override automatic memory calculationA customer can manually override the automatic max memory calculation, and set the maximum memory according to their own calculation. This is achieved by ignoring the automatic plugin memory configuration.

To override the automatic max memory calculation, do the following:

1 Locate the registry key:


2 Set IsSqlServerLocal to False.

IMPORTANT The formula for max memory calculations are not applicable to remote SQL Server installations.




Install SQL Server 2012Install SQL Server 2012 using the SQL Server Installation Wizard and the specific settings as outlined in this procedure.

Procedure1 Insert the SQL Server 2012 installation media into the DVD drive.

2 Open the drive and run setup.exe.

3 Select Installation, and then select New SQL Server stand alone installation or add features to an existing installation.

4 In the Installation Type window, select Perform a new installation of SQL Server.2012 is selected by default. Click Next.

5 Enter the Product Key, and click Next.6 Click I accept the license terms, and click Next. Do not click “Send feature usage

data to Microsoft.”

7 In the Setup Support Rules window, once the discovery operation to check the server configuration is complete, click Show Details.

8 In the Setup Support Rules window, wait until the status of all the rules is Passed, and click OK.




9 In the Product Updates window,

a. Wait until the latest SQL Server updates are installed, or click Skip Scan.

b. Click Next.10 In the Install Setup Files window, wait until the Setup process is complete.

11 In the Setup Support Rules window,

a. Wait until the rule check completes, and click Show Details.

b. Wait until the status of all the rules is Passed, and click Next.

The Setup Support Rules must all pass.




12 In the Setup Role window, click SQL Server Feature Installation, and click Next.

13 In the Feature Selection window, select these mandatory features:

The feature list can change for different SQL Server editions.




Reporting Services Native (SharePoint is not supported):






If required, modify the Shared Features directory, and click Next.




14 In the Installation Rules window,

a. Wait until the rule check is complete, and click Show Details.b. Wait until the status of all the rules is Passed, and click Next.

15 In the Instance Configuration window, select default or named instance.

Default Instance: you can have one default instance per machine. The default instance name is MSSQLServer.

Named Instance: you can set a named instance (such as Impact360) in place of the default name, or when there are multiple instances on the same machine. Use Microsoft guidelines when naming the instance, and ensure that:

- Must begin with a letter

- Must not include more than 16 characters




Instance Root Directory: It is preferable to use the default path; edit it if desired.




16 The Disk Space Requirements window calculates the required disk space for the features that you specify. Then it compares the required space to the available disk space. Click Next.

17 In the Server Configuration window Service Accounts tab, enter the Account Name and Password for each service, and configure the Startup Type and more settings for each service.




SQL Services Account Requirements: SQL services account definition requirements are listed in the Technology, Security, & Network Integration Deployment Reference Guide.

SQL Server Installation on domain controllers: If you are installing SQL Server 2012 on the domain controller, refer to limitations outlined in the Technology, Security, & Network Integration Deployment Reference Guide.

Remote SQL Server configuration recommendations, page 107: For service account configurations for remote or cluster SQL servers.

Refer to SQL Server 2008 R2 / 2012 Security Best Practices.

18 Click the Collation tab. For the Database Engine,

a. Click Customize, and select Windows collation designator and sort order.b. Define the collation using these guidelines:

Collation designator: Set the collation according to what is specified in the Site Preparation Checklist (SPC), or according to your database administrator.

Case-sensitive: Clear (do not select).

Accent-sensitive: Select.

Remaining options (Binary, Binary-code point, Kana-sensitive, Width-sensitive) options are not selected. If there is a specific reason to select one of these options, consult your database administrator.

Service Startup Type

Settings

SQL Server Agent

Automatic The SQL Server Agent is a member of the SQL sysadmin fixed server role, as described in Microsoft Article ID: 143504.Set folders with Share Permissions on the servers hosting the Application and Contact Databases:Set read/write folder permissions: ApplicationDataMigration ContactDataMigration Tools\Binn directory located in

%ProgramFiles%\Microsoft SQL Server (exact path depends on SQL Server version)

Set Read permissions for these folders: CommonDBShare

SQL Server Database Engine

Automatic


http://download.microsoft.com/download/1/2/A/12ABE102-4427-4335-B989-5DA579A4D29D/SQL_Server_2008_R2_Security_Best_Practice_Whitepaper.docx




19 Click OK, and then click Next.20 In the Database Engine Configuration window, set the Server Configuration

tabs to define the authentication mode and the built-in SQL Server administrator account.

a. Under Authentication Mode, click Windows Authentication Mode. Mixed mode is also supported.

b. Under Specify SQL Server administrators, click Add, and then select the Database Management Account.




21 Select the Data Directories tab and modify the default path of the database files.

If the SQL Server is installed locally, you do not need to modify any fields on this tab. Skip to Step 22.

If the SQL Server is installed remotely, modify the Temp DB directory and Temp DB log directory fields. Refer to the requirements specified in the Customer Furnished Equipment (CFE) Guide.

No further updates are required on this tab.




22 Click the FILESTREAM tab, which enables FILESTREAM for transact-SQL access. Do not change the default settings. Click Next.

23 In the Reporting Services Configuration window, under Reporting Services Native Mode, click Install only, and then click Next.




24 In the Error Reporting window, clear the option so that no information is sent to Microsoft, and click Next.

25 In the Installation Configuration Rules window,



26 In the Ready to Install window, review the Prerequisites, General Configuration, and Instance Configuration details for accuracy, and then click Install.




27 In the Installation Progress window, you can monitor the progress of the installation. After installation, the Complete page shows a Succeeded status for each feature. Click Close.

The installation is complete. Microsoft SQL Server 2012 appears under All apps containing the SQL Server tools, services, and documentation.




28 When installing SQL Server 2012 on a new Windows Server 2012 installation, if this message may appear:

The error occurs when .NET Framework 3.5 is not installed and enabled. To resolve the issue, manually enable .NET Framework 3.5 from the command prompt and then run the SQL Server installation process by repeating the steps in this chapter.

Related topicsInstall .NET 3.5 Framework SP1 on Windows 2012, page 77

Chapter 4 - Install SQL Server 2012 Post-installation procedures



Post-installation proceduresAfter installing SQL Server 2012, perform the post-installation procedures according to the workflow.






6 Resolve out of memory error, page 97


8 Configure the SQL Server 2012 help, page 98





13 SQL Server 2012 local and remote SQL configurations, page 105

14 Microsoft Download Center, page 111

15 Install SQL Performance Dashboard, page 114 (optional)

Modify the SQL Server port (mandatory)The system does not support dynamic ports. If the SQL Server was installed with a named instance (not the default one), you must modify the SQL Server port.


Procedure1 If Windows 2012, from the Start desktop, click SQL Server Configuration

Manager.2 In the left pane, expand SQL Server Network Configuration, and select

Protocols for Impact360.

3 In the right pane, verify that Shared Memory and TCP/IP protocols are enabled.

Chapter 4 - Install SQL Server 2012 Modify the SQL Server port (mandatory)





6 Under IP All, modify the TCP port according to your preference.

Set the port to (default) 1433 unless for security reasons you need to set a different port.

Verify that the port you set is not used by other services.

NOTE For TCP/IP Sockets, data transmissions are more streamlined and have less overhead. Data transmissions can also take advantage of TCP/IP Sockets performance enhancement mechanisms, such as windowing and delayed acknowledgements, which can be beneficial in a slow network. Depending on the type of applications, such performance differences can be significant.TCP/IP Sockets also support a backlog queue, which can provide a limited smoothing effect compared to named pipes, which may lead to pipe busy errors when you are attempting to connect to SQL Server.

Chapter 4 - Install SQL Server 2012 Keep Model DB size at 128 MB or lower



7 Clear the TCP Dynamic Ports field.

8 Click OK.


Keep Model DB size at 128 MB or lowerIf you have increased the Model DB size, you must return its size back to 128 MB (the default size) or smaller before proceeding with the WFO installation. WFO fails to install if the Model DB size is greater than 128MB. If you require a larger DB model, please contact Technical Support for assistance.



Studio.












5 Do the following:







c. Click OK.













12 Click OK.

Chapter 4 - Install SQL Server 2012 Install the latest SQL Server 2012 service pack



Install the latest SQL Server 2012 service packAt the time of publication, Service Pack 1 is available for SQL Server 2012, and must be installed.

Procedure1 Download the latest service pack for SQL Server 2012, as specified in the Customer

Furnished Equipment (CFE) Guide, or in the Microsoft Update Bulletin Support Cumulative Update Bulletin, which is updated and released on a monthly basis.

2 Install the latest service pack for SQL Server 2012.

Install the latest SQL Server 2012 hotfixDownload the latest hotfix for SQL Server 2012.

Procedure1 Browse to the latest service pack and hotfixes for SQL Server 2012 found in

SQLSecurity.com.

2 Click the relevant link to display the Microsoft site download page.



Resolve out of memory errorInstall the fix for an out of memory error. The error occurs when using ODBC with SQL Server.

Related informationhttp://support.microsoft.com/kb/2667742


The system requires that you disable the CEIP feature.

IMPORTANT Make sure to select a platform with x64 suffix.

http://www.sqlsecurity.com/faqs-1/sql-server-versions/sql-server-2012


Chapter 4 - Install SQL Server 2012 Configure the SQL Server 2012 help



Procedure1 From the notification area, at the rightmost of the taskbar, select the Customer

Feedback icon.

2 In the Microsoft SQL Server Customer Feedback Options window, click the No. I don’t wish to participate option, and then click OK.

Configure the SQL Server 2012 helpBy default, the SQL Server help searches for help topics on the Internet first. If the topic is not found, the system searches the local machine. When the Internet connection is disabled on the machine, the Internet search causes a long delay.

Procedure1 In Microsoft SQL Management Studio, on the Help menu, click Manage Help

Settings.

2 Click Choose Online or Local Help.

3 Select the Local option, and click OK.

Chapter 4 - Install SQL Server 2012 Install SQL Server 2005 backward compatibility components




The backward compatibility components are used by the system troubleshooting tools (%impact360softwaredir%\DBTools). They are not mandatory during run time, but are required for troubleshooting.

Procedure1 Browse to the Microsoft site download page.





The backward compatibility components works with SQL Server 2008/R2 and 2012.




IMPORTANT Make sure to select the file with the x64 suffix.






5 On the Feature Selection window, without changing the default settings, click Next.




6 On the Ready to Install Program window, click Install.

7 On the Completing Setup window, click Finish.




Add SQL Server trace flagsSQL Server trace flags are used to change SQL Server behavior. Trace flags can also be used to help diagnose performance issues.

Trace flag descriptions Trace Flag 1118 forces uniform extent allocations instead of mixed page allocations.

The trace flag is commonly used to help with TEMPDB scalability by avoiding SGAM and other allocation contention points.



Procedure1 If Windows 2012, from the Start desktop, click SQL Server Configuration


3 In the right pane, right-click the SQL Server service, and click Properties.

4 On the SQL Server Properties window, click the Startup Parameters tab.

Chapter 4 - Install SQL Server 2012 Enable Optimize for Ad Hoc Workloads option



5 In the Specify a startup parameter field, enter each flag in turn, and click Add.

-T1118 -T1117 -T2371

6 Click the Advanced tab, and verify that the Startup Parameters row contains the keys. Each flag is delimited by a semicolon. Select the right column to view the full list. Open and close the window to refresh the list.

7 After entering the new flags, press Enter to close the parameters panel, review the panel for confirmation of your changes, then click Apply.

8 On the Warning dialog informing you the changes will not take effect until the service is restarted, click OK.




2 Click New Query.

Chapter 4 - Install SQL Server 2012 Enable remote access





go

reconfigure

go


go

reconfigure

go

Result:Absence of an error message indicates success. In the results pane a message similar to this is displayed in the query results panel:





2 Click New Query.



go

reconfigure

go


go

reconfigure

go

Chapter 4 - Install SQL Server 2012 SQL Server 2012 local and remote SQL configurations



Result:Absence of an error message indicates success. In the query results pane a message similar to this is displayed:



SQL Server 2012 local and remote SQL configurationsThe table below lists the operations automatically performed during the installation process on local SQL servers.

As shown, most configurations are not performed on remote SQL servers (except for one configuration, Ultra-Logger Registration, as listed below). It is the customer responsibility to configure remote SQL Server settings, and to modify any configurations that were set on local SQL servers during installation.

For many of the operations listed below, “Remote SQL Server configuration recommendations” on page 107 describes the specific recommendations for how to define these in the remote SQL servers (which settings, and so on).

The Remote SQL Server Configuration Recommendations column indicates for which settings this section describes recommendations, and for which settings no recommendations are given (indicated by N/A).

Operation Local SQL Server

Remote SQL Server

Remote SQL Server Configuration Recommendations

Set max degree of parallelism (=1) -

Configured During Installation

Not Configured During Installation

Yes—see “Remote SQL Server configuration recommendations” on page 107

Set clr enabled (=1) Configured During Installation


N/A

NOTE: The clr enabled parameter must be enabled for Local SQL servers to enable the database capability of logging information to log files for audit and debugging purposes.

Set cost threshold for parallelism (=15)




Chapter 4 - Install SQL Server 2012 SQL Server 2012 local and remote SQL configurations



Set xp_cmdshell (=0) Configured During Installation



Set optimize for ad hoc workloads




Define Four TempDB devices (physical data files)




Define SQL Server account configurations




Add maintenance group Configured During Installation


N/A

Configure SQL Server trace flags: -T1118, -T1117, -T2371




Deploy UltraLoggerCLR.dll Configured During Installation


N/A




N/A

Configure max server memory





Remote SQL Server


Chapter 4 - Install SQL Server 2012 Remote SQL Server configuration recommendations



Remote SQL Server configuration recommendations

The following provides the best practices for remote SQL servers or cluster configurations, which is the customer’s responsibility:

Define Four TempDB Devices:

The tempdb system database is a global resource that is available to all users connected to the instance of SQL Server and is used to hold the following:

Temporary user objects that are explicitly created.

For example: global or local temporary tables, temporary stored procedures, table variables, or cursors.

Internal objects that are created by the SQL Server Database Engine.

For example: work tables to store intermediate results for spools or sorting.

Row versions that are generated by data modification transactions in a database that uses read-committed using row versioning isolation or snapshot isolation transactions.

Row versions that are generated by data modification transactions for features.

For example: online index operations, Multiple Active Result Sets (MARS), and AFTER triggers.

Recommended pre-allocation configuration:




N/A

Grant permission to run scripts on remote server.





Remote SQL Server


File type

Number of files

File size Auto Grow

Data 4 Refer to the CFE Guide for TempDB sizes

True, incremental=1GB, Max Size = 150% of file size

Log 1 10GB True, incremental=1GB, Max Size = 10GB

Chapter 4 - Install SQL Server 2012 Remote SQL Server configuration recommendations



Max Server Memory

Limiting the SQL max memory is done primarily to protect other processes that run on the machine from interfacing memory starvation.

The pseudo code for the formula is: Max Memory = (Physical RAM - 2GB) x 0.7.

Max degree of parallelism

When SQL Server runs on a computer with more than one microprocessor or CPU, it detects the best degree of parallelism, that is, the number of processors employed to run a single statement, for each parallel plan execution.

MAX DOP = 1 XP_cmdshell SPs

xp_cmdshell is an essential mechanism for executing arbitrary calls into the system using either the SQL Server context (i.e. the Windows account used to start the service) or a proxy account that can be configured to execute xp_cmdshell using different credentials.

By default, the xp_cmdshell option is disabled. It is recommended that you do not change the default value.

Optimize for ad hoc workloads (SQL 2008 or higher)

Optimize for ad hoc workloads=true Define Remote SQL Server Account Configurations

Cost Threshold for ParallelismCost threshold for parallelism = 15

Configure SQL Server Trace Flags -T1118, -T845Add the SQL Server Trace Flags -T1118, -T845

Network protocols

Enable shared memory and TCP/IP Configure SQL Server Trace Flag -T1117 Configure SQL Server Trace Flags -T2371 Validate the SQL Credential object ability to run scripts on the server. The object is

created when assigning database permissions to the service accounts. Perform these steps for the SQL Credential or for the default user:

a. In the Registry Editor browse to,

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings\

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Script Host\Settings\

b. Validate that there is a Settings folder, or create one.

Remote SQL servers can be configured as separate servers, or as SQL Server clusters or farms.

NOTE The system does not use the SQL Server Browser, so this service can be set according to individual company policies.

Chapter 4 - Install SQL Server 2012 Remote SQL cluster requirements



For more information on requirements for remote SQL Server clusters, see “Remote SQL cluster requirements” on page 109.

Remote SQL cluster requirements

If remote SQL Server clusters are configured, verify that the following requirements are met:

Windows 2012 64-bit of the Database server is configured as a cluster.

SQL Server Standard/Enterprise 2012 64 bit is configured as a cluster.

Sufficient free disk space on the SQL cluster shared storage according to the CFE Guide.

Each SQL cluster node must be installed with SSIS component.

When installing SQL cluster, the SSIS component is installed only on the active node. Therefore, the SSIS, Management Studio, and the Development tools must be also installed on each cluster node manually. This installs the SSIS 32-bit.

The ServerName attribute in the SSIS configuration file must be modified (see “Remote SQL Server with multiple instances or cluster configuration” on page 110).

The latest SQL service packs and hotfix must be installed.

In addition, perform the following procedures:

1 “Verify user rights assignments to SQL Services account” on page 75.

2 “Grant Database Administrator permissions” on page 93.

3 “Install SQL Server 2012” on page 79.

Chapter 4 - Install SQL Server 2012 Remote SQL Server with multiple instances or cluster configuration



4 Set the SQL Service accounts. For details, see “Install SQL Server 2012” on page 79.

5 Set the SQL Collation. For details, see “Install SQL Server 2012” on page 79.

6 Create a directory on the cluster shared storage (for example, T:\Impact360\Databases). This directory is used during the Database platform installation for the Database and Transaction Log directory destinations.

Remote SQL Server with multiple instances or cluster configuration

If a remote SQL Server is configured with multiple instances or an SQL Server cluster, it is required to update the ServerName attribute in the SQL Server Integration Services (SSIS) configuration file to point to the company-installed SQL Server instance (as opposed to the customer-installed instances).

Company-installed: a single SQL Server instance only is installed

Customer-installed: multiple SQL Server instances can be installed

To modify the SSIS configuration file:1 On the remote SQL Server, from the folder %ProgramFiles%\Microsoft SQL



If the remote SQL Server hosts multiple SQL Server instances, replace the period in the <ServerName> XML element with the following:


<Machine Name> is the name of the server hosting the multiple SQL Server instances

<SQL Server Instance Name> is the name of the company-installed SQL Server instance

If the remote SQL Server hosts an SQL Server cluster, replace the period in the <ServerName> XML element with the following:


<IP of SQL Server or Name of Cluster> is the IP address of the SQL Server managing the SQL services, or the name defined for the cluster


NOTE This configuration is only relevant when multiple SQL Server instances are running on the remote SQL Server. If only one SQL Server instance is running on the remote SQL Server or if using a local SQL Server, this attribute should not be modified.

Chapter 4 - Install SQL Server 2012 Install Management Client and Shared Management Objects on DBMS




3 After updating the MsDtsSrvr.ini.xml configuration file, restart the SSIS.

Install Management Client and Shared Management Objects on DBMS

When customers that deploy a remote SQL Server require support, it is time saving to have the SQL Server Management Studio (SQLManagementStudio_x64_ENU.exe) or SQLManagementStudio_x86_ENU.exe) installed on the Database Management Server. When and if remote connection is required, the customer can provide credentials. This file is available for download from Microsoft.

When customers are deploying a remote SQL server, it is required to install and deploy the Shared Management Objects installer package (SharedManagementObjects.msi) on the Database Management Server. The file is available for download from Microsoft.

Related information Microsoft Download Center


Chapter 4 - Install SQL Server 2012 Set SQL Security Features



Set SQL Security FeaturesThis table lists the SQL Server security settings. The settings recommended by Microsoft are listed in comparison to what is required by the system.








off off



off off


off off



xp_cmdshell off off





off off






Chapter 4 - Install SQL Server 2012 Set SQL Security Features






















not specified off



Chapter 4 - Install SQL Server 2012 Install SQL Performance Dashboard



Install SQL Performance DashboardThis is an optional post installation procedure to install the SQL Server Performance Dashboard to assist with future diagnostic evaluations of CPU issues.

Use the Microsoft download to install the dashboard on the SQL Server.

Related informationMicrosoft SQL Server 2012 Performance Dashboard Reports


not specified on






C h a p t e r 5

Install SQL Server 2008/R2

This section provides detailed instructions for installing SQL Server 2008/R2 Enterprise or Standard Edition (ENT/STD), according to system requirements and the customer license.



Verifying prerequisites, page 118

Install SQL Server 2008/R2, page 122


Chapter 5 - Install SQL Server 2008/R2 Microsoft links




Latest SQL Server 2008/R2 SP and hotfix list:

http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx

SQL Server 2005 Backward Compatibility:




Opening the firewall ports for SQL Server on Windows Server 2008:






Chapter 5 - Install SQL Server 2008/R2 Installation checklist



Installation checklistThe checklist provides a list of SQL Server 2008/R2 installation procedures and an estimate of the time required to complete each procedure.

Status Step Procedure Mandatory Estimated Time (minutes)

1 Verifying prerequisites, page 118

5

2 Install SQL Server 2008/R2, page 122

40


10


5

5 Installing the latest SQL Server 2008/R2 service pack, page 140

20

6 Install the latest SQL Server 2008/R2 hotfix, page 145

10


8 Configure the SQL Server 2008/R2 online help, page 150

5


10


2


10

Chapter 5 - Install SQL Server 2008/R2 Verifying prerequisites



Verifying prerequisitesPrerequisites must be met before you install SQL Server 2008/R2.

Workflow1 SQL Server Requirements

The customer is required to prepare the site for the SQL Server installation according to the Technology, Security, & Network Integration Deployment Reference Guide. See the SQL Server Requirements section inside the Third-Party Products chapter.

2 Opening the Firewall Ports for SQL Server

The Firewall port required by the SQL Server must be open.

3 Verifying user rights assignments to SQL Services account, page 119: The SQL Services Account must be granted with log on as a Service permission.

4 Verifying minimum software requirements, page 119: Ensure that the minimum software requirements are met before installing SQL Server 2008/R2.

5 Calculate max memory, page 121: For local SQL Server installations on consolidated platforms only, the CommonSB plugin automatically calculates the memory required according to a predefined formula. Customers can override the automatic calculation by changing the value of the registry key.


Upgrade to SQL Server 2008 (V11.1 SP1 Technology, Security, and Networking Deployment Reference Guide)

IMPORTANT Customers running SQL Server 2005 must first upgrade to SQL 2008 using the relevant V11.1 documentation.


Chapter 5 - Install SQL Server 2008/R2 Verifying user rights assignments to SQL Services account



Verifying user rights assignments to SQL Services account

The SQL Services Account must be granted with log on as a Service permission.

Procedure1 Click Start > All Programs > Administrative Tools > Local Security Policy.


3 On the on the right side, perform the following:

a. Double-click the Lock pages in memory policy and verify that the list includes the SQL Services Account.

b. Double-click the Log on as a service policy and verify that the list includes the SQL Services Account.

Verifying minimum software requirementsEnsure that the minimum software requirements are met before installing SQL Server 2008/R2.



Chapter 5 - Install SQL Server 2008/R2 Install .NET 3.5 Framework SP1




Windows Installer 4.5 is installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then restart SQL Server 2008 setup.exe.

.NET Framework 3.5 SP1 or later—see “Install .NET 3.5 Framework SP1” on page 120

Install .NET 3.5 Framework SP1

1 From the desktop, right-click My Computer, and then click Manage. The Server Manager window opens.

2 On the Server Manager window, in the Server Manager tree, click Features, and then click Add features.

3 Select .NET Framework 3.5.1 features.

4 In the Add Features Wizard window, click Next.5 In the Confirm Installation Selections window, click Install.6 In the Installation Progress window, wait for the installation to complete, and

then click Next.7 In the Installation Results window, click Close.

Chapter 5 - Install SQL Server 2008/R2 Calculate max memory



Calculate max memoryFor local SQL Server installations on consolidated platforms only, the CommonSB plugin automatically calculates the memory required according to a predefined formula. Customers can override the automatic calculation by changing the value of the registry key.

Formula for max memory calculationThe maximum memory required for the SQL Server is calculated according to the formula:

((APP * (total - (6144 + (IFA + ITS) * 4096))) + (1 - APP) * (total - 2048) * 0.75)where:

total is the total RAM on the server in MB.

APP, IFA, and ITS are the server roles that can be configured on the server, and must be set to either 1 if configured, or 0 if not configured.

APP is a Framework Applications server role


ITS is the Speech Transcription Server

Override automatic memory calculationA customer can manually override the automatic max memory calculation, and set the maximum memory according to their own calculation. This is achieved by ignoring the automatic plugin memory configuration.

To override the automatic max memory calculation, do the following:

1 Locate the registry key:


2 Set IsSqlServerLocal to False.

IMPORTANT The formula for max memory calculations are not applicable to remote SQL Server installations.

Chapter 5 - Install SQL Server 2008/R2 Install SQL Server 2008/R2



Install SQL Server 2008/R2Install SQL Server 2008/R2 using the SQL Server Installation Wizard.

Procedure1 Insert the SQL Server 2008 installation media into the DVD drive. Open the drive

and run the setup.exe.

2 In the SQL Server Installation Center window, click Installation, and then click New SQL Server stand alone installation or add features to an existing installation.

3 In the Setup Support Rules window, wait until the System Configuration Checker runs a discovery operation on your computer and the status of all the rules is Passed, and then click OK.




4 On the Product Key window, type the product key, and click Next.

5 In the License Terms window, click I accept the license terms, and click Next.




6 In the Setup Support Files window, click Install.

7 The Setup Support Rules window opens and the System Configuration Checker verifies the system state of your computer before Setup continues.

If errors occur, fix the errors before you continue.

8 Click Next.




9 In the Feature Selection window, select these mandatory features (the feature list may change for different SQL Server editions):




Reporting Services






The remaining features are optional.

If required, modify the Shared Features directory, and click Next.

10 In the Instance Configuration window, select default or named instance.

Default Instance: you can have one default instance for each computer. The default instance name is MSSQLServer.




Named Instance: you can set a named instance (such as Impact360) in place of the default name, or when there are multiple instances on the same computer. Use Microsoft's guidelines when naming the instance, and ensure that:

- Must begin with a letter

- Must not include more than 16 characters




Instance Root Directory: It is preferable to use the default path; modify it if desired.

11 Click Next.12 The Disk Space Requirements window calculates the required disk space for the

features that you specify. Then it compares the required space to the available disk space. Click Next.

13 In the Server Configuration window, in the Services Accounts tab, type the Account Name and Password for each service, and configure the settings for each service.

SQL Services Account Requirements: The requirements for the SQL services account are listed in the Technology, Security, & Network Integration Deployment Reference Guide.

SQL Services settings: The table below lists the settings required for each service.




SQL Server Installation Requirements: If you are installing SQL Server on the domain controller, refer to limitations outlined in the Technology, Security, & Network Integration Deployment Reference Guide.

Remote SQL Server configuration recommendations, page 161: For service account configurations for remote or cluster SQL servers.

Refer to SQL Server 2008 R2 / 2012 Security Best Practices

14 Click the Collation tab. For the Database Engine,

a. Click Customize, and select Windows collation designator and sort order.b. Verify that the following settings are defined.

Collation designator: Set the collation according to what was specified for that language in the Site Preparation Checklist (SPC).

Case-sensitive: Cancel the selection (do not select)

Accent-sensitive: Select

Remaining options (Binary, Binary-code point, Kana-sensitive, Width-sensitive) should be unchecked (not selected). If there is a specific reason to select one of these options, consult system support.

Service Startup Type

Additional Settings

SQL Server Agent

Automatic The SQL Server Agent is a member of the SQL sysadmin fixed server role, as described in Microsoft Article ID: 143504.Set folders with Share Permissions on the servers hosting the Application and Contact Databases:Set read/write folder permissions: ApplicationDataMigration ContactDataMigration Tools\Binn directory located in

%ProgramFiles%\Microsoft SQL Server (exact path is dependent on SQL Server version)

Set Read permissions for these folders: CommonDBShare

SQL Server Database Engine

Automatic


http://download.microsoft.com/download/1/2/A/12ABE102-4427-4335-B989-5DA579A4D29D/SQL_Server_2008_R2_Security_Best_Practice_Whitepaper.docx




.

IMPORTANT The above figure displays an example collation. For the specific collation required, refer to the instructions in this step. For details about collation requirements, see the SQL Collation Requirements in the Technology, Security, & Network Integration Deployment Reference Guide.




15 Click OK.

16 On the Server Configuration screen, click Next.17 In the Database Engine Configuration window, set the Server Configuration tabs

to define the authentication mode and the built-in SQL Server administrator account.

a. Under Authentication Mode, click Windows Authentication Mode. Mixed mode is also supported.




b. Under Specify SQL Server administrator, click Add and select the Database Management Service Account.

18 Click the Data Directories tab to modify the default path of the database files.

If the SQL Server has been installed locally, there is no need to modify any fields on this tab. Proceed to the next step.

If the SQL Server has been installed remotely, modify the Temp DB directory and Temp DB log directory fields according to the requirements specified in the




Customer Furnished Equipment (CFE) Guide. No further updates are required on this tab.

19 The FILESTREAM tab enables FILESTREAM for transact-SQL access. Do not change the default settings. Click Next.

20 On the Error and Usage Reporting window, clear any of the options, so that no information is sent to Microsoft.

a. In the Reporting Services Configuration screen, select Install, but do not configure the report server.




When the SQL Server installation completes, a setup status report is displayed in this window. Additional details can be found in the logs in MSSQL/LOG directory.

21 Click Next.22 In the Installation Rules window, to display all the installed parts, click Show

details.




23 Click Next.24 In the Ready to Install window, click Next.25 In the Installation Progress window, when the installation completes, click Next.

26 In the Complete window, click Close.

Chapter 5 - Install SQL Server 2008/R2 Post-installation procedures



Post-installation proceduresAfter installing SQL Server 2008/R2, perform post-installation procedures:




4 Installing the latest SQL Server 2008/R2 service pack, page 140

5 Install the latest SQL Server 2008/R2 hotfix, page 145

6 Resolve out of memory error, page 149


8 Configure the SQL Server 2008/R2 online help, page 150





13 SQL Server 2008/R2 local and remote SQL configurations, page 159

Modify the SQL Server port (mandatory)The system does not support dynamic ports. If the SQL Server was installed with named instance (not the default one) you must modify the SQL Server port.


Procedure1 Click Start > Programs > Microsoft SQL Server 2008 > Configuration Tools >

SQL Server Configuration Manager.2 Expand the SQL Server Network Configuration and select Protocols for

Impact360.

3 Verify that Shared Memory and TCP/IP protocols are enabled.

Chapter 5 - Install SQL Server 2008/R2 Modify the SQL Server port (mandatory)




NOTE For TCP/IP Sockets, data transmissions are more streamlined and have less overhead. Data transmissions can also take advantage of TCP/IP Sockets performance enhancement mechanisms, such as windowing and delayed acknowledgements, which can be beneficial in a slow network. Depending on the type of applications, such performance differences can be significant.TCP/IP Sockets also support a backlog queue, which can provide a limited smoothing effect compared to named pipes, which may lead to pipe busy errors when you are attempting to connect to SQL Server.

Chapter 5 - Install SQL Server 2008/R2 Keep Model DB size at 128 MB or lower




6 Under IP All, modify the TCP port according to your preference. By default, set the port to 1433 unless for security reasons you need to set a different port. You must verify that the port you set is not used by other services.

7 Clear the TCP Dynamic Ports.

8 Click OK.


Keep Model DB size at 128 MB or lowerIf you have increased the Model DB size, you must return its size back to 128 MB (the default size) or smaller before proceeding with the WFO installation. WFO fails to install

Chapter 5 - Install SQL Server 2008/R2 Grant Database Administrator permissions



if the Model DB size is greater than 128MB. If you require a larger DB model, please contact Technical Support for assistance.



Studio.









5 Do the following:






c. Click OK.




Chapter 5 - Install SQL Server 2008/R2 Installing the latest SQL Server 2008/R2 service pack



12 Click OK.

Installing the latest SQL Server 2008/R2 service packDownload the latest service pack and hotfixes for SQL Server 2008/R2.

Procedure1 Download the latest service pack and hotfixes for SQL Server 2008/R2, as specified

in the Customer Furnished Equipment (CFE) Guide, or in the Microsoft Update Bulletin Support Cumulative Update Bulletin, which is updated and released on a monthly basis.


Example: Install SQL Server 2008/R2 SP1

This section provides an example for installing the following downloaded file: SQLServer2008SP1-KB968369-x64-ENU.exe.

Procedure1 Double-click the downloaded file and extract it to the local machine.

2 Run the setup file.

NOTE Make sure to select a platform with x64 suffix.

Chapter 5 - Install SQL Server 2008/R2 Example: Install SQL Server 2008/R2 SP1




4 In the License Agreement window, click the I accept the license terms option, and click Next.




5 On the Select Features window, without changing the default settings, click Next.




6 On the Check Files in Use window, click Next.

7 In the Ready to Update window, click Update.




8 In the Update Progress window, click Next.

9 In the Complete window, click Close.

Chapter 5 - Install SQL Server 2008/R2 Install the latest SQL Server 2008/R2 hotfix



Install the latest SQL Server 2008/R2 hotfixDownload the latest hotfix for SQL Server 2008/R2.

Procedure1 Browse to the latest service pack and hotfixes for SQL Server 2008/R2 found in:


2 Click the relevant link to display the Microsoft site download page.



Example: Install latest SQL Server 2008/R2 hotfix

This section provides an example for installing the following downloaded file: SQLServer2008-KB975977-x64.exe.

Procedure1 Double-click the downloaded file and extract it to the local machine.

2 Run the setup file.



Chapter 5 - Install SQL Server 2008/R2 Example: Install latest SQL Server 2008/R2 hotfix



4 In the License Terms window, select the I accept the license terms option, and then click Next.

5 In the Select Features window, without changing the defaults, click Next.




6 In the Check Files in Use window, click Next.

7 In the Ready to Update window, click Update.




8 In the Update Progress window, click Next.

9 In the Complete window, click Close, and then restart the machine.

Chapter 5 - Install SQL Server 2008/R2 Resolve out of memory error



Resolve out of memory errorInstall the fix for an out of memory error. The error occurs when using ODBC with SQL Server.

Related informationhttp://support.microsoft.com/kb/2667742


The system requires that you disable the CEIP feature.


Chapter 5 - Install SQL Server 2008/R2 Configure the SQL Server 2008/R2 online help



Procedure1 From the notification area, at the rightmost of the taskbar, select the Customer

Feedback icon.

2 In the Microsoft SQL Server Customer Feedback Options window, click the No. I don't wish to participate option, and then click OK.

Configure the SQL Server 2008/R2 online helpBy default, the SQL Server online help searches for help topics on the Internet first. If the topic is not found, the system searches the local computer. When the Internet connection is disabled on the computer, the internet search causes a long delay.

Chapter 5 - Install SQL Server 2008/R2 Configure the SQL Server 2008/R2 online help



Procedure1 Click Start > All Programs > Microsoft SQL Server 2008 > Microsoft SQL

Management Studio.

2 In the Connect to Server window,


b. In the Server name list, select the SQL Server name.


3 From the Tools menu, select Options.

4 Select Help > Online.

5 Select the Try Local only, not online option.

6 Click OK.

Chapter 5 - Install SQL Server 2008/R2 Install SQL Server 2005 backward compatibility components




The backward compatibility components are used by the system’s troubleshooting tools (%impact360softwaredir%\DBTools). They are not mandatory during run time, but may be required for troubleshooting purposes.

Procedure1 Browse to the following link to display the Microsoft site download page:





The backward compatibility components works with SQL Server 2008/R2 and 2012.



IMPORTANT Always download the file with _x64 in the file name.The file is for 64-bit systems.


Chapter 5 - Install SQL Server 2008/R2 Example: Install SQL Server 2005 backward compatibility components





Chapter 5 - Install SQL Server 2008/R2 Example: Install SQL Server 2005 backward compatibility components



5 On the Feature Selection window, without changing the default settings, click Next

6 In the Ready to Install Program, click Install.

Chapter 5 - Install SQL Server 2008/R2 Add SQL Server trace flags



7 On the Completing Setup window, click Finish.

Add SQL Server trace flagsSQL Server trace flags are used to change the behavior of SQL Server. Trace flags can also be used to help diagnose performance issues.

Trace flag descriptions Trace Flag 1118 forces uniform extent allocations instead of mixed page allocations.

The trace flag is commonly used to assist in TEMPDB scalability by avoiding SGAM and other allocation contention points.



Chapter 5 - Install SQL Server 2008/R2 Add SQL Server trace flags



Procedure1 Click Start > All Programs > Microsoft SQL Server 2008 > Configuration

Tools > SQL Server Configuration Manager2 Select SQL Server Services.

3 On the right side, right-click the SQL Server service, and click Properties.

4 In the Advanced tab on the SQL Server Properties window, double-click the Startup Parameters property.

At the end of the existing row of Startup parameters, enter a semi-colon (;) followed by the new flags: -T1118;-T1117; -T2371

NOTE A semicolon (;) is used as a delimiter between Startup parameters.

Chapter 5 - Install SQL Server 2008/R2 Enable Optimize for Ad Hoc Workloads option



5 After entering the new flags, press Enter to close the parameters panel, review the panel for confirmation of your changes, then press Apply.

6 A Warning dialog informs you that changes will be saved but will not take effect until after the service is restarted. Press Ok to close the service Properties window.




2 Click New Query.

NOTE This procedure is only relevant for SQL Server 2008 and higher.

Chapter 5 - Install SQL Server 2008/R2 Enable remote access





go

reconfigure

go


go

reconfigure

go






2 Click New Query.

NOTE This procedure is only relevant for SQL Server 2008 and higher.

Chapter 5 - Install SQL Server 2008/R2 SQL Server 2008/R2 local and remote SQL configurations





go

reconfigure

go


go

reconfigure

go




SQL Server 2008/R2 local and remote SQL configurations

The table below lists the operations automatically performed during the installation process on local SQL servers.

As shown, most configurations are not performed on remote SQL servers (with the exception of one configuration, Ultra Logger Registration, as listed below). It is the customer’s responsibility to configure remote SQL Server settings, and to modify any configurations that were set on local SQL servers during installation.

For many of the operations listed below, “Remote SQL Server configuration recommendations” on page 161 describes the specific recommendations for how to define these in the remote SQL servers (which settings, etc).

The Remote SQL Server Configuration Recommendations column below indicates for which settings this section describes recommendations, and for which settings no recommendations are given (indicated by N/A).

Chapter 5 - Install SQL Server 2008/R2 SQL Server 2008/R2 local and remote SQL configurations




Remote SQL Server


Set max degree of parallelism (=1) -




Set clr enabled (=1) Configured During Installation


N/A

Set remote access (=1)Not required from V11.1 SP1 and higher.



Required for distributed database deployments (levels L4 and higher)

NOTE: The clr enabled parameter must be enabled for Local SQL servers to enable the database capability of logging information to log files for audit and debugging purposes.

Set cost threshold for parallelism (=15)




Set xp_cmdshell (=0) Configured During Installation



Set optimize for ad hoc workloads (SQL 2008 or higher)




Define Four TempDB devices (physical data files)




Define SQL Server account configurations




Add maintenance group Configured During Installation


N/A

Chapter 5 - Install SQL Server 2008/R2 Remote SQL Server configuration recommendations



Remote SQL Server configuration recommendations

The following provides the best practices for remote SQL servers or cluster configurations, which is the customer’s responsibility:

Define Four TempDB Devices:

The tempdb system database is a global resource that is available to all users connected to the instance of SQL Server and is used to hold the following:

Temporary user objects that are explicitly created.

For example: global or local temporary tables, temporary stored procedures, table variables, or cursors.

Internal objects that are created by the SQL Server Database Engine.

For example: work tables to store intermediate results for spools or sorting.

Configure SQL Server trace flags: -T1118, -T1117, T2371




Deploy UltraLoggerCLR.dll Configured During Installation


N/A




N/A

Configure max server memory







N/A

Grant permission to run scripts on remote server.





Remote SQL Server


Chapter 5 - Install SQL Server 2008/R2 Remote SQL Server configuration recommendations



Row versions that are generated by data modification transactions in a database that uses read-committed using row versioning isolation or snapshot isolation transactions.

Row versions that are generated by data modification transactions for features.

For example: online index operations, Multiple Active Result Sets (MARS), and AFTER triggers.

Recommended pre-allocation configuration:

Max Server Memory

Limiting the SQL max memory is done primarily to protect other processes that run on the machine from interfacing memory starvation.

The pseudo code for the formula is: Max Memory = (Physical RAM - 2GB) x 0.7.

Max degree of parallelism

When SQL Server runs on a computer with more than one microprocessor or CPU, it detects the best degree of parallelism, that is, the number of processors employed to run a single statement, for each parallel plan execution.

MAX DOP = 1 XP_cmdshell SPs

xp_cmdshell is an essential mechanism for executing arbitrary calls into the system using either the SQL Server context (i.e. the Windows account used to start the service) or a proxy account that can be configured to execute xp_cmdshell using different credentials.

By default, the xp_cmdshell option is disabled. It is recommended that you do not change the default value.

Optimize for ad hoc workloads (SQL 2008 or higher)

Optimize for ad hoc workloads=true Define Remote SQL Server Account Configurations

Cost Threshold for Parallelism

File type

Number of files

File size Auto Grow

Data 4 Refer to the CFE Guide for TempDB sizes

True, incremental=1GB, Max Size = 150% of file size

Log 1 10GB True, incremental=1GB, Max Size = 10GB

NOTE The system does not use the SQL Server Browser, so this service can be set according to individual company policies.

Chapter 5 - Install SQL Server 2008/R2 Remote SQL Server cluster recommendations



Cost threshold for parallelism = 15 Configure SQL Server Trace Flags -T1118, -T845

Add the SQL Server Trace Flags -T1118, -T845 Network protocols

Enable shared memory and TCP/IP Configure SQL Server Trace Flag -T1117 Configure SQL Server Trace Flags -T2371 Validate the SQL Credential object’s ability to run scripts on the server. The object is

created when assigning database permissions to the service accounts. Perform these steps for the SQL Credential or for the default user:

a. In the Registry Editor browse to Computer\HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Script Host

b. Validate that there is a Settings folder. If not create one.

Remote SQL servers can be configured as separate servers, or as SQL Server clusters or farms.

For more information on requirements for remote SQL Server clusters, see “Remote SQL Server cluster recommendations” on page 163.

Remote SQL Server cluster recommendations

If remote SQL Server clusters are configured, verify that the following requirements are met:

Windows server of the Database server is configured as a cluster.

SQL Server Standard/Enterprise 2008 64 bit is configured as a cluster.

Sufficient free disk space on the SQL cluster shared storage according to the CFE Guide.

Each SQL cluster node must be installed with SSIS component.

When installing SQL cluster, the SSIS component is installed only on the active node. Therefore, the SSIS, Management Studio, and the Development tools must be also installed on each cluster node manually. This installs the SSIS 32-bit.

The ServerName attribute in the SSIS configuration file must be modified (see “Remote SQL Server with multiple instances or cluster configuration” on page 164).

The latest SQL service packs and hotfix must be installed.

Chapter 5 - Install SQL Server 2008/R2 Remote SQL Server with multiple instances or cluster configuration



In addition, perform the following procedures:

1 “Verifying user rights assignments to SQL Services account” on page 119.

2 “Grant Database Administrator permissions” on page 137.

3 “Install SQL Server 2008/R2” on page 122.

4 Set the SQL Service accounts. For details, see “Install SQL Server 2008/R2” on page 122.

5 Set the SQL Collation. For details, see “Install SQL Server 2008/R2” on page 122.

6 Create a directory on the cluster shared storage (for example, T:\Impact360\Databases). This directory is used during the Database platform installation for the Database and Transaction Log directory destinations.

Remote SQL Server with multiple instances or cluster configuration

If a remote SQL Server is configured with multiple instances or an SQL Server cluster, it is required to update the ServerName attribute in the SQL Server Integration Services (SSIS) configuration file to point to the company-installed SQL Server instance (as opposed to the customer-installed instances).

Company-installed: a single SQL Server instance only is installed

Customer-installed: multiple SQL Server instances can be installed

Chapter 5 - Install SQL Server 2008/R2 Remote SQL Server with multiple instances or cluster configuration



To modify the SSIS configuration file:1 On the remote SQL Server, from the folder %ProgramFiles%\Microsoft SQL



If the remote SQL Server hosts multiple SQL Server instances, replace the period in the <ServerName> XML element with the following:


<Machine Name> is the name of the server hosting the multiple SQL Server instances


If the remote SQL Server hosts an SQL Server cluster, replace the period in the <ServerName> XML element with the following:


<IP of SQL Server or Name of Cluster> is the IP address of the SQL Server managing the SQL services, or the name defined for the cluster



NOTE This configuration is only relevant when multiple SQL Server instances are running on the remote SQL Server. If only one SQL Server instance is running on the remote SQL Server or if using a local SQL Server, this attribute should not be modified.

Chapter 5 - Install SQL Server 2008/R2 Install Management Client and Shared Management Objects on DBMS



3 After updating the MsDtsSrvr.ini.xml configuration file, restart the SSIS.

Install Management Client and Shared Management Objects on DBMS

When customers that deploy a remote SQL Server require support, it is time saving to have the SQL Server Management Studio (SQLManagementStudio_x64_ENU.exe) or SQLManagementStudio_x86_ENU.exe) installed on the Database Management Server. When and if remote connection is required, the customer can provide credentials. This file is available for download from Microsoft.

When customers are deploying a remote SQL server, it is required to install and deploy the Shared Management Objects installer package (SharedManagementObjects.msi) on the Database Management Server. The file is available for download from Microsoft.

Related information Microsoft Download Center


Chapter 5 - Install SQL Server 2008/R2 Set SQL Security Features



Set SQL Security FeaturesThis table lists the SQL Server security settings. The settings recommended by Microsoft are listed in comparison to what is required by the system.








off off



off off


off off



xp_cmdshell off off





off off




























not specified off







not specified on





C h a p t e r 6

Install and Configure SSRS

SQL Server Reporting Service (SSRS) is required in both new and upgraded systems to support reporting in Customer Feedback, Workforce Management (WFM), Scorecards, eLearning and Coaching. It also supports Interactions and Analytics reporting.

Topics SSRS Guidelines, page 171

Install SSRS Reporting Service (Remote SQL), page 172

Add SSRS to an existing SQL Server Instance, page 178

Configure SSRS, page 181

Verify SSRS configuration post SQL upgrade, page 192

SSRS Encryption Keys Backup and Restore, page 193

Chapter 6 - Install and Configure SSRS SSRS Guidelines



SSRS GuidelinesSSRS installation and configuration is performed by the customer in all new and upgraded systems to support reporting in Customer Feedback, Workforce Management (WFM), Scorecards, eLearning, Coaching, Interactions, and Analytics.

SSRS: installation methodSSRS is installed as a SQL Server component during the SQL server installation on data center servers, or as a stand-alone SQL component on the database management platform when there is a remote SQL deployment.

SSRS: installation locationSSRS is installed on data center servers prior to installing platforms hosting the Reporting Services server role.

SSRS: account used to run the configurationThe account used to install and configure SSRS must be any customer account with:

local windows administrative rights

SQL administrative rights (sysadmin)

SSRS: SQL Server upgrade preparation and validationThe SSRS configuration must be modified before upgrading the SQL Server. Post SQL Server upgrade, the configuration needs to be validated.

SSRS ValidationsSSRS readiness is validated by the Server Readiness Tool.

SSRS: Management Account runs the serviceFollowing system deployment, the Management Service Account (MSA) is used by the system to run the reporting service.

Deployment Level

Data Center Comments

L1 Consolidated

L2 Data Center

L3 Database Install SSRS on the Database Management platform for L3 to L6 systems with Remote SQL.L4 or L5 Framework Database &

Reporting

L6 Reporting Platform

Chapter 6 - Install and Configure SSRS Install SSRS Reporting Service (Remote SQL)



Install SSRS Reporting Service (Remote SQL)You install SQL Server Reporting Services on the Database Management platform using the SQL Server Installation Wizard.

This procedure is relevant when SQL Servers are deployed remotely. For local SQL Servers, use the instructions in the SQL Server Installation chapters of this guide. They contain full SQL server installation instructions that include SSRS.

Before you beginVerify server prerequisites are met according to the Technology, Networking and Security Deployment Reference Guide.

Procedure1 Insert the SQL Server installation media into the DVD drive. Open the drive and run

setup.exe.

2 In the SQL Server Installation Center window, click Installation, and then click New SQL Server stand-alone installation or add features to an existing installation.

3 In the Setup Support Rules window, once the discovery operation to check the server configuration is complete, click Show Details.

4 Wait until the status of all the rules is Passed, and click OK.




5 In the Product Updates window:

a. Wait until the latest SQL Server updates are installed, or click Skip Scan.

b. Click Next.6 In the Install Setup Files window, wait until the Setup process is complete.

7 In the Setup Support Rules window:


b. Wait until the status of all the rules is Passed, and click Next.8 In the Installation Type window, Perform a new installation of SQL Server is

selected by default. Click Next.9 In the Product Key window, enter the product key, and click Next.10 In the License Terms window, click I accept the license terms, and click Next.11 In the Setup Role window, click SQL Server Feature Installation, and click

Next.12 In the Feature Selection window, select:

Reporting Services - Native Management Tools - Basic Management Tools - Complete SQL Server Data Tools (Install data tools separately in SQL Server 2014)

https://msdn.microsoft.com/en-us/library/mt204009.aspx




13 In the Installation Rules window:

a. Wait until the rule check is complete, and click Show Details.

b. Wait until the status of all the rules is Passed, and click Next.14 In the Instance Configuration window, select either the default or named

instance.

a. Default Instance: You can have one default instance per machine. The default instance name is MSSQLServer.

b. Named Instance: You can set a named instance (such as Impact360) in place of the default name, or when there are multiple instances on the same machine. Use Microsoft's guidelines when naming the instance, and ensure that the name meets the following:

It must begin with a letter.

It must not exceed 6 characters.


SQLServerAgent: SQLAgent$<instance name> MSSQL Service: MSSQL$<instance name> Instance Root Directory: It is preferable to use the default path; edit it if

desired.




The Disk Space Requirements window calculates the required disk space for the features that you specify. It then compares the required space to the available disk space. Click Next.

15 In the Server Configuration window, in the Services Accounts tab, enter the Account Name and Password for each service.

a. SQL Services Account Requirements: Describes each service and the required user account settings. The requirements are listed in the Technology, Security, & Network Integration Deployment Reference Guide.

b. SQL Server Installation Requirements: If you are installing SQL Server 2012, and you are installing on the same computer that also serves as a domain controller, the following settings are affected by the limitations involved in this installation. The requirements are listed in the Technology, Security, & Network Integration Deployment Reference Guide.

c. Remote SQL Server configuration recommendations: For service account configurations for remote or cluster SQL servers.

16 In the Reporting Services Configuration window, under Reporting Services Native Mode, click Install Only, and then click Next.

17 In the Error Reporting window, clear the option so that no information is sent to Microsoft, and click Next.

18 In the Installation Configuration Rules window:






19 In the Ready to Install window, review the Prerequisites, General Configuration, and Instance Configuration details for accuracy, and then click Install.

20 In the Installation Progress window, you can monitor the progress of the installation. After installation, the Complete page shows a Succeeded status for each feature. Click Close.




21 To finalize the configuration of Reporting Services, you should perform the steps listed in Configure SSRS, page 181, with the only difference being that your database settings are for a remote SQL Server, because you did not install the SQL Server engine locally.

What to do nextConfigure SSRS, page 181

Chapter 6 - Install and Configure SSRS Add SSRS to an existing SQL Server Instance



Add SSRS to an existing SQL Server InstanceUse this procedure when you have an existing local SQL Server instance, and need to add Reporting Services.

The Reporting Service will install at the level of the installation media. Even if the SQL Server instance was upgraded to a later version, the SSRS instance will remain at the version of the installation media. To align the SSRS and SQL Server versions, you need to re-install all service pack and CU patches.

Procedure1 Double-click setup.exe for the version of SQL Server currently installed.

2 In the SQL Server Installation Center window If there are prerequisites that need to be installed, click OK to install prerequisites, if they are required. Otherwise, move to the next step.

3 Select Installation > New SQL Server stand-alone installation or add features to an existing installation and wait for the SQL Server setup processes the current operation.

4 In the Setup Support Rules window, verify there are no failures, and then click OK.

5 In the Installation Type window, select Perform a new installation of SQL Server, and click Next.

Chapter 6 - Install and Configure SSRS Add SSRS to an existing SQL Server Instance



6 In the Product Key window, enter the product key and click Next.7 Accept the license terms and click Next.8 In the Setup Role window, select SQL Server Feature Installation, and click

Next.9 In the Feature Selection window, select Reporting Services - Native, and then

click Next.

10 In the Installation Rules window, the installer verifies all pre-requisites are installed for Reporting Services. When all rules have passed, click Next.

11 In the Instance Configuration window, enter the Named instance and modify the Instance root directory if necessary, then click Next.

12 Review the Disk Space Requirements, and click Next.13 In the Server Configuration window, provide the Account Name and Password

for the Reporting Service, and click Next.

Chapter 6 - Install and Configure SSRS Verify the SQL service pack level



14 In the Report Services Configuration window, select an option for Reporting Services Native Mode, and click Next: Install and Configure: SSRS is configured during the installation process.

Install only: SSRS is configured after the installation process.

15 To enable error reporting, select Send Error Reports to Microsoft or your corporate report server. Click Next.

16 In the Installation Configuration Rules window, the installer runs rules to verify the installation process.

a. If there are any other issues, click Show Details to display the status of the failed configuration rule.

b. Click Re-run to validate the configuration again.

c. When all configuration rules have passed, click Next. 17 In the Ready to Install window, review the features to be installed, and click

Install.

18 When the Complete window is displayed, click Finish to close the installer.

What to do nextVerify the SQL service pack level, page 180

Verify the SQL service pack levelIf SSRS was installed after the SQL Server was upgraded to the latest service pack, you need to re-run the service pack for SSRS to be upgraded to the same service pack level.

Procedure1 Run this query in the SQL Server to reveal the current version:

run select @@VERSION

Example: query resultMicrosoft SQL Server 2008 R2 (SP3) - 10.50.4305.0 (X64) Apr 3 2014 17:55:58 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

2 To compare the SQL Server version to the SSRS version, open the SSRS Configuration Tool, and select the server to view the Product Version.

3 If the versions are not identical, re-run the service pack to upgrade the SSRS version.

Chapter 6 - Install and Configure SSRS Configure SSRS



Configure SSRSComplete the following topics to configure SSRS:

Connect to the Report Server, page 181

Configure the Service Account, page 183

Configure the Web Service URL, page 184

Configure the Report Server database, page 185

Test the Report Manager URL, page 188

Configure SSRS E-mail Settings, page 189

Configure Database Server Name Change in SSRS, page 191

Connect to the Report ServerTo run the SSRS configuration, use any of your existing domain accounts that is both a local administrator and an SQL server administrator. Note that this user is for running the configuration only, not for running the SSRS service.

Procedure1 Click Start > All apps > Microsoft SQL Server > Configuration Tools >

Reporting Services Configuration Manager.The Reporting Services Configuration Connection window is displayed.

2 If not already displayed, enter the Server Name.

IMPORTANT SSL Configuration: To configure SSL for the SSRS server, see the Security Configuration Guide.

Chapter 6 - Install and Configure SSRS Connect to the Report Server



3 Select the Report Server Instance. This will be the named instance you created during the installation of SQL, or MSSQLSERVER if you used the default instance option

4 To connect to the Report Server, click Connect.The Reporting Services Configuration Manager window is displayed.

The window consists of three panes:

The left pane displays a list of logical groups which you can select for your configuration settings.

The top right pane displays a page for the settings corresponding to the currently selected group.

The bottom right pane displays the results for actions you apply.

Chapter 6 - Install and Configure SSRS Configure the Service Account



Configure the Service Account1 In the left pane, select Service Account.

The service Account settings are displayed in the right pane.

2 In the Service Account section of the right pane, select Use another account and then enter the MSA user name and password. (MSA is the Management Service Account used by services to run the suite applications in the enterprise. It has the minimal SQL rights required during application run-time.)

3 Click Apply.

The changes are applied. In the Results portion of the right pane, you will see the status of the changes you have applied.

Chapter 6 - Install and Configure SSRS Configure the Web Service URL



Configure the Web Service URL1 In the left pane, select Web Service URL.

The Web Service URL settings are displayed in the right pane.

2 Verify the Virtual Directory is: ReportServer_<name_of_SQL_instance>. ReportServer_IMPACT360, for example.

3 Update the TCP Port to the non-SSL default port 29283.

The SSL port for SSRS is not required due to Secure Gateway SSL offloading.

4 Click Apply.

The Web Service URL settings are applied, and the status is displayed in the Results section.

NOTE The name of the SQL instance, shown as _<name_of_SQL_instance> above, is added by default if SSRS is a named instance. Otherwise, the value of the Virtual Directory is ReportServer.For all other settings, leave the default values.

Chapter 6 - Install and Configure SSRS Configure the Report Server database



Configure the Report Server database1 In the left pane, select Database.

The Report Server Database Settings are displayed.

2 If the Database Name value displayed is ReportServer (the case for the default instance name), proceed to “Test the Report Manager URL” on page 188.

3 If the value displayed is blank or is not ReportServer, such as ReportServer$<name_of_SQL_instance>, complete the following:




a. Click Change Database.

The Report Server Database configuration wizard opens.

b. Select Create a new report server database, and then click Next.The Database Server settings display in the right pane.

c. Verify that the Server Name field contains the SQL Server instance you will create or on which an existing report database is located.

d. Verify that Authentication Type is set to Current User-Integrated Security, and then click Test Connection.

The database connection is tested.

If the connection succeeds, a dialog box will indicate a successful connection. Click OK to close the dialog box.

If the connection fails, you must diagnose the connection issue and retry the connection test.




e. After successfully testing the connection, click Next.In the right pane, the Database settings are displayed. Do not change any settings on this window.

f. Click Next.In the right pane, the Credentials settings are displayed. Do not change any settings on this window.

g. Click Next.In the right pane, the wizard summary is displayed.

Chapter 6 - Install and Configure SSRS Test the Report Manager URL



h. Click Next. The database configuration launches, and the status is displayed in the right pane.

When the configuration completes, the Finish button is enabled.

i. Click Finish.

The Reporting Services Configuration Manager window is displayed again.

Test the Report Manager URL1 In the left pane, select Report Manager URL.

The Report Manager URL settings are displayed in the right pane.

2 In the right pane, check to see if the Apply button is enabled. If enabled, click Apply.

The virtual directory is created, and the status is displayed in the Results area.

Chapter 6 - Install and Configure SSRS Configure SSRS E-mail Settings



3 Click the URLs link.

If the Windows Security window opens, provide the Management Services Account credentials.

The SQL Server Reporting Services Home page opens as shown in the following example:

4 Close the SQL Server Report Services Home page.

5 Click Exit to close the Reporting Services Configuration Manager.

You have completed SSRS configuration.

Configure SSRS E-mail SettingsThe report server e-mail delivery extension is not configured by default. You must use the Reporting Services Configuration Manager to minimally configure the extension.

To set advanced properties, you must edit the RSReportServer.config file.

NOTE If SQL Server Reporting Services Home page does not open or does not look like the example, check the SSRS configuration values and try again.

Chapter 6 - Install and Configure SSRS Configure SSRS E-mail Settings



Procedure1 Verify that the Report Server Windows service has Send As permissions on the

SMTP server.

2 Start the Reporting Services Configuration Manager and connect to the report server instance.

3 On the Email Settings page, enter the name of the SMTP server. This value can be an IP address, a UNC name of a computer on your corporate intranet, or a fully qualified domain name.

4 In Sender Address, enter the name an account that has permission to send e-mail from the SMTP server.

5 Click Apply.

Chapter 6 - Install and Configure SSRS Configure Database Server Name Change in SSRS



Configure Database Server Name Change in SSRSIf the name of your database server changes after you’ve installed and configured SSRS, you need to reconfigure SSRS accordingly.

Procedure1 Launch Reporting Services Configuration Manager.

2 Connect to the server and instance.

3 Select the Database side menu option.

4 Click Change Database.

5 Select Choose an existing report server database option.

6 Click Next.7 Provide updated connection details, which should just be the new name of the

server in place of the old name.

8 Click Test Connection to confirm settings. Be sure to use an account that is local administrator on the server (required to launch the SSRS configuration manager), and that has SQL privileges.

9 Click Next.10 Select the report server database. It should be ReportServer, or

ReportServer$<Instance Name> if you are using a named instance (for example, ReportServer$MYINSTANCE).

11 Click Next.12 Confirm the credentials.

13 Click Next.14 Review the summary of changes and click Next.15 Verify that the configuration progress completes without errors.

16 Click Finish.

Chapter 6 - Install and Configure SSRS Verify SSRS configuration post SQL upgrade



Verify SSRS configuration post SQL upgradeAfter upgrading SQL Server, verify the SSRS configuration has adopted the new instance ID and new SQL server version.

Procedure1 Identify the SQL Server Instance ID of the upgraded instance.

a. Launch the Reporting Services Configuration Manager.b. Connect to the Report Server Instance.

c. In the Report Server Status screen copy the Instance ID.

2 Navigate to %IMPACT360SOFTWAREDIR%\SSRS\Util using a command line.

3 Run the following command:

ReportingServicesUtils.Shell.exe /ssrspostupgrade ssrsinstancename:<instance id> version:<version>

4 Verify the outcome of the instance ID and versions:

Instance ID is the current, post-upgrade version of SQL Server.

Version is one of currently supported options: "2008R2", or "2012", or “2014”.

Chapter 6 - Install and Configure SSRS SSRS Encryption Keys Backup and Restore



SSRS Encryption Keys Backup and RestoreA backup copy of the Reporting Services encryption keys is required in these circumstances:

When restoring an existing report services server role.

When changing the management service account credentials.

Related informationBack up SSRS Encryption Keys (Workforce Optimization Maintenance Guide)

Restore SSRS Encryption Keys (Workforce Optimization Maintenance Guide)

C h a p t e r 7

Set Database Management Permissions

Topics Database Management Account (DMSA), page 195

DMSA preparation workflow scenarios, page 196

Assign DB permissions automatically, page 197

Assign DB permissions manually, page 200

SQL Permissions for Service Accounts, page 209

Post-system configuration tasks, page 214

Chapter 7 - Set Database Management Permissions Database Management Account (DMSA)



Database Management Account (DMSA)A domain database management account is available for customers that want to separate database run-time application operations from the database management and maintenance operations that require SQL SysAdmin rights. This enhances the security options available for customers by reducing privileges when accessing the SQL server.

Customers can select whether to use a single management service account for all application and database activities, or to introduce the database management account in addition to the management service account.

When you implement the database management account, database permissions are assigned as follows:

Management Service Account (MSA) permissions are reduced to the minimal SQL rights required for run-time application operations. MSA does not require SQL SysAdmin rights.

Database Management Account (DMSA) permissions include all database installation, maintenance and configuration operations. DMSA is also responsible for database upgrade, migration and patch installation.

DMSA is a member of the SQL SysAdmin role during these scenarios and the SysAdmin privileges can be revoked following system configuration.

All site preparation tasks: Technology, Security, and Networking Deployment Reference Guide.

All Database permission tasks: This guide

All post-system configuration tasks: Enterprise Manager Configuration and Administration Guide

IMPORTANT Database account permissions are validated by the Server Readiness Validation Tool, and by the hardware validation during system installation.

Chapter 7 - Set Database Management Permissions DMSA preparation workflow scenarios



DMSA preparation workflow scenariosThe DMSA preparation workflows vary depending on the scenario.

Define MSA/DMSA in new systems (turquoise).

Introduce DMSA in an existing system functioning with MSA only (blue).

Change the MSA account, DMSA account, or both in an existing system (green).

DMSA workflows

Re-define existing MSA and MSA as SQL SysAdmins

New V11.2 System with MSA/DMSA

Introduce DMSA in existing V11.2

System

Change MSA/DMSA Credentials

Assign Database Permissions Manually

1. Verify user credentials 2. Set account permissions 3. Create SQL credential object 4. Assign MSDB permissions

5. Create a new proxy

5. Assign I360 database permissions 6. Create a new proxy

5. Modify database user name

Post System Configuration Tasks

1. Remove SysAdmin rights from DMSA

1. Configure MSA/DMSA in the Enterprise Settings 2. Remove SysAdmin rights from DMSA

1. Verify no services are failing 2. Resolve all active alarms in the system 3. Configure MSA/DMSA in the Enterprise Settings 4. Review the alarms again and resolve active alarms 5. Perform sanity tests 6. Remove previous MSA/DMSA accounts from the SQL server and Windows domain 7. Remove SysAdmin from DMSA

Assign database permissions automatically?

Assign Database Permissions Automatically

1. Verify Tool User Credentials 2. Verify PowerShell Functionality 3. Run the Database Permissions Configuration Tool

Site preparation

1. Define DMSA and MSA accounts 2. Meet Windows user rights requirement 3. Prepare and install SQL Server(s) 4. Define DMSA/MSA as SQL Logins 5. Grant DMSA SysAdmin rights (revoke later)

YESNO

Chapter 7 - Set Database Management Permissions Assign DB permissions automatically



Assign DB permissions automaticallyThe Database Permissions Configuration Tool automatically assigns the relevant service accounts with the required database permissions. Some permissions impact the SQL server instance level (credential, proxy, and so on), while others impact database security.

The tool is signed by a trusted certificate authority (CA) to facilitate database security and uses PowerShell scripting functionality that exposes all SQL server scripts for the database administrator in plain text format.

Before you beginEnsure all MSA/DMSA site preparation is complete according to the workflow and the Technology, Security, and Networking Deployment Reference Guide.

Procedure1 Verify tool user credentials, page 198

2 Verify Windows PowerShell functionality, page 198

3 Run the Database Permissions Configuration Tool, page 198

Related informationPrepare DMSA (or MSA) for Database Management (Technology, Security, & Network Integration Deployment Reference Guide)

Access the Database Permissions Configuration ToolYou can access the Database Permissions Configuration Tool on the Verint Online site prior to a first time installation, or from any server hosting the database platform in existing systems.

Access for New InstallationsPrior to a new system installation, the tool is accessible from the document tree on the Verint Online site.

1 Enter the Verint Online site and browse to the WFO & FT V15.1 Tools folder.

2 Copy the Database Permissions Configuration Tool folder to a server installed and configured an SQL Server instance.

For multiple SQL instances, download the tool to one SQL server instance only.

Access for Existing SystemsThe tool is located on each database platform server following system installation. For deployment levels that have multiple database platforms, you need to access the tool on one server only.

On a server installed with a database platform, browse to the [Software Directory]/CommonDB/Utils/Database Permissions Configuration Tool folder.

Chapter 7 - Set Database Management Permissions Verify tool user credentials



Verify tool user credentialsAs the user running the tool, verify credentials to ensure that you are defined as:

A local windows administrator on the server running the tool.

A member of the SQL SysAdmin server role on each machine hosting an SQL server instance.

Verify Windows PowerShell functionalityVerify the PowerShell execution policy on the server running the Database Permissions Configuration Tool. Depending on the policy, select the relevant setup file.

Procedure1 On the SQL Server, run Start > Windows PowerShell.2 In the Administrator: Windows PowerShell console, run the Get-

ExecutionPolicy command.

If the result is:

Unrestricted: Servers with Unrestricted, RemoteSigned, or AllSigned PowerShell functionality can run the PowerShell setup file (Setup_signed.ps1).

Restricted: There are two options for servers restricted for PowerShell functionality:

Use the batch setup file (Setup.bat) to bypass the restriction for a single execution of the tool, or

Enable the machine for unrestricted functionality and then use the PowerShell setup file, as follows:

i. In the console run the Set-ExecutionPolicy AllSigned command.

ii. Enter Y to confirm the change.

iii. Use the Setup_signed.ps1 when running the tool.

Run the Database Permissions Configuration ToolRun the Database Permissions Configuration Tool once for each SQL server instance in the enterprise. Update the server name and port for each instance.

Procedure1 From the Database Permissions Configuration Tool folder run the relevant

setup file.

2 If prompted, confirm that you trust the publisher, enter [A] Always run or [R] run once.

3 Enter the SQL Server Details:

SQL Server Name: The host name or IP address of the SQL Server.

Chapter 7 - Set Database Management Permissions Run the Database Permissions Configuration Tool



Port: The SQL Server listening port. The default port is 1433.

4 Enter the SQL Server Login Details:

5 Click Apply. When the confirmation message appears, click Yes.

6 A permissions validation message appears if the SQL public server role does not have the execute permission. Click Details to troubleshoot the relevant scripts and refer to the SQL public server role permissions table.

7 Result: When the database permissions are all successfully assigned to the service accounts, the success message All database permissions scripts ran successfully appears.

If the success message does not appear at the end of the text box, scroll through the SQL server scripts the tool ran and search for Status: Failed. Troubleshoot the stored procedure script above this status. If not, scroll through the logs displayed to review which database permission was denied or failed.

8 For multiple SQL Server instances, run the tool again for each instance from the same machine by changing the SQL Server Name and Port to the server name hosting the next instance.

Parameter Description

Database Management Account Name

Enter the user name as configured for DMSA during SQL server configuration.

Database Management Account Password

Enter the account password as configured for DMSA during SQL server configuration.

Management Service Account Name

Enter the account login name as configured for MSA during SQL server configuration.

Management Service Account Password

Enter the account password as configured for MSA during SQL server configuration.

Chapter 7 - Set Database Management Permissions Assign DB permissions manually



Assign DB permissions manuallyManually assigning database permissions requires that SQL permissions are set for both the Management Service Account (previously known as IMSA) as well as the Database Management Account (DMSA) for each SQL server instance. Some permissions impact the SQL server instance level (credential, proxy, and so on), while others impact database security.

Before you beginEnsure all MSA/DMSA site preparation is complete according to the workflow and the Technology, Security, & Network Integration Deployment Reference Guide.

Procedure1 Verify user credentials, page 200

2 Set account permissions, page 200

3 Create or modify SQL credential object, page 201

4 Assign MSDB permissions, page 202

5 Assign I360 databases permission, page 204 (for workflow 2/blue only)

6 Create a new proxy, page 206

7 Modify database user name, page 207 (for workflow 3/green only)

Related informationDMSA site preparation (Technology, Security, & Network Integration Deployment Reference Guide)

Verify user credentialsAs the user assigning database permissions manually, ensure you are defined as a member of the SQL SysAdmin server role on each machine hosting an SQL server instance.

Set account permissionsSet the account permissions for customers who elect to have a single Management Service Account, as well as those who choose to separate the Management from the Database account.

All accounts must be assigned the required permissions as detailed in the User Rights, Windows Services, and Settings Guide.

NOTE It is mandatory for all SQL Server jobs to use the predefined names for the credential and proxy that are created during this procedure: I360DBCredential and I360DBProxy.

Chapter 7 - Set Database Management Permissions Create or modify SQL credential object



Depending on the customer’s selected configuration, perform the following:

Customers with a single Management Service Account: Assign the Management Service Account with all the permissions listed in both permission tables A and B.

Customers that elect to use separate accounts for Management and Database:

Assign the Management Service account with the Management Service Account permissions in table A.

Assign the Database Service Account with the Database Management Service Account permissions in table B.

Related TopicsTable A: Management Service account permissions, page 209

TTable B: Database Management Service account permissions, page 210

Create or modify SQL credential objectTo enable mapping between the SQL Server and the Operating System, create or modify the SQL credential object.

Create a new credential when defining DMSA for the first time (workflow 1 and 2).

Modify the credential when existing systems with DMSA are changing the user name and/or password of the database and/or Management Service Account(s) (workflow 3).

In remote SQL configurations the SQL credential object requires permission in the registry to run scripts. See “Remote SQL Server configuration recommendations” on page 107.

Procedure1 From the SQL Server Management Studio, connect to the relevant SQL server

instance and select Security > Credentials.

2 Right-click Credentials, select New Credential and create the new credential or modify an existing credential. Enter the details as follows:

Chapter 7 - Set Database Management Permissions Assign MSDB permissions



The credential is created/modified for the Database Management Account.

Assign MSDB permissionsAssigning the accounts with MSDB permissions enables the accounts to manage SQL server jobs and SSIS packages. This can be done manually from the SQL Manager or by using TSQL commands.

Procedure

Credential name I360DBCredential

Identity <DOMAIN\USER>If you selected not to use the DMSA option, then enter the Management Service Account details when prompted for Domain and User in order to create the credential for the Management Service account.

Password <PASSWORD>

Confirm password <PASSWORD>

TIP You can also use the TSQL Command to create the required credential:CREATE CREDENTIAL [I360DBCredential] WITH IDENTITY = N'<DOMAIN\USER>', SECRET = N'<PASSWORD>'

Step SQL Server Management Studio Command Line

1 Create the I360DBRole database role:Open SSMS Connect to the relevant SQL Server Instance DatabasesSystem DatabasesmsdbSecurityRolesDatabase Roles (right click) New Database Role.Enter details as follows:Role name: I360DBRoleOwner: dbo

USE [msdb];

GO

CREATE ROLE [I360DBRole] AUTHORIZATION [dbo]

Chapter 7 - Set Database Management Permissions Assign MSDB permissions



2 Create the I360DBUser Database User:Open SSMS Connect to the relevant SQL Server Instance DatabasesSystem DatabasesmsdbSecurityUsers(right click) New User.Enter details as follows:User name: I360DBUserLogin name: <DOMAIN\USER> (for DMSA user)Default schema: dbo

In the Database role membership list, select the following roles:db_datareaderI360DBRoleSQLAgentOperatorRoledb_ssisadminSQLAgentReaderRole

USE [msdb];

GO

CREATE USER [I360DBUser] FOR LOGIN [<DOMAIN\USER>] WITH DEFAULT_SCHEMA=[dbo]

Note: [<DOMAIN\USER>= “DMSA user”EXEC sp_addrolemember N'db_datareader', 'I360DBUser'

EXEC sp_addrolemember N'I360DBRole', 'I360DBUser'

EXEC sp_addrolemember N'SQLAgentOperatorRole', 'I360DBUser'

EXEC sp_addrolemember N'db_ssisadmin', 'I360DBUser'

EXEC sp_addrolemember N'SQLAgentReaderRole', 'I360DBUser'

3 Create the I360AppRole database role:

Open SSMS Connect to the relevant SQL Server Instance DatabasesSystem DatabasesmsdbSecurityRolesDatabase Roles (right click) New Database Role.Enter details as follows:Role name: I360AppRoleOwner: dbo

USE [msdb];

GO

CREATE ROLE [I360AppRole] AUTHORIZATION [dbo]


Chapter 7 - Set Database Management Permissions Assign I360 databases permission



Assign I360 databases permissionPerform this step only when introducing a new database management account for systems with an existing Management Service Accounts only (workflow 2/blue).

It is best practice that a new service account is created as the DMSA user, and the existing Management Service account remains as Management Service Account (with less database access).

In this scenario, every system database requires that the two database users are mapped as follows:

DMSA SQL login should be mapped to the I360DBUser, which is mapped to the I360DBRole

Management Service Account SQL login should be mapped to the I360AppUser, which is mapped to the I360AppRole

4 Perform this step only when customers select to use separate accounts for Management and Database: Create the I360AppUser database user:

Open SSMS Connect to the relevant SQL Server Instance DatabasesSystem DatabasesmsdbSecurityUsers(right click) New User:Enter details as follows:User name: I360AppUserLogin name: <DOMAIN\USER> (for Management Service Account user)Default schema: dbo

In the Database role membership list select the following roles: db_datareader I360AppRole SQLAgentReaderRole RSExecRole (Assign this role on the

SQL Server hosting the Reporting Services Database only.)

USE [msdb];

GO

CREATE USER [I360AppUser] FOR

LOGIN [<DOMAIN\USER>] WITH DEFAULT_SCHEMA=[dbo]

Note:[<DOMAIN\USER>= “Management Service Account user”

EXEC sp_addrolemember N'db_datareader', 'I360AppUser'

EXEC sp_addrolemember N'I360AppRole', 'I360AppUser'

EXEC sp_addrolemember N'SQLAgentReaderRole', 'I360AppUser'

EXEC sp_addrolemember N'RSExecRole', 'I360AppUser'


Chapter 7 - Set Database Management Permissions Assign I360 databases permission



Procedure


1 Create the I360DBRole database role:Open SSMSConnect to the relevant SQLServer InstanceDatabases(I360 Database) SecurityRolesDatabase Roles(right click) New Database Role.Enter details as follows:Role name: I360DBRoleOwner: dbo

USE [<I360 Database>];GO

CREATE ROLE [I360DBRole] AUTHORIZATION [dbo]

2 Create the I360DBUser Database User:Open SSMS Connect to the relevant SQLServer InstanceDatabases<I360 Database> SecurityUsers(right click) New User.Enter details as follows:User name: I360DBUserLogin name: <DOMAIN\USER(for DMSA user)Default schema: dboIn the Database role membership list, select the following roles: db_owner I360DBRole

USE [<I360 Database>];

GO

CREATE USER [I360DBUser]

FOR LOGIN [<DOMAIN\USER>]

WITH DEFAULT_SCHEMA=[dbo]

Note: <DOMAIN\USER>= "DMSA user"EXEC sp_addrolemember N'db_owner', 'I360DBUser'

EXEC sp_addrolemember N'I360DBRole', 'I360DBUser'

3 Create the I360AppRole database role:Open SSMSConnect to the relevant SQLServer InstanceDatabases(I360 Database) SecurityRolesDatabase Roles(right click) New Database Role.Enter details as follows:Role name: I360AppRoleOwner: dbo

USE [<I360 Database>];

GO

CREATE ROLE [I360AppRole] AUTHORIZATION [dbo]

Chapter 7 - Set Database Management Permissions Create a new proxy



Create a new proxyCreating a new proxy defines the connection between the Credential object and the executable set of defined jobs. Create a new proxy manually or using the TSQL command line.

Procedure

4 Perform this step only when customers elect to use separate accounts for Management and Database: Create the I360AppUser database user:Open SSMSConnect to the relevant SQL Server InstanceDatabases(I360 Database) SecurityUsers(right click) New User Enter details as follows:User name: I360AppUserLogin name: <DOMAIN\USER> (for Management Service Account user)Default schema: dboIn the Database role membership list select the following roles:db_ownerI360AppRole

GO

CREATE USER [I360AppUser]

FOR LOGIN [<DOMAIN\USER>]

WITH DEFAULT_SCHEMA=[dbo]

Note: <DOMAIN\USER>= "Management Service Account user"EXEC sp_addrolemember N'db_owner', 'I360AppUser'

EXEC sp_addrolemember N'I360AppRole', 'I360AppUser'



1 From the SQL Server Management Studio, select SQL Agent>Proxies, and right click Create New Proxy.

EXEC msdb.dbo.sp_add_proxy

@proxy_name = N'I360DBProxy',

@credential_name = N'I360DBCredential',

@enabled = 1

Chapter 7 - Set Database Management Permissions Modify database user name



Modify database user nameRunning the scripts maps the previous user names to the new user name. This is required for workflow 3/green when:

Changing the credentials of an existing DMSA user.

Changing the credentials of an existing Management Service Account in a system that already includes DMSA.

Modify DMSA user nameRun this script to map the I360 databases user (I360DBUser) to the new DMSA SQL login.

Modify Management Service account user nameRun this script to map the I360 databases user (I360AppUser) to the new Management Service Account SQL login.

2 Ensure that the new proxy is active to the following sub-systems:

Operating system (CmdExec)

SQL Server Integration Services Package

EXEC msdb.dbo.sp_grant_proxy_to_subsystem @proxy_name = N'I360DBProxy', @subsystem_id = 3

EXEC msdb.dbo.sp_grant_proxy_to_subsystem

@proxy_name = N'I360DBProxy',

@subsystem_id = 11

3 From the Principals tab, click Add Button, with the details as follows:

Principal type: Msdb role Select from the list:

I360DBRole

EXEC msdb.dbo.sp_grant_login_to_proxy @proxy_name = N'I360DBProxy', @msdb_role = N'I360DBRole'


SQL Server Management Studio Command Line

Execute the command for each I360 database

ALTER USER [I360DBUser] WITH NAME = [I360DBUser], LOGIN = [<DOMAIN>\<USER>]

Where the <DOMAIN>\<USER> are the credentials of the new DMSA user.

Chapter 7 - Set Database Management Permissions Modify database user name



SQL Server Management Studio Command Line

Execute the command for each I360 database

ALTER USER [I360AppUser] WITH NAME = [I360AppUser], LOGIN = [<DOMAIN>\<USER>]

Where the <DOMAIN>\<USER> are the credentials of the new Management Service Account user.

Chapter 7 - Set Database Management Permissions SQL Permissions for Service Accounts



SQL Permissions for Service Accounts Table A: Management Service account permissions, page 209

Table B: Database Management Service account permissions, page 210

Table C: SQL public server role permissions, page 212

Table A: Management Service account permissionsThis table lists the SQL permissions to set for the Management Service Account when using the DMSA option. When not using the DMSA option, the permissions in both table A and table B are set for the Management Service Account.

Permission Required Command Example

"bulkadmin" fixed role EXEC master..sp_addsrvrolemember @loginame = N'<DOMAIN\USER>', @rolename = N'bulkadmin'

ETLs, bulk insert file operations etc

“VIEW SERVER STATE” permission

GRANT VIEW SERVER STATE TO [<DOMAIN\USER>]

View DMVs, query server state etc

Execute permission on xp_msver

GRANT EXECUTE ON [xp_msver] TO [<DOMAIN\USER>]

Retrieve information about SQL Server instance

Execute permission on xp_sqlagent_enum_jobs

GRANT EXECUTE ON [xp_sqlagent_enum_jobs] TO [<DOMAIN\USER>]

Retrieve current status of SQL Agent jobs

Execute permission on xp_enum_oledb_providers

GRANT EXECUTE ON [xp_enum_oledb_providers] TO [<DOMAIN\USER>]

Enumerates all OLE DB providers installed on a SQL Server so the correct value will be populated during EM distribution.

Execute permission on sp_execute

GRANT EXECUTE ON [sp_execute] TO [Domain\LoginName]

Used to execute SQL script and/or dynamic SQL within stored procedures.

Execute permission on sp_executesql

GRANT EXECUTE ON [sp_executesql] TO [Domain\LoginName]


Chapter 7 - Set Database Management Permissions Table B: Database Management Service account permissions



Table B: Database Management Service account permissions

This table lists the SQL permissions to set for DMSA. When not using the DMSA option, the permissions in both table A and table B are set for the Management Service Account.

Execute permission on sp_prepare

GRANT EXECUTE ON [sp_prepare] TO [<DOMAIN\USER>]

Used to prepare (compile) SQL script and/or dynamic SQL within ETLs and managed code.

Execute permission on sp_prepexec

GRANT EXECUTE ON [sp_prepexec] TO [<DOMAIN\USER>]

Used to prepare (compile) and execute SQL script and/or dynamic SQL within ETLs and managed code.

Execute permission on sp_unprepare

GRANT EXECUTE ON [sp_unprepare] TO [<DOMAIN\USER>]

Used to free a prepared (compiled) SQL script and/or dynamic SQL within ETLs and managed code.

Execute permission on sp_xml_preparedocument

GRANT EXECUTE ON [sp_xml_preparedocument] TO [<DOMAIN\USER>]

Submit evaluations, xml-based ETLs

Execute permission on sp_xml_removedocument

GRANT EXECUTE ON [sp_xml_removedocument] TO [<DOMAIN\USER>]




"sysadmin" fixed role EXEC master..sp_addsrvrolemember @loginame = N'<DOMAIN\USER>', @rolename = N'sysadmin'

Grant during system installation or during a change to the service accounts until configuration and distribution is complete

"bulkadmin" fixed role EXEC master..sp_addsrvrolemember @loginame = N'<DOMAIN\USER>', @rolename = N'bulkadmin'

ETLs, bulk insert file operations etc

Chapter 7 - Set Database Management Permissions Table B: Database Management Service account permissions



"ALTER SETTINGS" permission

GRANT ALTER SETTINGS TO [<DOMAIN\USER>]

Configure different aspects of SQL Server instance to optimize performance (for example, define "max server memory" value)

"VIEW SERVER STATE" permission

GRANT VIEW SERVER STATE TO [<DOMAIN\USER>]

View DMVs, query server state etc

“ALTER ANY LINKED SERVER” permission

GRANT ALTER ANY LINKED SERVER TO [<DOMAIN\USER>]

Create or change SQL linked servers.

Execute permission on "xp_msver

GRANT EXECUTE ON [xp_msver] TO [<DOMAIN\USER>]

Retrieve information about SQL Server instance

Execute permission on "xp_sqlagent_enum_jobs

GRANT EXECUTE ON [xp_sqlagent_enum_jobs] TO [<DOMAIN\USER>]

Retrieve current status of SQL Agent jobs

Execute permission on "xp_enum_oledb_providers

GRANT EXECUTE ON [xp_enum_oledb_providers] TO [<DOMAIN\USER>]

Enumerates all OLE DB providers installed on a SQL Server so the correct value will be populated during EM distribution

Execute permission on sp_execute

GRANT EXECUTE ON [sp_execute] TO [Domain\LoginName]


Execute permission on sp_executesql

GRANT EXECUTE ON [sp_executesql] TO [Domain\LoginName]


Execute permission on sp_prepare

GRANT EXECUTE ON [sp_prepare] TO [<DOMAIN\USER>]

Used to prepare (compile) SQL script and/or dynamic SQL within ETLs and managed code.

Execute permission on sp_prepexec

GRANT EXECUTE ON [sp_prepexec] TO [<DOMAIN\USER>]

Used to prepare (compile) and execute SQL script and/or dynamic SQL within ETLs and managed code.


Chapter 7 - Set Database Management Permissions Table C: SQL public server role permissions



Table C: SQL public server role permissionsThis table lists the objects that require the EXECUTE right for the SQL public server role. Use this table as a reference when troubleshooting SQL public role permission validations for the service accounts defined as SQL logins. In accordance with Microsoft guidelines, do not revoke internal stored procedures from the public server role.

Some stored procedures may be deprecated in later versions of SQL server.

Execute permission on sp_unprepare

GRANT EXECUTE ON [sp_unprepare] TO [<DOMAIN\USER>]

Used to free a prepared (compiled) SQL script and/or dynamic SQL within ETLs and managed code.

Execute permission on sp_xml_preparedocument

GRANT EXECUTE ON [sp_xml_preparedocument] TO [<DOMAIN\USER>]


Execute permission on sp_xml_removedocument

GRANT EXECUTE ON [sp_xml_removedocument] TO [<DOMAIN\USER>]



SQL Public Server Role

sp_AddFunctionalUnitToComponent

sp_createorphan sp_droporphans sp_fetchLOBfromcookie

sp_getschemalock sp_http_generate_wsdl_complex

sp_http_generate_wsdl_simple

sp_MSgetversion

sp_releaseschemalock

sp_replddlparser sp_replhelp sp_replsendtoqueue

sp_replsetsyncstatus

sp_replwritetovarbin

sp_reset_connection

sp_resyncexecute

sp_resyncexecutesql

sp_resyncprepare sp_resyncuniquetable

sp_SetOBDCertificate

sp_setuserbylogin sp_showmemo_xml

sp_start_user_instance

sp_unprepare

sp_update_user_instance

xp_dirtree xp_fileexist xp_fixeddrives

xp_getnetname xp_instance_regread

xp_MSADEnabled xp_qv

Chapter 7 - Set Database Management Permissions Table C: SQL public server role permissions



xp_regread xp_repl_convert_encrypt_sysadmin_wrapper

xp_replposteor

SQL Public Server Role

Chapter 7 - Set Database Management Permissions Post-system configuration tasks



Post-system configuration tasksPerform all post-system configuration tasks according to the workflow. These tasks are performed after the system installation, upgrade, and / or system enterprise configuration. This is not performed after SQL Server configuration.

Define DMSA in a new systems (turquoise)1 Remove SysAdmin rights from DMSA (optional).

This is to be done only following successful enterprise configuration and distribution.

Introduce DMSA in an existing system (blue) 1 Configure MSA/DMSA in the Enterprise Settings.

2 Remove SysAdmin rights from DMSA (optional)

Related informationChange the MSA/DMSA account credentials (green step-by-step) (Enterprise Manager Configuration and Administration Guide)

avaya workforce optimization sql server · avaya workforce optimization sql server installation and...

Documents