Database User Permission Requirements

Overview

EMS Loop consists of three (3) distinct components, Windows connector services installed on your network accessible to your CAD database, EMS Loop Website and the EMS Loop Mobile applications.

In order for EMS Loop to connect to your CAD system and provide services that interact with your system, the Windows services need to access your CAD database. The user account that is used to access your database will be configured through the Windows connector services installer (EMS Loop Consolidated Installer) when the Windows services are installed.

This document will outline the permissions that the provided user will need to successfully be able to communicate with EMS Loop and your CAD.

This document provides commands that can be run against your database server. Since these commands will be run against a production database server, ensure you are taking the proper precautions before running these commands such as running backups. Commands should only be run against a production database server by a qualified Database Professional. EMS Loop is not responsible for any data loss, corruption or damage from running these commands in an importer way.

General Requirements

The following are general requirements for your SQL Server, and are required for EMS Loop to function properly.

• SQL Server 2012 R2 or later

• .NET Framework 4.5.1 or later versions

• SQL Server service broker enabled for the databases required for your CAD System

SQL Server Database Requirements

The EMS Loop services utilize the Service Broker technologies built into Microsoft SQL Server. In order for the EMS Loop services to communicate correctly, the Service Broker functionality must be enabled for your CAD database. The following table defines which database requires this functionality based on the supported CAD System.

With ZOLL Data Systems RescueNet Dispatch product the database can be named something other than the default of (RCSQL) check with your CAD Administrator if you’re unsure of the database name.

To ensure that the Service Broker functionality is enabled for your database the following command can be run in a query window for the appropriate database above.

SELECT is_broker_enabled FROM sys.databases WHERE name = '[YOUR DATABSE HERE]';

If your database is not enabled for Service Broker functionality you can enable it by running the following command in a query window.

ALTER DATABASE [DATABASE NAME] SET ENABLE_BROKER

SQL Server USER Permissions

You can supply the installer any user you wish, as long as the user defined within your database server has the following permissions to your CAD database. The following table outlines the databases for each CAD that the EMS Loop user will need access to.

With ZOLL Data Systems RescueNet Dispatch product the database can be named something other than the default of (RCSQL) check with your CAD Administrator if you’re unsure of the database name.

The following permissions are required for the EMS Loop user to function properly.

• ALTER

• CONNECT

• CONTROL

• CREATE CONTRACT

• CREATE MESSAGE TYPE

• CREATE PROCEDURE

• CREATE QUEUE

• CREATE SERVICE

• EXECUTE

• INSERT

• SELECT

• SUBSCRIBE QUERY NOTIFICATIONS

• UPDATE

• VIEW DATABASE STATE

• VIEW DEFINITION

If the user that you’re supplying for EMS Loop is in one of the following groups then the above permissions should already granted.

• Administrator

• db_owner

• db_owner role

Before installing EMS Loop please ensure the above permissions are granted for the user you’re providing for EMS Loop’s use even if the user is a member of one of the above groups / roles.

The following query can be run in a SQL Query window and will show you the permissions granted to the user you supply in the query. Replace [YOUR USER HERE] with the user you’re providing the EMS Loop services to check the permissions granted.

SELECT dp.class_desc, dp.permission_name, dp.state_desc,
ObjectName = OBJECT_NAME(major_id), GranteeName = grantee.name, GrantorName = grantor.name
FROM sys.database_permissions dp
JOIN sys.database_principals grantee on dp.grantee_principal_id = grantee.principal_id
JOIN sys.database_principals grantor on dp.grantor_principal_id = grantor.principal_id
WHERE grantee.name = '[YOUR USER HERE]'