The SQL Server must be configured as follows:
Allow both SQL Server and Windows authentication (Mixed Mode).
Use the Local System account in the Services Accounts screen.
Select Latin1_General Accent-sensitive for the Collation settings.
The Application User must be granted a SQL Server login to the database server that is to be used by Agile Business Suite. The login is case-sensitive and must be in the same case as specified in the Windows Security Accounts Manager database.
Notes:
The imported Model database has to be this collation sequence of LATIN1_General_CI_AS because it is case-sensitive considering LDL is casesensitive as well. If the imported Model has a different collating sequence, AB Suite might function unpredictably. Also, note that this collating sequence does not affect Kanji because it uses Unicode for most strings.
Also note that the System Modeler always creates its repository with the collation sequence it requires regardless of the SQL Server Instance default, which is Latin1_General_CI_AS. Runtime Administrators are free to install SQL Server under any kind of collation sequence database they like and Admin Tool can prepare it for use for Runtime.
Some Servers, which have non English locales might require a different collation sequence. Contact your CSC to determine the best collation sequence for your locale. For example, a Latvian locale requires the Latvian_100_Bin.
Configuring the Default ‘sa’ Account
When SQL Server is installed, by default the ‘sa’ account is created with a blank password. In order to ensure that unauthorized users do not gain access to your server, it is recommended that you assign a password to the ‘sa’ account. If a password is not assigned and an unauthorized user gains access using the ‘sa’ account, they will have full control of all databases contained on your server.