Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Administrator
  • All Products

Table of Contents

Search

  1. Connectors and connections
  2. Connection configuration
  3. Connection properties
  4. Swagger file generation for REST V2 connections

Connections

Connections

Back Next

Microsoft SQL Server connection properties

Microsoft SQL Server connection properties

When you set up a Microsoft SQL Server connection, configure the connection properties.
The following table describes the Microsoft SQL Server connection properties:
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.
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
You cannot run a database ingestion task on a Hosted Agent or serverless runtime environment.
SQL Server Version
Microsoft SQL Server database version.
Authentication Mode
Authentication method to access Microsoft SQL Server.
Select one of the following methods:
  • SQL Server Authentication. Uses your Microsoft SQL Server user name and password to access Microsoft SQL Server.
  • Windows Authentication (Deprecated). Uses the Microsoft Windows authentication to access Microsoft SQL Server.
    This option is available when you access
    Data Integration
    or
    Mass Ingestion
     by using Microsoft Windows.
    When you choose this option, you don't need to enter credentials to access Microsoft SQL Server and ensure that the user account that starts the
    Secure Agent
     service is available in the Microsoft SQL Server database.
    If you use
    Mass Ingestion Databases
     and want to use Windows authentication, select this option.
    Windows authentication is not certified for Microsoft SQL Server 2017 version hosted on Linux.
    You can't configure Windows Authentication when you use a serverless runtime environment.
  • Active Directory Password. Uses the Azure Active Directory user name and password to authenticate and access the Microsoft Azure SQL Database.
  • Windows Authentication v2. Uses this authentication method to access Microsoft SQL Server from
    Data Integration
     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.
    When you choose this option on Windows, ensure that the user account that starts the
    Secure Agent
     service is available in the Microsoft SQL Server database.
    You can't configure Windows Authentication when you use a serverless runtime environment.
  • Kerberos.
    Uses 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.
    You can't configure the Kerberos authentication when you use a Hosted Agent or serverless runtime environment.
Domain
Applies to Windows Authentication v2.
The domain name of the Windows user.
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
For Windows Authentication v2, specify the Windows NT user name.
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.
For Windows Authentication v2, specify the Windows NT password.
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.
Instance Name
Instance name of the Microsoft SQL Server database.
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.
Schema
Schema used for the target connection.
Code Page
The code page of the database server.
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.
Metadata Advanced Connection Properties
Additional properties for the JDBC driver to fetch the metadata.
If you specify more than one property, separate each key-value pair with a semicolon.
Runtime Advanced Connection Properties
Additional properties for the ODBC driver to run
mappings
.
If you specify more than one property, separate each key-value pair with a semicolon.
0 COMMENTS
We’d like to hear from you!