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
  • Informatica Data Quality 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding Domains
  3. Managing Your Account
  4. Using Informatica Administrator
  5. Using the Domain View
  6. Domain Management
  7. Nodes
  8. High Availability
  9. Connections
  10. Connection Properties
  11. Schedules
  12. Domain Object Export and Import
  13. License Management
  14. Monitoring
  15. Log Management
  16. Domain Reports
  17. Node Diagnostics
  18. Understanding Globalization
  19. Managing Distribution Packages
  20. Appendix A: Code Pages
  21. Appendix B: Custom Roles
  22. Appendix C: Informatica Platform Connectivity
  23. Appendix D: Configure the Web Browser

Administrator Guide

Administrator Guide

Back Next

MS SQL Server Connection Properties

MS SQL Server Connection Properties

Use a Microsoft SQL Server connection to access Microsoft SQL Server. A Microsoft SQL Server connection is a connection to a Microsoft SQL Server relational database. You can create and manage a Microsoft SQL Server connection in the Administrator tool or the Developer tool.
The order of the connection properties might vary depending on the tool where you view them.
The following table describes MS SQL Server connection properties:
Property
Description
Database Type
The database type.
Name
Name of the connection. The name is not case sensitive and must be unique within the domain. The name cannot exceed 128 characters, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
ID
String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name.
Description
The description of the connection. The description cannot exceed 765 characters.
Use trusted connection
Enables the application service to use Windows authentication to access the database. The user name that starts the application service must be a valid Windows user with access to the database. By default, this option is cleared.
Windows and NTLM authentication is not certified for a Microsoft SQL Server 2017 version hosted on Linux.
User Name
The database user name. Required if Microsoft SQL Server uses NTLMv1 or NTLMv2 authentication.
Password
The password for the database user name. Required if Microsoft SQL Server uses NTLMv1 or NTLMv2 authentication.
Pass-through security enabled
Enables pass-through security for the connection. When you enable pass-through security for a connection, the domain uses the client user name and password to log into the corresponding database, instead of the credentials defined in the connection object.
Metadata Access Properties: Connection String
Connection string used to access metadata from the database.
Use the following connection string: 
jdbc:informatica:sqlserver://<host name>:<port>;DatabaseName=<database name>
To test the connection with NTLM authentication, include the following parameters in the connection string:
  • AuthenticationMethod. The NTLM authentication version to use.
    UNIX supports NTLMv1 and NTLMv2 but not NTLM.
  • Domain. The domain that the SQL server belongs to.
The following example shows the connection string for a SQL server that uses NTLMv2 authentication in a NT domain named Informatica.com: 
jdbc:informatica:sqlserver://host01:1433;DatabaseName=SQL1;AuthenticationMethod=ntlm2java;Domain=Informatica.com
If you connect with NTLM authentication, you can enable the
Use trusted connection
 option in the MS SQL Server connection properties. If you connect with NTLMv1 or NTLMv2 authentication, you must provide the user name and password in the connection properties.
AdvancedJDBCSecurityOptions
Database parameters for metadata access to a secure database. Informatica treats the value of the AdvancedJDBCSecurityOptions field as sensitive data and stores the parameter string encrypted.
To connect to a secure database, include the following parameters:
  • EncryptionMethod. Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to SSL.
  • ValidateServerCertificate. Optional. Indicates whether Informatica validates the certificate that is sent by the database server.
    If this parameter is set to True, Informatica validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate.
    If this parameter is set to false, Informatica does not validate the certificate that is sent by the database server. Informatica ignores any truststore information that you specify.
  • HostNameInCertificate. Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate.
  • cryptoProtocolVersion. Optional. If you enable TLS for the Microsoft SQL Server instance, set the cryptoProtocolVersion parameter as follows:
    cryptoProtocolVersion=TLSv<version number>.
    For example, cryptoProtocolVersion=TLSv1.2
    The version number must be the same as the TLS version you configured for the server.
  • TrustStore. Required. Path and file name of the truststore file.
    If you configure SSL or TLS and specify only the file name, you must copy the truststore file to the following directory to test the connection:
    <Informatica server installation directory>/tomcat/bin
  • TrustStorePassword. Required. Password for the truststore file for the secure database.
Not applicable for ODBC.
Informatica appends the secure JDBC parameters to the connection string. If you include the secure JDBC parameters directly to the connection string, do not enter any parameters in the AdvancedJDBCSecurityOptions field.
Data Access Properties: Provider Type
The connection provider that you want to use to connect to the Microsoft SQL Server database.
You can select the following provider types:
  • ODBC
  • Oldeb(Deprecated)
Default is ODBC.
Although the Microsoft SQL Server connection user interface shows the OLEDB provider type as deprecated, Informatica supports the OLEDB provider type. For more information about the OLEDB provider type support statement, see the following Knowledge Base article KB 522895.
Use DSN
Enables the Data Integration Service to use the Data Source Name for the connection.
If you select the Use DSN option, the Data Integration Service retrieves the database and server names from the DSN.
If you do not select the Use DSN option, you must provide the database and server names.
Connection String
Use the following connection string if you do not enable DSN mode: 
<server name>@<database name>
If you enable DSN mode, use the following connection strings: 
<DSN Name>
Code Page
The code page used to read from a source database or to write to a target database or file.
Domain Name
The name of the domain.
Packet Size
The packet size used to transmit data. Used to optimize the native drivers for Microsoft SQL Server.
Owner Name
The name of the owner of the schema.
When you generate a table DDL through a dynamic mapping or through the
Generate and Execute DDL
 option, the DDL metadata does not include schema name and owner name properties.
Schema Name
The name of the schema in the database. You must specify the schema name for the Profiling Warehouse if the schema name is different from the database user name. You must specify the schema name for the data object cache database if the schema name is different from the database user name and if you configure user-managed cache tables.
When you generate a table DDL through a dynamic mapping or through the
Generate and Execute DDL
 option, the DDL metadata does not include schema name and owner name properties.
Environment SQL
SQL commands to set the database environment when you connect to the database. The Data Integration Service runs the connection environment SQL each time it connects to the database.
Transaction SQL
SQL commands to set the database environment when you connect to the database. The Data Integration Service runs the transaction environment SQL at the beginning of each transaction.
Retry Period
This property is reserved for future use.
SQL Identifier Character
Type of character that the database uses to enclose delimited identifiers in SQL queries. The available characters depend on the database type.
Select (None) if the database uses regular identifiers. When the Data Integration Service generates SQL queries, the service does not place delimited characters around any identifiers.
Select a character if the database uses delimited identifiers. When the Data Integration Service generates SQL queries, the service encloses delimited identifiers within this character.
Support Mixed-case Identifiers
Enable if the database uses case-sensitive identifiers. When enabled, the Data Integration Service encloses all identifiers within the character selected for the
SQL Identifier Character
 property.
When the
SQL Identifier Character
 property is set to none, the
Support Mixed-case Identifiers
 property is disabled.
ODBC Provider
ODBC. The type of database to which ODBC connects. For pushdown optimization, specify the database type to enable the Data Integration Service to generate native database SQL. The options are:
  • Other
  • Sybase
  • Microsoft_SQL_Server
Default is Other.
0 COMMENTS
We’d like to hear from you!