When using a Gateway for Popdock, it is recommended that you create a SQL user to use exclusively for the Gateway. It is not recommended to use the SQL sa account. This document will cover all the necessary information regarding the creation and permissions for this SQL user to work with the Gateway.
Credentials
This user must be created using SQL Server authentication. Windows authentication will not work for the Gateway. The username can be whatever you want, but we recommend that the username is related to Popdock in some way (ex: GatewayUser, Popdock, PopdockGateway, etc.).
For the password, you may not want to enforce password expiration since this is a service account. The password should be stored in a secure place for future reference.
Everything else in this section of the user properties can remain as the default options.
Server Role
You can leave the default set to public unless you prefer to change it.
User Mapping
User mapping is the key to getting this user to work correctly with the Gateway. The user will need to be granted permission to any database where they need access. The user will need the db_datareader role for the each database, in order to access the metadata for the tables.
They will also need to be assigned the default schema of that database (default is typically dbo) to be able to access the data. You will need these permissions on every database in your server that you want to access in Popdock.
Having trouble creating the user for the Gateway? Email support at support@eonesolutions.com
