Catalog Source Configuration > Microsoft SQL Server > Before you begin
  

Before you begin

Before you create a catalog source, verify that you have the information required to connect to the source system.
Complete the following prerequisite tasks:

Verify permissions

To extract metadata and to configure other capabilities that a catalog source might include, you need account access and permissions on the source system. The permissions required might vary depending on the capability.

Permissions to extract metadata

To extract Microsoft SQL Server metadata, you need access to the Microsoft SQL Server source system.
Grant permissions that allow you to perform the following operations:

Permissions to run data profiles

Ensure that you have the required permissions to run profiles.
Grant SELECT permissions on tables and views that you want to profile.

Permissions to run data classification

You don't need any additional permissions to run data classification.

Permissions to run relationship discovery

You don't need any additional permissions to run relationship discovery.

Permissions to run glossary association

You don't need any additional permissions to run glossary association.

Create a connection

Before you configure the Microsoft SQL Server catalog source, create a connection object in Administrator.
If you use a Windows agent for the SQL Server connector with Windows Authentication v2, specify the login credentials in the Windows agent properties.
    1In Administrator, select Connections.
    2Click New Connection.
    3Enter the following connection details:
    Property
    Description
    Connection Name
    Name of the Microsoft SQL Server connection. Must be unique within the organization.
    Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -
    Maximum length is 100 characters.
    Connection names are not case sensitive.
    Description
    Optional description of the connection.
    Maximum length is 255 characters.
    Type
    Type of connection. Ensure that the type is SQL Server.
    4Enter properties specific to the Microsoft SQL Server connection:
    Property
    Description
    Runtime Environment
    The execution platform that runs tasks. The runtime environment is either a Secure Agent or a serverless runtime environment.
    SQL Server Version
    Microsoft SQL Server database version.
    Authentication Mode
    The authentication method to connect to Microsoft SQL Server.
    Select one of the following authentication modes:
    • - SQL Server Authentication. Use the Microsoft SQL Server user name and password to connect to Microsoft SQL Server.
    • - Active Directory Password. Use the Microsoft Azure Active Directory user name and password to authenticate and to access a Microsoft Azure SQL Database.
    • - Windows Authentication v2. Use this authentication method to access Microsoft SQL Server using the agent hosted on a Linux or Windows machine. When you choose this option on Linux, enter your domain name and Microsoft Windows credentials to access Microsoft SQL Server.
    • - Kerberos. Use Kerberos authentication to connect to Microsoft SQL Server. When you choose this option, ensure that the user account that starts the Secure Agent service is available in the Microsoft SQL Server database. You don't need to enter your credentials to access Microsoft SQL Server.
    User Name
    Name of the Microsoft SQL Server user account that connects to the Microsoft SQL Server database.
    Password
    Password to connect to the Microsoft SQL Server database.
    Host
    Host name of the machine where the Microsoft SQL Server database runs.
    Port
    Port number for the Microsoft SQL Server database engine service.
    Code Page
    Code page associated with the Microsoft SQL Server database.
    Schema
    A list of schema for which you want to extract metadata.
    Database Name
    Name of the Microsoft SQL Server database to connect to.
    Encryption Method
    The method that the Secure Agent uses to encrypt the data exchanged between the Secure Agent and the database server.
    Default is None.
    Crypto Protocol Version
    Cryptographic protocols to use when you enable SSL encryption.
    Validate Server Cerificate
    Validates the certificate that is sent by the database server. If you specify the Host Name in Certificate property, the Secure Agent also validates the host name in the certificate.
    Trust Store
    The location and name of the truststore file. For the serverless runtime environment, specify the following certificate path in the serverless agent directory:
    /home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<TrustStore_filename>
    Trust Store Password
    The password to access the contents of the truststore file.
    Host Name in Certificate
    Host name of the machine that hosts the secure database.
    If you specify a host name, the Secure Agent validates the host name included in the connection against the host name in the SSL certificate.
    5Click Test Connection.

Import a relationship inference model

Import a relationship inference model if you want to configure the relationship discovery capability. You can either import a predefined relationship inference model, or import a model file from your local machine.
    1In Metadata Command Center, click Explore on the navigation panel.
    2Expand the menu and select Relationship Inference Model. The following image shows the Explore page with the Relationship Inference Model menu:The image shows the Explore page with the Relationship Inference Model menu and the Import Predefined Content options.
    3Select one of the following options:
    The imported models appear in the list of relationship inference models on the Relationship Discovery tab.