Configuring an ADF Linked Service Connection for Sybase
For information on how to enable a connection for use with linked services, see Configuring a Linked Service Connection.
Field labels in this walkthrough follow the underlying Azure Data Factory property names, with the connection column that carries each value named alongside. The exact labels shown in the BimlFlex Connection Editor may differ.
After selecting Sybase from the Linked Service Type dropdown, the form required for creating a Sybase Linked Service will appear.
Source Only Connector
A Sybase connection is used as a source. It is not available as a target.
Each object is read through a dataset parameterized on table, and the query on the copy source reads the object.
Choosing an Authentication Method
| Method | Credentials | Additional Settings |
|---|---|---|
| Basic | User Name and Password | None |
| Windows | No credential fields in the form | None |
Recommendation: Store the Password in Azure Key Vault rather than entering it as plaintext.
Complete Example: Basic Authentication with Azure Key Vault
| Field | Example Value |
|---|---|
| Connect via Integration Runtime | bfx-shir |
| Server | sybase.contoso.com |
| Database | SALES |
| Authentication Type | Basic |
| Username | bfx_reader |
| Azure Key Vault Linked Service | bfx-kv |
| Secret Name (for Password) | BFX-SRC-SybasePassword |
Required Fields
Common Required Fields
Some required fields for a Sybase Linked Service connection depend on the Authentication Type used. There are some fields that are required regardless of Authentication Type.
These common required fields are:
Authentication Type Dependent Required Fields
Required fields for Basic:
- Username
- Password (or Azure Key Vault)
Connect via Integration Runtime
Connect via Integration Runtime names the integration runtime for a Sybase Linked Service connection, and it must name a self-hosted integration runtime.
Azure Data Factory reaches a Sybase database only through a self-hosted integration runtime, and the data provider for Sybase iAnywhere.Data.SQLAnywhere 16 or above must be installed on the integration runtime machine.
To use another runtime, select it from the dropdown or choose + New to add one.
When a custom value is saved in the linked service form, it will be added to the custom integration runtimes.
The custom values that appear in this dropdown can be maintained in Settings under Azure - AzureIntegrationRuntime.
The runtime is stored in the connection's LS_ConnectVia_IntegrationRuntime column. Any value other than AutoResolveIntegrationRuntime is written to the linked service as the runtime it connects through.
Server
The Server names the Sybase server the connector reads from (for example, sybase.contoso.com).
It is stored in the connection's LS_Server column and maps to the ADF server property.
Database
The Database names the Sybase database the connector reads from (for example, SALES).
It is stored in the connection's LS_Db column and maps to the ADF database property.
Authentication Type
The Sybase Linked Service connection can use Basic or Windows authentication.
The selected value is stored in the connection's LS_AuthenticationType column and maps to the ADF authenticationType property.
When using Basic, a Username and Password are required.
For Windows, the form takes no Username or Password.
Basic
Basic authentication signs in to the Sybase database with a Username and Password.
The Username is stored in the connection's LS_Username column and maps to the ADF username property.
The Password field accepts the password as plaintext in the LS_Password column, or an Azure Key Vault reference held in the LS_PasswordKVS_ fields that resolves to the password at runtime. It maps to the ADF password property.
It is suggested that Azure Key Vault be used in place of manually entering the Password.
Azure Data Factory Linked Service Additional Information
For additional information on ADF Sybase Linked Service and its connection requirements see the Azure Data Factory Sybase Connector documentation.