2 Replies Latest reply on Jun 13, 2017 6:56 PM by jesusm

    When is it necessary (or convenient) to create a new AF database or use an existing one


      In the video "Create PI Points in PI System Explorer using AF Templates", a new database is created for managing the so called "sampled process - pumps". My question is when is it necessary (or convenient) to create a new database or use an existing one. In my case, my PI AF Server is going to collect data from different data sources (several independent laboratory plants). My doubt is if it is better so use the same database (Lab plants, for example) for all data coming from the different plants or just use a different database (lab1, lab2, lab3, ...) for each plant. What are the consequences of my decision?


      Thanks in advance,

      Jesús M. Zamarreño

        • Re: When is it necessary (or convenient) to create a new AF database or use an existing one

          Hi Jesús,

          Great question! Unfortunately there isn't a 100% straightforward answer as it'll depend on several factors and what you/your end users value. This is most likely not an exhaustive list, but here are a few things that I came up with that you should consider when making the decision to use the same or a new database:

          1. ***Most important consideration*** Do your labs have similar assets that you're modeling? Library objects, most importantly templates, only exist within a single database; they are not server wide. Thus, if you will be using the same templates to model assets from your different labs, you will most likely want to organize them into a single database. Technically you can export your template and import it into a new database if you'd like to reuse it, but then any future modifications to that template will have to be done twice (or more if you use separate databases for lab3, lab4, etc.) which adds to the amount of administration you'd be required to do.
          2. Do you want to restrict users to only the lab that they are involved with? You can configure security at the database level if using separate databases for your labs, or configure security at the object level (i.e. if all of your labs are in one database and you'd like to restrict users to only a particular branch. Thus you could control this either way, but your preference may influence how\where you want to model your labs.
          3. How big is each lab? If none of the assets in your labs rely on the same templates and each lab is rather extensive, you may consider placing them in separate databases simply for easy of navigation, searching, etc. However, this is more of a user preference than essential consideration...until you element count is as high as some of those mentioned in the Hardware and PI System Sizing Recommendations Sheet (albeit if any of your labs exceed these sizes, you'd need to separate your labs into different servers entirely, not just AF databases).

          Overall, there isn't a right or wrong answer to the question of when to use a new AF database or the same, however I'd say the re-usability of library objects (templates) is probably the most important factor.

          1 of 1 people found this helpful