Support FAQ > Installation & Deployment > Can I store my Visual KPI configuration data in SQL Server on a different machine?
Yes! All components of Visual KPI may be run on the machine of your choice. While it is very common for trial or pilot systems to have the SQL Server database running on the same server machine as the Visual KPI web server, production deployment architectures are frequertly driven by corporate IT requirements and data security issues.
A typical production environment segregates responsibilities for web servers and database servers between two different IT subspecialties. This usually means the SQL DBA will be a different person than the webmaster maintaining the web server. For illustration, let's assume a corporate environment where "MyDomain" is the name of the company's Active Directory domain, with a Fully Qualified Domain Name of www.MyDomain.com. Let's further assume that the NetBEUI name of the web server machine is "VKPISVR" with an FQDN of VKPISVR.MyDomain.com. Let's also asume the NetBEUI name of the SQL Server machine is "SQLSVR" and the FQDN is SQLSVR.MyDomain.com.
In this scenario it is essential that the person running the Visual KPI Server manager (VKPISM) has sufficient permissions to create a database on the remote SQL machine. VKPISM runs under the "logged-in user" on the web server, so this user Domain user must have at least Security Admin rights on the SQLO Server at the instance level. You can test this requirement by simply running the SQL Server management Studio to create a test DB then delete this test DB. If you can create/delete a test DB then all is well.
After passing the test above, this logged-in user is ready to create an instance of Visual KPI. Select and then right-click on either the root of the IIS instance or on the base-level Virtual Directory you wish to created the Visual KPI instance under. Once the wizard has completed, there is only one manual step required: granting read/write access to the newly-created database in SQL Server for the services running on the web site machine. Visual KPI uses very low privelefge accuonts which use the NT AUTHORITY\NETWORK SERVICE identity for data access across the LAN or WAN. When accessing a "local" SQL database, this account appears to SQL Server as the literal account name, or "NT AUTHORITY\NETWORK SERVUCE." However, when accessing a "remote" SQL database, this account appears to the SQL Server as "MyDomain\VKPISVR$" instead of "NT AUTHORITY\NETWORK SERVICE." So the last step after creating a new Visual KPI instance is to tell SQL Server that the "MyDomain\VKPISVR$" account has read/write access to the just-created database. So if you created a new Visual KPI instance named "MyInstance" then you are required to open the SQL Management Studio application, create a new Login at the SQL Instance level called "MyDomain\VKPISVR$" and grant VisualKPI_role and SecurityAdmin rights to the database named "MyInstance." Voila! You now have a remote SQL database for all Visual KPI configuration data.
Last updated on May 20, 2012 by Michael Saucier