Add Named Database Connection: Named Connections store (in a central location) authentication information associated with a user.
For information about setting up and using named connections, please see:
The host name of the MS SQL Server.
The name of the database to access.
Enter the username and password to access the database, user account, or wherever authentication is required.
When connecting through a Windows user account, the database can validate the account name and password using the Windows principal token in the operating system.
The user identity is confirmed by Windows, so if this checkbox is selected, the Username and Password parameters are ignored.
Note: This parameter is not present in the Azure SQL Database reader and writer. The Azure SQL Database reader and writer will always request Secure Sockets Layer (SSL) encrypted connections.
When selected, this parameter requests Secure Sockets Layer (SSL) encryption for the connection. If the server does not have a certificate trusted by the client machine, the connection will fail. Otherwise, data will be encrypted before traveling over the network. There are multiple ways to trust a server certificate on a client machine.
If this parameter is not selected, encryption behavior will be determined by encryption properties set for SQL Server Native Client, and for SQL Server.
Tip: When Encrypt Connection is selected, please provide a fully qualified Server name. For example, a server named safe-sql-server might have a fully qualified name of safe-sql-server.dev.safe. This fully qualified name should be an exact match for the server name on the trusted certificate.
Specifies whether to write geometry (planar data) or geography (geodetic data) when writing to tables. This parameter works only in combination with the Spatial Column parameter.
Specifies the geometry or geography column to use when writing to tables. This parameter works only in combination with the Spatial Type parameter.