|
Installing the Database |
  
|
|
Installing the Database |
|
OfficeStatus Server is backed by a managed SQL Server database, the creation and configuration of which is handled automatically by the product installer.
The OfficeStatus Server installer will prompt you for a specific SQL Server instance which will host the OfficeStatus database. You can either enter a known SQL Server address into the specified field, or click the drop-down arrow to build a list of available SQL Servers on the local network (including the local host computer).
Note that the SQL Server discovery mechanism can only find a specific SQL Server instance if its SQL Browser service is enabled.
In order to create and configure the OfficeStatus database, the installer must log in to your SQL Server database as a System Administrator (e.g. member of the "sysadmin" role). Two different authentication methods are supported:
| • | Windows Integrated - The Windows account under which you're currently logged in must be a SQL Server database administrator. |
| • | SQL Server - Uses a built-in SQL Server account which is configured as a database administrator. |
The OfficeStatus Server installer will use this information in the final stages of installation to do the following:
| • | Create a database named "OfficeStatus" |
| • | Create a SQL Server login bound to the Windows user account specified in an earlier installation step |
| • | Assign OfficeStatus database ownership to the SQL Server login |
Tip 1: When installing OfficeStatus Server on the same machine that hosts SQL Server Express 2005, the default SQL Server instance address will be "COMPUTER-NAME\SQLExpress".
Tip 2: If your current, logged-in user account is not a SQL Server system administrator, you can always use the "sa" account for this step (as long as your SQL Server instance has mixed mode authentication enabled).