1. Administering Your Microsoft SQL Server Geodatabase
Chet Dobbins
Ron Lazar
Shannon Shields

2. Online Content and Services
Intended Audience
Desktop
Web
Device
Portal
Server
SQL Server
Desktop
Web
Device
Server
Online Content and Services
Portal
You are…..
A geodatabase administrator
An accidental DBA
A deliberate DBA
Not sure what DBA means
And you…
Store your data in a SQL Server database
Are thinking about using SQL Server
This is your session!
Esri UC Administering Your Microsoft SQL Server Geodatabase

3. Agenda News since the last UC How do I …
Configure SQL Server to support geodatabases?
Create geodatabases?
Control access to my data?
Make sure that my data is safe?
Maintain good performance?
Esri UC Administering Your Microsoft SQL Server Geodatabase

4. ArcGIS and Microsoft changes since last year
News
ArcGIS and Microsoft changes since last year

5. What’s new at 10.4.x Support for SQL 2016
ODBC Driver 13 supported at
Transaction model changes
Read-committed Snapshot
Snapshot Isolation
KB Article
Esri UC Administering Your Microsoft SQL Server Geodatabase

6. Supported versions 10.3.x last release to support 2008 & 2008 R2
10.4.x releases support SQL Server 2016
ODBC 13 driver – supported with only
10.4 use ODBC 11 driver
Esri UC Administering Your Microsoft SQL Server Geodatabase

7. How do I…?
Common questions when working with SQL Server databases and geodatabases

8. How do I… configure SQL Server to support geodatabases?

9. How do I configure SQL Server to support geodatabases?
Install a supported version of SQL Server
Microsoft SQL Server database requirements for ArcGIS
Must use a Case-Insensitive (CI) collation
Can use Windows or Mixed-mode authentication
SQL Server Browser not required
Must provide static TCP port on connection
Esri UC Administering Your Microsoft SQL Server Geodatabase

10. Connecting to SQL Server from ArcGIS
Requires a Microsoft stand-alone DLL
Microsoft ODBC Driver 13 for SQL Server – ArcGIS
Microsoft ODBC Driver 11 for SQL Server – ArcGIS 10.3.x and 10.4
SQL Server Native Client – ArcGIS 10.2.x and earlier
SQL Server 2012 is last release to ship the Native Client
Install on every single client
Must be same or newer version than SQL Server
Esri UC Administering Your Microsoft SQL Server Geodatabase

11. Connecting to SQL Server
Ron Lazar
Esri UC Administering Your Microsoft SQL Server Geodatabase

12. How do I… create geodatabases?

13. Databases and Geodatabases
A database is a SQL Server object
There can be many per SQL Server instance
A geodatabase is an ArcGIS construct hosted in a database
One allowed in each database
Options for creating geodatabases
Use a GP tool to create a new geodatabase from scratch
Use a GP tool to create a new geodatabase in an existing database
Esri UC Administering Your Microsoft SQL Server Geodatabase

14. Creating a geodatabase
Ron Lazar
Esri UC Administering Your Microsoft SQL Server Geodatabase

15. Choosing a geodatabase schema
DBO
Owned by the DBO built-in user
Multiple logins can be DBO
Easier to use Windows authentication for administrator
SDE
Owned by a database user (SDE)
SDE user needs fewer permissions than DBO
No geodatabase users need to be DBO
Esri UC Administering Your Microsoft SQL Server Geodatabase

16. Special cases Use Enable Geodatabase command when
DBO is database owner, not sysadmin
SDE user, no sysadmin
Windows-authenticated SDE user
Esri UC Administering Your Microsoft SQL Server Geodatabase

17. Points to remember Use GP Tools to create geodatabases
Default size of 500MB data file & 125MB logfile
More control over storage?
Use SQL Server tools to create database first
Enable geodatabase tool
Create a geodatabase in an existing database, without sysadmin privileges
Do not rename a database that contains a geodatabase
Esri UC Administering Your Microsoft SQL Server Geodatabase

18. Upgrading a geodatabase
Permissions
Requires DBO, SysAdmin or db_owner
Order of operations when upgrading both geodatabase and SQL Server
One at a time
SQL Server needs to be at supported release for upgraded version
Applies to geodatabase AND connecting clients
Upgrading SQL Server
Does not upgrade compatibility level of your database
Esri UC Administering Your Microsoft SQL Server Geodatabase

19. How do I… control access to my data?
Access to SQL Server objects are managed with permissions granted to logins, users and roles

20. SQL Server Principals Logins = Authentication Users = Authorization
Who is connecting?
Users = Authorization
What can this person do in the database?
Schemas = Containers
What are logical groups of database objects that should be managed as a whole?
Esri UC Administering Your Microsoft SQL Server Geodatabase

21. SQL Server Instance Logins Users
Esri UC Administering Your Microsoft SQL Server Geodatabase

22. User-schema relationship
For users that create data, ArcGIS requires that
user name = default schema name
Not a SQL Server rule
Users that are DBO all create data in the DBO schema
Data readers & editors do not need a same-named schema
Esri UC Administering Your Microsoft SQL Server Geodatabase

