Work Smarter Not Harder Standardize Your Environment With Best Practices

Introduction  AJ Mendo   Over the years AJ has worked with a variety of databases and has worked for military, civilian, and federal government organizations supporting a wide variety of applications. He currently works on a team of DBAs supporting over 200 database servers of various sizes. He is a frequent presenter at user groups, SQL Saturday’s and online. He gives his time freely for SQL Events and loves being a part of the SQL Community.

Objectives  What does it mean to Standardize?  What can be Standardized?  Using “scripts” to make things easier  Get others to follow the Standards  Document and publish – consider it a “living document”

What does it mean to Standardize?  Definition: stand·ard·ize /ˈstandərˌdīz/ Verb: 1.to make or become standard: 2. to test by or compare with a standard: “SQLAJ has an effort underway to standardize server installations".  Partial Source:

Quiz: Why Should You Standardize?  Lays out the rules for everyone  Makes “non-standards” easy to spot and corrections easier  It will make your life (and job) easier  Because SQLAJ said so (and he is cool!)  All of the above

O.K. but what can be standardized?  Server setup  Access restrictions  SQL versions and installations  Post install configurations  Routine maintenance  Tracking Changes  Release/Deployment process

Server Setup  Drive configuration  Use the correct file system  Formatting drives correctly

Access Restrictions  Types of accounts  Windows - users  SQL - applications  Different levels for different environments  Development, Test/QA, Pre-Production, Production  Who gets access  Developers, Project Managers, Build Managers  Isolate Services  Different Accounts for SQL Engine, SQL Agent  Use low-rights Windows or Local accounts

Sizing Drives  Get the information from customer  Current database size  Projected growth 1, 3, 5 years  Develop an algorithm Backups will be compressed Allow for.5% growth  Remember Operating System and application installation  C:\OS – 40GB  D:\App(SQL) – 50GB

Windows and SQL Versions  Operating System  SQL Server  Service Packs  SQL components

Install from Configuration File  Faster Installs  No more clicking “Next”  Put all commands in Configuration file  Advantage to standard server builds  Different Configuration Files based on components SQL Engine, Report Services, SSIS, SSAS  Blog Post on how to 

Post Install Configuration  SQL Agent Jobs – Option 1  Manually Create Jobs  Use the Wizard / Design Console  Can be time consuming (approximately 5 minutes each x4)  Job is owned by user who created it  Maintenance plans can be finicky

Post Install Configuration  SQL Agent Jobs – Option 2  Use SQL scripts to create jobs  Faster (approximately 30 seconds or less)  Easy to use/maintain  Job owner is set (local or domain account)

Routine Maintenance  Backups  Integrity Checks  Index Defragmenting  Clean Up

Tracking changes  How do you track changes to environment  Is there an approval process  Work flow  Closing tickets

Release/Deploying Code Updates  Release calendar  Released from Development, QA/Test, Pre-Production, Production  Application code, database scripts, deployment instructions  Required 72 hours in advance  Instructions must be full and complete  Written so any DBA or SA can deploy updates

Getting others to follow standards  Talk with Managers  Demonstrate how makes setup/configuration easier  Getting team members to agree

Document and Publish  Write up the Standards  Post to a central location  Refer others such as SAs and Project Managers to location  Living Document – update as needed.

Wrap Up  What does it mean to Standardize?  What can be Standardized?  Get others to follow Standards  Using “Scripts” to make things easier  Document and publish – Consider it a “living document”

Resources  Isolate SQL Services   Using the Correct File System   Formatting data drives   Blog Post – Install using Configuration file 