This screen allows a user to create a new SQL Server Database connection to use in a replication. Users will be asked to enter the type of SQL Server database being used, the Server name and instance, the database name, an authentication type of either "Windows Authentication", "SQL Authentication" or "Trusted Authentication", user name and password credentials for SQL and, in the case of Windows authentication, a domain is also required.
- Server name and instance, and authentication mode: Enter the name of the SQL server an instance e.g. localhost\sqlexpress would denote a SQL database on the local machine with an instance called SQL Express. Select the type of authentication in use. This can either be "SQL Authentication", "Windows Authentication" and "Trusted Authentication". Details of each type of authentication are covered in detail below.
- Database name and version: Type the name of the SQL Server database in "Database name" field and Select the version of SQL in use from the drop down.
- User Credentials: Depending on the authentication type used you may be asked to enter some user credentials. This is covered in greater detail in the types of authentication section below.
- Test connection button: Once you have filled in all the fields on the form, click the test connection to ensure SQList can talk to your SQL database with the credentials and settings you have supplied.
- Enable/Disable site: If you wish to disable replications that use this database connection uncheck this check box and save the profile.
- Next: Save the settings and continue.
- Cancel: Cancel this page.
- Help: Opens this help page.
Types of authentication - Examples
In this section, we discuss the various types of authentication used by SQList to connect to SQL Server or SQL Azure
When using SQL Server Authentication in a SQL DB, logins are created in SQL Server that are not based on Windows user accounts. Both the user name and the password are created by using SQL Server and stored in SQL Server. Simply provide this user name and password in the appropriate fields in SQList.
When a SQL Database is secured using a Windows user account, SQL Server validates the account name and password using the Windows principal token in the operating system. This means that the user identity is confirmed by Windows. Windows Authentication is the default authentication mode in SQL Server, and is much more secure than SQL Server Authentication. Windows Authentication uses Kerberos security protocol, provides password policy enforcement with regard to complexity validation for strong passwords, provides support for account lockout, and supports password expiration. A connection made using Windows Authentication is sometimes called a trusted connection, because SQL Server trusts the credentials provided by Windows.
To configure a connection to a SQL Server Database that uses Windows Authentication simply provide the windows username, password, and domain name.
Trusted authentication also uses Windows Credentials to connect to your SQL Server Database and requires Windows Authentication to be configured on SQL Database. In this case SQList requires that you enter your Windows Credentials to connect to SQL Server in the SQList Windows service. The SQList form does not require you to enter any credential details.