Ajilius enables browsing of source system metadata, to identify and load data into the warehouse. Here is a typical display:
A click on a table, on the left side, shows the columns for that table on the right side.
Until now, each update of this screen represented a round trip to the database. That was fine for a data source located close by the Ajilius server, but users in hybrid environments reported slow screen updates when pulling cloud metadata to on-premise Ajilius. This was particularly apparent with large Oracle systems, which add thousands of system table entries to a metadata set.
We’ve now added a feature to cache metadata within Ajilius. This means the delay of updating metadata happens only once, and subsequent interactions are as fast as an on-premise solution.
The context menu for a data source now contains an option to Refresh Metadata:
When you select this option, you will be prompted with a screen warning that a metadata update might be slow. In this case, “slow” means a few seconds.
On running this refresh, an internal metadata cache is added to your data warehouse metadata repository, and subsequent calls to browse metadata or load metadata into the warehouse will be drawn from this cache.
You may refresh the cache at any time.
An added bonus is that once your data source metadata is cached, you no longer need to be connected to the source whilst working with source metadata. That’s a great feature for companies with high risk data, and for people who like to take their work home with them 🙂
Ajilius. More flexible metadata.