ONLY USE THIS STEP IF A SERVER WAS ALREADY IN PLACE AND IS TO BE REUSED OR FOR SOME OTHER CUSTOM SQL MODIFICATIONS !!!

If an Existing SQL Server is in Place or you require to pre-create the RuleSoft Database container then the below information should be read.

An Existing SQL Server or Express Server is fine to use (load permitting).

Read the following "Cases" to determine which applies to you...

SQL Server and "sysadmin" cannot be granted (IT department rules typically)

Have your IT group create a Database Named in the format "CompanyName_System" where "CompanyName" is replaced with a short acronym of YOUR companies name or Division Name.

AVOID USING "RULESOFT_System" or other similar names such as "RS_System", "CPD_System".
The reason is that these names are already in use publicly by us in shared environments.
If the Prefix before "_system" is duplicated you will only be able to login to ONE system concurrently. The primary issue is that often people will "Test" using our public systems and then COPY and PASTE there data to the local system later (cannot be done with a duplicate).

Have the IT group create an SQL Account (User) that has "dbo" (database owner) access to the database that was previously created.

"dbo", for the one database, is all that is required for the program to operate correctly. sysadmin is only used to create the database for you via the program automated configuration utility.

SQL Server Controls Pro User Account needs to be set to "dbo" after install (often due to IT Policies)

In the SQL Server Manager, under the Object Explorer tree, Expand the "Database Instance", "Security", "Logins" Node.

Ensure the "CompanyName_Server" database has already been created by either the IT group or the RuleSoft program.

Under "Logins" find the "Controls Pro" User and open it's properties window (double click, right click)

Clear the "sysadmin" checkbox on the "Security" page.

Change to "User Mapping" Page.

Select the Database in grid marked "Users mapped to this login:" and ensure it is "Checked". After selection the lower list labeled "Database role membership for:..." should be re-populated.

In the lower Database Role List check "db_owner". This marks the user as "dbo" for this specific database.

Select "OK"