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 connection.
    Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
    Maximum length is 255 characters.
    Description
    Description of the connection. Maximum length is 4000 characters.
    Type
    Type of connection.
    Select SQL Server from the list.
    4Enter properties specific to the Microsoft SQL Server connection:
    Property
    Description
    Runtime Environment
    The name of the runtime environment where you want to run the tasks.
    A runtime environment is either Informatica Cloud Secure Agent or a serverless runtime environment.
    SQL Server Version
    This property is not applicable for Microsoft SQL Server Connector.
    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
    User name for the database login. The user name can't contain a semicolon.
    To connect to Microsoft Azure SQL Database, specify the user name in the following format: username@host
    If you use Windows Authentication v2 on Windows, the user name is used as follows:
    • - During design time, the agent uses the user name specified here to test the connection.
    • - During runtime, the Microsoft SQL server driver ignores the user name specified in this field and uses the credentials of the user who started the Secure Agent service.
    If you use Windows Authentication v2 on Linux, the user name specified here is used both during design time and runtime.
    Note: This property is not applicable if you use the Windows Authentication mode to access Microsoft SQL Server.
    Password
    Password for the database login. The password can't contain a semicolon.
    If you use Windows Authentication v2 on Windows, the password is used as follows:
    • - During design time, the agent uses the password specified here to test the connection.
    • - During runtime, the Microsoft SQL server driver ignores the password specified in this field and uses the credentials of the user who started the Secure Agent service.
    If you use Windows Authentication v2 on Linux, the password specified here is used both during design time and runtime.
    Note: This property is not applicable if you use the Windows Authentication mode to access Microsoft SQL Server.
    Host
    Name of the machine hosting the database server.
    To connect to Microsoft Azure SQL Database, specify the fully qualified host name.
    For example, vmjcmwxsfboheng.westus.cloudapp.azure.com.
    Port
    Network port number used to connect to the database server.
    Default is 1433.
    Code Page
    The code page of the database server.
    Schema
    Schema used for the target connection.
    Database Name
    Database name for the Microsoft SQL Server target connection. Database name is case-sensitive if the database is case-sensitive. Maximum length is 100 characters.
    Database names can include alphanumeric and underscore characters.
    Encryption Method
    The method that the Secure Agent uses to encrypt the data sent between the driver and the database server. You can use the encryption method to connect to Microsoft Azure SQL Database.
    Default is None.
    Crypto Protocol Version
    Cryptographic protocols to use when you enable SSL encryption.
    Validate Server Certificate
    When set to True, Secure Agent validates the certificate that is sent by the database server.
    If you specify the HostNameInCertificate parameter, Secure Agent also validates the host name in the certificate.
    When set to false, the Secure Agent doesn't validate the certificate that is sent by the database server.
    Trust Store
    The location and name of the truststore file. The truststore file contains a list of Certificate Authorities (CAs) that the driver uses for SSL server authentication.
    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 with 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.