23. Limit Permissions for Most Users
Data Owners
Data Editors
Data Readers
Admin
Esri UC Administering Your Microsoft SQL Server Geodatabase

24. Who is DBO? Sysadmin fixed-server role
members are DBO in every database
Database owner
Is DBO in single
database
Db_owner role members
are NOT DBO
Have DBO-like permissions
Esri UC Administering Your Microsoft SQL Server Geodatabase

25. Managing permissions Chet Dobbins
Esri UC Administering Your Microsoft SQL Server Geodatabase

26. Permissions needed to read, edit or create data
Task
Required permissions
Creator
CREATE TABLE, CREATE PROCEDURE and
CREATE VIEW*
Editor
SELECT, INSERT, UPDATE and DELETE on objects** plus EXECUTE on stored procedures used to generate sequential values
Reader
SELECT on tables**
* Needed to create versioned or archived views ** Including feature, SDEGEOMETRY, versioning and archiving support tables, if present
Esri UC Administering Your Microsoft SQL Server Geodatabase

27. Permissions needed to manage users
Task
Required permissions
Create geodatabase user
Membership in sysadmin fixed server role
Create database role
CREATE ROLE
Compress geodatabase
SDE-schema: SDE user, DBO user or member of DB_OWNERS database role
DBO-schema: DBO user or member of DB_OWNERS database role
Kill geodatabase connections
Membership in the processadmin fixed server role, and granted VIEW DEFINITION database permission
View all geodatabase users
VIEW DEFINITION database permission
Esri UC Administering Your Microsoft SQL Server Geodatabase

28. Permissions needed to manage databases
Task
Required permissions
Create enterprise geodatabase
Membership in sysadmin fixed server role
Upgrade geodatabase
DBO user in database OR
Member of DB_OWNERS fixed database role
User privileges for geodatabases in SQL Server
Esri UC Administering Your Microsoft SQL Server Geodatabase

29. Password Policies SQL Server uses Windows password policy
Password expiration rules
Complexity rules for strong passwords
Can be disabled
Security policy is set on the domain or local OS
Policies may vary from site to site
Esri UC Administering Your Microsoft SQL Server Geodatabase

30. User-schema with Windows groups
A Windows group can be added as a login
Associate the login with a database user
Do not create a matching schema
For logins that create data, SQL Server automatically creates matching user and schema Recommendation: Data should be created through explicit Windows or SQL Server login
Use group logins for data readers or data editors
Esri UC Administering Your Microsoft SQL Server Geodatabase

31. Points to remember
Creating a user does not give access to data in the database
It must be granted by the data owner
ArcGIS tools manage permissions on all parts of a feature class
Creating a user with the Create User tool will grant permissions sufficient for creating data
Esri UC Administering Your Microsoft SQL Server Geodatabase

32. How do I… make sure my data is safe?

33. (and practice restoring it)
BACKUP YOUR DATA NOW!!!
(and practice restoring it)
Esri UC Administering Your Microsoft SQL Server Geodatabase

34. How do I make sure that my data is safe?
Backups allow you to recover from:
Media failures
User errors
Hardware failures
Natural disasters
Also, backups can be used for:
Copying or moving data between servers
Setting up database mirroring or AlwaysOn
Use BACKUP command or Backup task in Management Studio
Esri UC Administering Your Microsoft SQL Server Geodatabase

35. Points to remember
Backups are the only way to reliably protect your data
Decide how much time you can afford to lose when disaster strikes and data must be restored
Create a restore plan that will achieve that goal
Create a backup plan that supports your restore plan
Implement your plan
Test your recovery plan regularly by using real backup media to restore to a system capable of being used in production
Esri UC Administering Your Microsoft SQL Server Geodatabase

36. How do I… maintain good performance?

37. How do I maintain good performance?
Standard maintenance
Reconcile/Post/Compress
Rebuild Indexes
Update Statistics
Layer scale dependencies
Spatial data performance - Spatial Index
Is it being used?
Is it the right index?
Manual grid vs Auto grid
Esri UC Administering Your Microsoft SQL Server Geodatabase

38. Spatial Indexes Chet Dobbins
Esri UC Administering Your Microsoft SQL Server Geodatabase

39. Spatial index performance
Use Auto grid indexes
Default spatial index type for ArcGIS 10.3.x and higher
Points – test using Manual grid with High on all 4 levels
Extents
Make your spatial index extent is >= feature class extent
Keep SQL Server current
Apply Service Packs & Cumulative Update Patches
Esri UC Administering Your Microsoft SQL Server Geodatabase

40. Thank you
Questions?

41. Please take our Survey Find your event in the Esri Events App
Your feedback allows us to help maintain high standards and to help presenters
Find your event in the Esri Events App
Find the session you want to review
Scroll down to the bottom of the session
Answer survey questions and submit
Esri UC Administering Your Microsoft SQL Server Geodatabase