Configure the SE-Viewer Database for SQL Server

Using the Configuration Utility

All events are written to a Microsoft SQL Server or Microsoft SQL Express database. For use in a production environment, AVIcode recommends configuring the system to use a SQL Server database.

The Configuration Utility is a tool that allows you to automatically create and/or configure the following components:

In some cases the Configuration Utility cannot complete all of the necessary configuration steps automatically due to a lack of MS SQL server administrative rights. Additionally, if you use the Windows Integrated security model, you will have to manually configure the IIS Application pool and Intercept Reporting Windows Service to be run under a custom Domain account.

 Later in this chapter you will find step-by-step instructions that allow you to complete the configuration process. Most of steps apply to any installation, but certain steps are only needed for certain configuration scenarios. You will need to be able to answer these questions:

Configuring the SE-Viewer Database for MS SQL

The SE-Viewer Configuration Utility allows you to manage the SE-Viewer database:

The database requires a minimum 10 GB of free space

New Installations

Custom Security

The first step to prepare your environment is to identify the server on which you will install the SE-Viewer database.  Once this is determined, create and configure the database. 

If the test succeeds, then your database has already been configured and you do not need to continue with these instructions.

Modifications can be made to the script and the script saved via Save As

Windows Security

The first step to prepare your environment is to identify the server on which you will install the SE-Viewer database.  Once this is determined, create and configure the database. 

This account should have:

NT security mode (Windows NT Authentication only) vs. Mixed mode (Windows NT Authentication and SQL Server Authentication).

In Windows NT mode (the 'Use Windows NT Integrated security' option), users that NT validates can also connect to SQL Server databases based on their user account names and group membership which already exist in Windows NT 4.0, or Windows XP.

In mixed mode ('the Use a specific user name and password' option), NT users connect to SQL Server databases under Windows NT mode and users that NT doesn't validate use valid SQL Server (SQL Server Authentication) logins. Users that connect to SQL Server databases under Windows NT can make use of trusted connection mechanism for both authentication modes. Whenever the SQL Server database is connected, the access control mechanisms that in this case are lower level-ones (access to databases or database objects only) function identically in both authentication modes.

If the test succeeds, then your database has already been configured and you do not need to continue with these instructions.

Modifications can be made to the script and the script saved via Save As

Upgrading

If the test succeeds, then your database has already been configured and you do not need to continue with these instructions

Last update: Thursday, December 09, 2010 02:07:47 PM