Asle Frantzen

Custom (OLEDB Ent.) database objects not included in AFDB export?

Discussion created by Asle Frantzen Champion on Oct 21, 2015
Latest reply on Nov 12, 2015 by pthivierge

I've always recommended people use the following settings when exporting everything from an AF database in PI System Explorer:




But I recently found a flaw in this theory when one of my customers were looking for some OLEDB Ent. custom views they had created in a database, prior to moving the database to another server. Turned out these were not included in the export. I can understand that these were created as part of a data access tool (SQL Cmdr. / OLEDB Ent) but I still thought they were linked closely enough to be included.


Any input on this?


With that in mind, are there any other fool proof ways of exporting "everything" related to a single AF database in one operation, when moving from one environment (Test) into another (QA/Production)?