---
title: "creating executable permissions in SQL"
canonical: "https://servicedesk.maxgeo.com/space/LC/1263566934/creating%20executable%20permissions%20in%20SQL"
format: markdown
---
<u>**Objective:**</u>

1. To enable 'stored procedures' to be executed within the SQL database - refer **Instructions Step 1**.

<u>**Instructions:**</u>

<span style="color: #bf2600">*This requires permissions to be created from within SQL Management Studio.  You should ensure that such creation does not breach IT, security or other company policy.  This should be done only by persons who have sufficient training and experience with SQL.  If such a person is unavailable to you, you are welcome to contact our team at *</span><span style="color: #bf2600">*[support@maxgeo.com](mailto:support@maxgeo.com)*</span><span style="color: #bf2600">*, noting that you are responsible for ensuring that direction issued to us is compliant with your company policies, as we take no repsonsibility.*</span>

1. Check to see if there is a role called "db_executor" (if you don't know where to find this - refer **Step 3**).
  - If you don't have this role, follow **Step 2 **through to the end.
  - If you do have this role, follow **Step 4** through to the end.
2. Run the following script in SQL Management Studio:
  - create role db_executor grant execute to db_executor
3. Open the following folder, and confirm you have the new role db_executor (you may have to refresh SQL):
  - Security: Users: Roles: Database Roles
4. Right-click this new "db-executor" and select "Properities", then "Add".  This opens a new window where you select all users that require these permissions, then click through "OK".
  - All users of LeaseControl Admin Licence (which has edit rights) are required to be added to db_executor.
5. If you are doing this due to receiving error, you should now go back to what you were doing to ensure everything now runs smoothly.

<u>**Additional Info:**</u>

- <u>*Why didn't I have to do this in an earlier version of LeaseControl?*</u>  Earlier versions had more limited functionality within the database.  For example, in V1.6.1 there were no stored procedures (which is a set of instructions to respond to a particular action).