You create an event database by adding it to an existing database server. You can then use enterprise reporting software to analyze the events in the database.
About this task
Deploy the database server for the event database on a dedicated server, so that event logging activity does not affect provisioning and other activities that are critical for View deployments.
You do not need to create an ODBC data source for this database.
Verify that you have a supported Microsoft SQL Server or Oracle database server on a system that a View Connection Server instance has access to. For a list of supported database versions, see Database Requirements for View Composer and the Events Database.
Verify that you have the required database privileges to create a database and user on the database server.
If you are not familiar with the procedure to create databases on Microsoft SQL Server database servers, review the steps in Add a View Composer Database to SQL Server.
If you are not familiar with the procedure to create databases on Oracle database servers, review the steps in Add a View Composer Database to Oracle 12c or 11g.
- Add a new database to the server and give it a descriptive name such as ViewEvents.
For an Oracle 12c or 11g database, also provide an Oracle System Identifier (SID), which you will use when you configure the event database in View Administrator.
- Add a user for this database that has permission to create tables, views, and, in the case of Oracle, triggers and sequences, as well as permission to read from and write to these objects.
For a Microsoft SQL Server database, do not use the Integrated Windows Authentication security model method of authentication. Be sure to use the SQL Server Authentication method of authentication.
The database is created, but the schema is not installed until you configure the database in View Administrator.
What to do next
Follow the instructions in Configure the Event Database.