...
- Server: the name of the instance of SQL Server installed on the service, will be pre-filled from the previous page
- Database: the name of the database you want to create in SQL Server
- Authentication: the Active Directory option can be chosen for those SQL installs that don’t have any explicit accounts, as long the account of the person installing has access to create databases within SQL Server
- Username prefix: palCentre relies on 3 SQL logins. So that you can conform to your own naming standards, palCentre asks for a prefix to use for these logins. The default is ahsri_eppoc – please change this to ahsri_pcoc. ePPOC is a sister centre of PCOC and this name should be reserved if ePPOC databases are ever installed on your server. palCentre. This will create logins ahsri_pcocpalCentre_dbo, ahsri_pcoc palCentre_user and ahsri_pcoc palCentre_reader. You can use any prefix you like which would result in a valid SQL login.
- DBO Owner password, User password and Reader password: you may use the same password for all 3 logins or different passwords. For higher security we recommend using a different password for each SQL login. For each login, there is a password and confirm password textbox. Note that these passwords are encrypted before being saved in the configuration file, ensuring your password security. Make a note of these passwords because you will need to use them again in the ‘Client Configuration Wizard’. Ordinary users will never need to use or know these passwords.
- Database path: this is the path on the SQL Server (not on the client machine) where the database .MDF and .LDF files will be created. The default is C:\ePPOC\ but you will probably have a specific folder where SQL Database files are kept. This path must already exist to correctly work.
...