SQL Server Requirements
SQL Server Installed Components
- Database Engine Services
SQL Server Naming Conventions
Do not use special characters for server names.
SQL Server User Access
- SYSADMIN Server role.
- MINIMUM SQL Server User Accesses required to install or upgrade Plant
Applications when SYSADMIN Server role is not available for the Database
User.
To install Plant Applications, the following configurations are required for the database user:
- Server Role:
- processadmin
- public
- setupadmin
- Mapping for Database User with Server Roles
For example:
For This Database Use This Database User Role msdb - public
- SQLAgentUserRole
Plant Applications Database (SOADB) - db_owner
- public
tempdb public - Securables
You can set the following permissions (WITH GRANT) for the database users:
- Connect Any Database
- Alter any login
- Connect SQL
- Create any database
- View any definition
- View any database
- View server state
Note: For msdb users, you must give access to the following with permissions as shown in the table:Access To This Permission Table Select 'WITH GRANT' View Select 'WITH GRANT' Stored procedure Execute 'WITH GRANT'
- Server Role:
Supported SQL Server Cloud
The following two versions (or flavors) of Cloud SQL are supported:
- AWS Relational Database Service (RDS)
- Azure
Supported Network Protocols
Before installing SQL Server, the stand-alone named and default instances must support the following network protocols:
- Shared memory (Shared memory is not supported on failover clusters)
- Named pipes
- TCP/IP
The same network protocol must be set up on the server and client computers to be able to communicate with each other.
SQL Server Browser Service and Plant Applications Server
Microsoft System CLR Types SQL Server 2016 (32-bit only) must be installed.
If you are installing Plant Applications Server on a computer and SQL Server on a different computer, the SQL Server Browser service (sqlbrowser) must be running before installing Plant Applications Server.
For information on the SQL Server Browser service, see: http://msdn2.microsoft.com/en-us/library/ms165724.aspx
Enabling TCP/IP and XP_cmdshell
The xp_cmdshell option and the TCP/IP protocol, which are disabled by default, must be enabled. The installation process verifies whether the TCP/IP protocol is enabled and if it is not enabled, a message box appears asking permission to enable the TCP/IP protocol. If permission is denied, the installation process will quit. The xp_cmdshell option is automatically enabled during the installation process.