Part 3 of the series will be creating the Events database. Horizon View uses the events database as a repository to store logging information such as user connections. Microsoft SQL Server or Oracle database servers are supported. For my environment I will be using SQL Server 2014. This step can be skipped if you do not want to log these events.
vBoring Blog Series:
Creating Events Database in SQL 2014:
First we need to create the database. Login to your SQL server, launch the SQL Server Management Studio, right clickDatabase then click New Database:
Give the database a name, I used ViewEvents so it can easily be identified:
On the Options page change the Recovery model to Simple then click Ok:
Let’s create the account View will use to connect. Drill down to Security, right click Logins then click New Login:
On the General page enter a Login name, select SQL Server authentication and enter a password. Change the drop down menu of Default Database to the Database that we created above.
Note: View only SQL authentication is supported.
On User Mapping select the database we created above, give it db_owner permissions then click Ok:
Add Events Database in Horizon View 7:
Switch back over to the View Administrator Console, drill down to View Configuration -> Event Configuration -> then click Edit:
Enter the FQDN/IP Address of your SQL Server, Database Name, and the Login created from above.
You would enter something in the Table Prefix if you were going to have multiple instances of View talking to the same database.
Click Ok:
The Event Database section should now be populated if the details you entered were correct. You can edit the Events Settings to change the time period settings, but I left them default.
Browse to Monitoring -> Events. Here you will find a summary of recently added events.
On the View Dashboard you will now see the Event Database section populated.
Proceed to the next step:
