The PINpoint application will open connections to the BES SQL Server every time:

• When data is pushed to BlackBerry devices
• When the PINpoint list is refreshed from the device side
• When the PINpoint Administrator is using the PINpoint management Console.

Please see below a description of how PINpoint interfaces with the BES SQL server:

1. PINpoint relies only on SQL authentication. Because of this the BES SQL server should be set-up to support Mixed Authentication.
2. At installation time PINpoint Standard Edition creates the following objects in the BESMgmt database:
   • A role called PINpoint_DataReader
   • Three in-line functions: USR_PINPOINT_GET_BLACKBERRY_USER, USR_PINPOINT_GET_BLACKBERRY_USERS, USR_PINPOINT_GET_CONTENT_LIST
   • The installer will grant SELECT rights to the above In-line functions to the PINpoint_DataReader role. [NB. in a more restricted environment this step could be skipped at installation time: the application ships with the actual SQL scripts that could be handed on to a DBA to run them manually.]
3. Our recommendation is to create a SQL Login that will be used by the PINpoint application to open connections to the BESMgmt database. This login at server level should be member of the public role and at BESmgmt database level should be mapped to a User that is member of the Public role and PINpoint_DataReader.
4. At PINpoint level at configuration time, the above login should be used to set-up the SQL Connection to the BESMgmt Database. This will limit the capabilities the PINpoint application has at SQL level to the three in-line functions specific to the PINpoint application.