1 of 1 people found this helpful
PI Coresight 2016 R2 and PI Vision 2017 come with a display utility that you can use the migrate displays. Here is the section in the manual about this utility: PI Vision
2 of 2 people found this helpful
The tricky thing with the display utility is that you need to have access to both the source and target SQL servers at the same time. And that is often not possible.
So what i do is: 1) copy the PI Vision database from the source to the target SQLserver and then 2) use the display utility to copy these displays from the source to the target display.
If you like this different, like me, upvote here: Allow the PI Vision Display Utility to export the configuration to a file and import from a file – Customer Feedback for…
Once this has been done (copied the entire database from one server to another). What if I want to copy one or two new displays from the source to the destination server, but I do not want to override any other displays on the destination server created on the first move since these might have been improved/altered.
Do you have any suggestions on how to do that. I guess if I do the database copy-display utility approach again, it will override my destinations displays..
The display utility takes care of that. Displays are identified by ID not by name, so duplicate names is not an issue.
I have not looked at the database schema in a while, but you could hack the DisplayID to ensure you don't get a duplicate ID if you perform a DB copy