DCO ETL Export Database

[DCIM_Support]

Can you advise are there any logic to identify delta data in the DCO ETL Export Database?

We are talking to our data management team to extract the data from the ETL export database and they need to know this to understand when to extract the data.

Also, in this page http://sxwhelpcenter.ecostruxureit.com/display/public/DCIMDEVELOPER/ETL+Export+Database the Data Information State link at the top of the page is not working, it goes back to the same page.  Please help to fix it, thanks.

(CID:129404832)

[DCIM_Support]

YJ,

Correct link is below,we are working to fix the link.

Keeping Track of Information State

(CID:129404991)

[DCIM_Support]

To add what I got from the folks:
In addition, the information in there, the user can, at their own comfort, use the state-information given in the export database, for bookkeeping on the integration made based on the export database. It is not mandatory to use on the export database, and the running DCO instance will not be affected by the information stated in the export database.

(CID:129404993)

[DCIM_Support]

The state_flag and state_last_updated columns will be your best bet on tracking when a device was last updated and when to perform your extraction. Your first sync should show that everything is New with a recent time stamp. After that as changes happen the state_flag will change to "changed" and most of the time will stay that way and the state_last_updated will be time stamped in EPOCH time when that change was done. What I would do is also cache the timestamps in a separate DB or file. Then you can perform your delta on the next run and extract items with a time stamp greater than what you have cached.

(CID:131959127)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.