There are two options for authentication with MS-SQL Server:

1. Windows Authentication
2. SQL Server Authentication

When using the Windows Authentication, the used user must be granted access rights for the database. That means, if later on different Windows users want to work with the eBiss Client, then all users need read & access rights for the database. It also has the consequence that a Windows user must be deposited in the eBiss (Windows) service. This can be any account, but it must be noted that this Windows account is never deactivated, otherwise the service would no longer run. Therefore it is recommended to store an employee-independent Windows account in the service, so that e.g. the account is not deactivated when the employee leaves.
Caution: The service must run under a Windows user and each new Windows user must be shared on the MS-SQL server or you create a group for it.

The second alternative is the SQL Server Authentication. You create an account in the database, which has the required read & access rights. This user can then be stored in the configurator for the database.
Caution: By storing a fixed SQL account, the login can be read out of the *.config files. What can be prevented by an encryption of the *.confg.