This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We have our data set up to run once a week to refresh our meta data. Sometimes our analysts have created new database entities that they would like to document. Is there any way that this can be updated in just that data source, rather than running the whole update (which takes 6-7 hours)?
I think that what @JoTP is trying to achieve is a "additive load", while @joshuaburkhow proposes "partial load". The issue with partial load is that it deletes everything from Connect that has been created before and is not part of this load.
Example: @JoTP loads these 3 databases all the time - aaa,bbb,ccc. That takes several hours. Then, somebody created database ddd and JoTP wants to load only this ddd database without refreshing aaa,bbb,ccc. If he sets ddd as the objects to load, then all the aaa,bbb,ccc databases will be removed and only ddd will be visible in Connect. That is not his goal.
Unfortunately Connect does not currently support this use case.
Some clients are using a workaround that for each subset of objects they create a separate data source. So in JoTP's case, the ddd database would look like that it's on a different machine than the others. Which is not acceptable, I assume.