SQL Server as a target
The SQL Server target endpoint supports both cloud and on-premises databases. To connect to an on-premises database, your environment must have a self-managed Groundplex configured in the Classic Manager shared folder. Refer to Connect to on-premises endpoints for more information.
When you select SQL Server, if AutoSync detects that a Groundplex is available, a dialog opens that enables you to select a cloud or on-premises database. For an on-premises database, you must also select a Groundplex.
Supported account types
Designer and Classic Manager provide multiple account types for most endpoints and not all types are compatible with AutoSync. When you create or edit a data pipeline, the existing credentials list only includes compatible Accounts.
For SQL Server, AutoSync supports:
- SQL Server Account
Connection configuration
SQL Server properties include the following:
- Account Properties:
- Credential label: A unique, meaningful name such as
SQL-Server-Sales
. If a configuration with the same name exists, AutoSync displays anAsset conflict error message
. - Hostname: The name of the machine hosting the database.
- Port Number: The port number to connect to the database. Default value:
1433
- Database name: The name of the database. For example,
MyDB
. - Username: A username for an account with the correct permissions for AutoSync to synchronize data.
- Password: The password for the account. Multiple retries with an invalid password can cause your account to be locked.
- Share: (Optional) Select a user group to share this configuration with. Org admins create user groups to share credentials. If you are a member of a user group, you can select it from the dropdown. You can also select the global shared folder, which shares the credentials with everyone in your Org.
- Credential label: A unique, meaningful name such as
- Validate and save: After saving and validating, AutoSync adds the configuration to the list of saved credentials.
- Select schema: AutoSync populates this list from the account. Choose the schema that contains the tables to load as a source.