Product: Kryon RPA

Product Version: N/A

Components: Database

Article Contributors: Kryon CS

Prerequisites: N/A

Symptom: Failure to create a DB trigger.

Cause: A very large schema.

Resolution:

The following process covers the creation of a read-only user with limited access to specific tables in DB in order to monitor DB events.

In this example we use the following values that may be changed according to internal convention and security needs:
 

1.        The SQL username à TempUser
2.        Table to be tracked à MyTable
3.        Database name à MyDB
4.        Database Server à MyServer

Workaround:

Step 1: Configure New SQL User

• Open Microsoft SQL Server Management Studio (SSMS)
• Login to MyServer with a user that has permissions to add users and grant permissions.
• Right click on "Security" --> "New" --> "Login…"

 

• Create a new SQL user:

• Open a new query editor and execute the following query (after changing to your values):

 

 

 

 

USE

 

 

 

 


Step 2: Create DB Trigger

• Use the following connection string example:

 

 

 

Provider=SQLOLEDB.1;Password=<Password>;Persist Security Info=True;User ID=TempUser;Initial Catalog=MyDB;Data Source=MyServer

 

 

 


**The list of tables should show only the tables that the user has access to.