Create the Database User and Grant User Access

You use the Microsoft SQL Server Management Studio to create the database user for your SIMULIA Execution Engine. The steps provided here are for Microsoft SQL Server 2019 databases. Other database products will have different administrative tools to accomplish these tasks.

  1. Access the Database Configuration Assistant using one of the following methods:
    • Windows: Launch Microsoft SQL Server Management Studio from Start menu.
    • Linux: no UI available. Either connect it from windows Microsoft SQL Server Management Studio or use sqlcmd for creating new database user account for Isight.
  2. Log in to Microsoft SQL Server Management Studio.
  3. After successful login, press New Query, copy the SQL code below, and paste it into the new query window.

                    
    CREATE LOGIN <DATABASE_LOGIN>
        WITH PASSWORD    = '<DATABASE_PASSWORD>',
        CHECK_POLICY     = OFF,
        CHECK_EXPIRATION = OFF,
        DEFAULT_DATABASE = [<DATABASE_NAME>];
    GO
    
    USE [<DATABASE_NAME>];  
    GO  
    
    CREATE USER [<DATABASE_LOGIN>] FOR LOGIN [<DATABASE_LOGIN>];  
    GO  
    
    GRANT CREATE TABLE,
          ALTER,
          REFERENCES,
          SELECT,
          INSERT,
          UPDATE,
          DELETE
    ON DATABASE::<DATABASE_NAME> TO <DATABASE_LOGIN>;
    GO                
    

    Where:

    <DATABASE_NAME> - Name of the database

    <DATABASE_LOGIN> - Login name for the new user account

    <DATABASE_PASSWORD> - Password for the new user account

    Note:
    • The user script does not grant database administrator (DBA) permissions to the user account.
    • In SQL Server it is necessary to create a LOGIN first, then a USER; they are two different entities with different purposes.
    • The CREATE DATABASE statement purposely omits any COLLATION option, so it will pick up the default collation specified during the SQL Server installation.
    • All string literals surrounded by single quotes use the default character encoding scheme. To force SQL Server to use Unicode for these string literals, prepend the N prefix as explained in the following Microsoft support article:

      https://docs.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-ver15

      For example,

      NAME = '<db_name>'

      becomes NAME = N'<db_name>'