Before you begin

• •Ensure that you have the required permissions to extract metadata and to configure other capabilities.
• •Configure a connection to the Microsoft SQL Server source system in Administrator.
• •If the source system is SSL-enabled, specify appropriate values for the Trust Store field when you create a connection to the Microsoft SQL Server source system. The data profiling task for an SSL-enabled Microsoft SQL Server database might fail if you don't specify the truststore value.
• •Create endpoint catalog sources for connection assignment.
• •Optionally, if you want to identify pairs of similar columns and relationships between tables within a catalog source, import a relationship inference model.

Verify permissions

Permissions to extract metadata

• •Configure VIEW DEFINITION permission for the user account.

• •select on sys.all_columns
• •select on sys.all_objects
• •select on sys.all_parameters
• •select on sys.database_principals
• •select on sys.databases
• •select on sys.foreign_key_columns
• •select on sys.indexes
• •select on sys.index_columns
• •select on sys.partitions
• •select on sys.schemas
• •select on sys.sql_modules
• •select on sys.synonyms
• •select on sys.tables
• •select on sys.extended_properties
• •select on sys.external_data_sources
• •select on sys.types
• •select on sys.table_types
• •select on sys.external_tables

Permissions to run data profiles

Permissions to run data classification

Permissions to run relationship discovery

Permissions to run glossary association

Create a connection

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

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:
3Select one of the following options:
• - Import Predefined Content. Imports a predefined relationship inference model called Column Similarity Model v1.0.
• - Import. Imports the predefined relationship inference model from your local machine. Select this if you previously imported predefined content into your local machine and the inference model is stored on the machine.
To import a file, click Choose File in the Import Relationship Inference Model window and navigate to the model file on your local machine. You can also drag and drop the file.
The imported models appear in the list of relationship inference models on the Relationship Discovery tab.