This screen is where you specify how BlueView software will connect to the SQL Server database. It is shown when you first install the software and can be found under Tools, in Database Configuration.
This is a wizard that will help you set up your connection to SQL Server. It has information relating to installing SQL Server, different configurations for BlueView servers and clients, SQL Server installed on a remote machine, etc. This is the best place to start when configuring BlueView for the first time.
BlueView Server or Client
The BlueView Server is the primary installation of BlueView on the network. There can only be one BlueView Server on the network, because this is the software that handles communication between the door controllers and the software. Despite the term "server," a BlueView server can run on any type of computer (laptop, workstation, server) that meets the minimum hardware requirements.
A BlueView Client allows the BlueView system to be managed from other computers on the same network. BlueView Clients are identical to BlueView Servers in terms of management capabilities, except that BlueView Clients do not have the ability to start or stop Bluelink Network Services (which runs ONLY on the BlueView Server). BlueView Client installations are subject to BlueView software licensing. Clients cannot be configured until the BlueView server has been installed and configured. For more information on setting up a client, see our Guide for Client Setup.
Server Name or IP Address: This is the server name or IP address of the machine hosting the BlueWave SQL Server database.
• If SQL Server is running on the same machine as this installation of BlueView, the server name can be set to "." which means local machine.
• If SQL Server is on a different machine than BlueView, this field should contain either the name or the IP address of the computer where SQL Server is running. Note that when SQL Server is on a different machine than BlueView, there are additional steps needed to configure SQL Server so that it can be accessed remotely.
Instance Name: This is the name of the SQL Server Instance where the BlueWave database is/will be installed. This would have been set when SQL Server was installed. The default instance name is usually MSSQLSERVER but is sometimes SQLEXPRESS, left blank or set to a custom name by the person who installed SQL Server. Use the Browse button or go through Guide Me to search for available SQL Server instances on your machine and/or network.
Connection Timeout (in seconds): This specifies how long BlueView will wait for a response SQL Server when trying to connect. It can be adjusted at your discretion, based on your computer and network latencies.
This section specifies the credentials that BlueView software will use to connect to the database. There are two options:
This option means that BlueView will try to access SQL Server using the credentials of the Windows account that is currently logged into the machine. By default, ONLY the Windows account that installed SQL Server will have access using this method. If you are using SQL Server 2012 or higher, this option is available ONLY for expert SQL Server users. This is because Bluelink Network Services will not have access to the database without the Windows service being given explicit access to the BlueWave SQL database. We recommend using SQL Server Authentication instead. If additional Windows accounts need to be able to use BlueView, these accounts will also need to be given access to the SQL Server database. If you do not know how to do this, we recommend using SQL Server Authentication
SQL Server Authentication
This means that BlueView will use the specified user name and password to connect to SQL Server, regardless of which Windows user is logged into the machine. If Mixed Mode Authentication was specified during SQL Server installation, the sa login created at that time can be used here. If not, or if you prefer not to use the sa login, use the Create SQL Login button to create a SQL Server login for BlueView to use. (Note: Check the Integrated Security box before clicking on the Create SQL Login button, to ensure you have proper database permissions to create the login.) BlueWave recommends using SQL Server Authentication in most cases, because it funnels access to the database through a single SQL Server account that is not tied to a Windows login. It also simplifies setup for BlueView clients, for SQL Server running on a remote machine, and for SQL Server versions 2012 and later.
Use the Test Connection button to test the connection information.
Create SQL Login
This button can be used to create a SQL Login that can be used for BlueView to access the database. This will ONLY work if a valid connection to the database has already been confirmed using *Test Connection*. It also relies on Mixed Mode Authentication being turned on in SQL Server. If Mixed Mode Authentication is not enabled in SQL Server, a message on the Create SQL User screen will direct you to the appropriate documentation to resolve the problem.
This button will restore the Database Location information to the default settings that ship with BlueView.
Be sure to hit Apply before leaving this screen to save the new settings. BlueView will re-test the connection before saving and will only allow valid settings to be saved.
BlueView needs to be run as an Administrator (Windows setting), especially when setting up the initial database. This should happen automatically, but in case it doesn't, use Windows Explorer to navigate BlueView's installation directory (typically C:\Program Files\BlueView). Right-click on BlueView.exe and select Properties. Click on the Compatibility tab. Under Privilege Level, check "Run as Administrator." Then OK to close. Now, try running BlueView again.
If changes you make in the Database Configuration screen do not "stick" after Apply and Close, the problem may be that the file where these settings are stored may be marked as Read-Only by Windows. Using Windows Explorer, go to BlueView's installation directory (typically C:\Program Files\BlueView). Right-click on the file DAL.config folder and select Properties. Next to Attributes near the bottom, click on the check box next to Read Only to clear the box. Then click OK. It will then tell you you need to provide administrator permission to change these attributes. Click Continue.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article