Blog | Language | Customer Login | +1-925-218-6983
What is Visual KPI? | FREE 30-Day Trial | +1-925-218-6983 Subscribe via RSS Feed


Real-Time Dashboards & Alerts

Smartphones | Tablets | Web Browsers | PC & Mac | More

Visual KPI reads multiple data sources in real-time (big data, historians, databases, manual data, web services and more) and adds context with KPIs, groups/hierarchy, alerts, and geolocation. It gets your critical data in the hands of more users without extensive training and it can be deployed in days, not months. Want to see how we do it?

Mobile Operations Monitoring - Tour
Real-time KPIs on Browser, iPhone, iPad, Android, Windows Phone, tablet
Check out a 2-minute video and see the latest…
What is it?

Visual KPI is mobile dashboard software for any device. It reads existing data sources and delivers KPIs, scorecards, analytics and alerts in real-time.

Who uses it?

Decision makers. Operations. Remote workers. Data Junkies. Anyone who values knowing what's happening right now, regardless of their device.

Why use it?

Mobility is no longer optional. Visual KPI presents problems and opportunities before it's too late. Oh, and there's no six-month project that "might" pay off.

American Electric Power BP Wind Energy con edison operations Exelon Energy Genentech FMI - Freeport McMoRan Corning Pemex Tesoro


OSIsoft PI World Sponsor 

Support FAQ > Installation & Deployment > How do I move Visual KPI to a new server?

Search the FAQ for entries containing:

Migrating the Visual KPI Server from one machine to another is a very straightforward process, but please note...

The steps are easy, but the order is critical.

Another thing to point out:  The prerequisites are fundamental and you would not believe how many people ignore the preparation for such a move, imagining that it is just like copying a notepad file from one file server to another.  It is not.  Even though Visual KPI is a modern and quick-to-deploy mobile monitoring and BI tool, it is still an enterprise application and should be treated as such during a migration such as this.

For this FAQ we will assume the worst case, which is SQL Server and Visual KPI are on different physical machines. We will also assume that the database and Visual KPI Instance name are identical and are the default value of “VisualKPI” as delivered form the factory (us). The optional steps will be shown for the trivial case where SQL Server and Visual KPI are on the same machine.


  1. OS version is not important, you can move from Windows Server 2008 R2, 2012, 2016 and back.
  2. Both servers have all Visual KPI prerequisites installed and tested (.NET 4.6 Complete).
  3. Both servers are patched and fully up to date for the OS version
  4. IIS is configured to allow .NET 4.0 to run on the target server
  5. The SQL Server software is of the same vintage (i.e. moving from 2005 to 2005, or from 2008 to 2008 or from 2008R2 to 2008R2, 2012, 2014, 2016 etc.)
    1. Note: This is a SQL requirement, not a Visual KPI requirement
    2. To migrate SQL versions, a more involved process is required rather than simply creating a BAK file for restoration.  Contact us if you need help with this.
  6. SQL Server is patched the same on both machines, or the target machine is more up-to-date with patches than the original

Steps to Migrate:

Here are the steps for migrating Visual KPI to a new server.  Note: make sure you have the necessary permissions before you begin. This should take no more than 10 minutes:

  1. Use SQL Server Backup to create a .BAK file on the Source SQL Server machine, then copy it to the Target SQL Server machine. E.g. VKPI.BAK, containing the database “VisualKPI”
  2. Restore the Database using SQL Restore function, now you have a database on the Target SQL box called VisualKPI.
  3. Run the Visual KPI Server manager on the Visual KPI Target machine and create a new web site instance named “VisualKPI”
    1. When the database creation step arrives, simply choose a DB name of “VisualKPI-deleteme”
    2. Keep all other selections named “VisualKPI”
    3. Let the wizard run to completion
  4. Create all interfaces (to data sources – OSIsoft PI System, Oracle, etc.) with the same names as used on the original web server.
    1. For ODBC, OLEDB and OLAP interfaces, copy the *.SQL files (using Windows File Explorer) which hold the Current, History and Trend data queries to their corresponding file folders in the Target Visual KPI machine, overwriting the default files created when the interfaces where installed on the Target VKPI machine.
  5. Modify connection strings in the 3 applications, change “DB=VisualKPI-delete” me to “DB=VisualKPI” in
    1. Cache Server
    2. Alert Server
    3. Website
  6. Delete the dummy database in the Target SQL Server machine named “VisualKPI-deleteme”
  7. You are done

If you have questions or issues with a migration, please contact us and one of our engineers will happily walk you through the process.

Last updated on June 5, 2017 by Transpara

Free 30-Day Trial

Transpara LLC
4715 W. Culpepper Drive‎
Phoenix, AZ 85087

© 2005-2018 Transpara LLC. All rights reserved.
Privacy Policy | Terms of Use | Copyrights

© 2005-2018 Transpara LLC | Privacy Policy | Terms of Use | | +1-925-218-6983