Running the grantusr.sql scripts on Azure SQL

This topic explains how to run the grantusr_azure_master.sql and grantusr_azure_siebeldb.sql scripts to set up necessary logins and users for Siebel CRM on Azure SQL.

Before you install the Siebel database, the Database Administator (DBA) must review, modify, and execute the grantusr_azure_master.sql and grantusr_azure_siebeldb.sql scripts.

This task is part of Creating Table Owner and Administrator Accounts.

Note: For Azure SQL Databases, you must split your traditional grantusr.sql script into two separate scripts, but these scripts do the same fundamental steps as are done against Microsoft SQL Server (On Premises) databases.

Both the scripts are located in the DBSRVR_ROOT\MSSQL subdirectory.

Note: For purposes of these instructions, the following assumptions are made:

• Your database owner is "SIEBEL"

• Your Siebel database is named as "siebeldb"

You must adjust the scripts if either of these is not the case.

As an administrator execute these scripts against the database, to set up minimum database logins and users.

1. Prepare and run the grantusr_azure_master.sql script:

   The grantusr_azure_master.sql script creates database logins for the SADMIN (Siebel administrator) account, the table owner (SIEBEL) account, various GUEST* accounts, and the LDAPUSER account.

   1. Specify the desired passwords for these users in the following lines at the top of the script:

      For example, for the SIEBEL user, update the following line:

      INSERT INTO #Logins VALUES (1, N'SIEBEL', ''); to INSERT INTO #Logins VALUES (1, N'SIEBEL', '********'); Where ******** is your desired password.

   2. You may also optionally add more logins if you plan to use Database Authentication in this environment, but Siebel CRM Production environments should not use Database Authentication.

   3. After editing the script, execute it against the master db.

      Note:

      The script performs the following validations:

      • The password cannot be blank.
      • The password cannot be the same as the login name.
      • If the login already exists, it will not be recreated.
      • Any database password complexity or other requirements will be enforced by the database, not the script.

2. Prepare and run the grantusr_azure.siebeldb.sql script

   The grantusr_azure_siebeldb.sql script creates users in the siebeldb.

   Note: For an explanation of the difference between logins and users, refer to the Microsoft documentation.

   1. Before running the script, the DBA must ensure that the following variables at the top of the script are set:

      • --@Role specifies the database role that will be given to all the other users to provide access to the Siebel data. This is typically "SSE_ROLE".

      • --@TableOwner specifies the database owner (dbo) for the siebeldb. This is typically SIEBEL.

      • --@systemAdmin is used temporarily during the process of changing the dbo to the @TableOwner. This can be almost any user (other than @TableOwner), but for simplicity, just use the login of the system user that is executing the script.

   2. After editing the script, execute it against the siebeldb.