Creating an internal data store - Data360_DQ+ - Latest

Data360 DQ+ Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
Latest
Language
English
Product name
Data360 DQ+
Title
Data360 DQ+ Help
Copyright
2024
First publish date
2016
ft:lastEdition
2024-07-09
ft:lastPublication
2024-07-09T15:09:58.774265
Note: To create an internal data store, you must have Create Data Store and Write permissions to a pipeline.

An internal data store can hold data pushed from another (external) application, such as Assure DQ or ER DQ, or it can hold data from other data stores that are already set up within Data360 DQ+. These types of data stores are typically outputs from other data stages, such as an analysis that transforms a set of data stores to create a new one. Additionally, internal data stores can be used to hold the detail records for case stores within a database.

To complete the following steps, you may require assistance from your Data360 DQ+ administrator.

  1. Connect to Data360 DQ+ - To bring data into Data360 DQ+ from another application, your administrator must create an "Application User" profile. This profile allows the other product to communicate with Data360 DQ+.
  2. Push definitions to create data stores - Once a connection is established, you can push the definitions from your external application to Data360 DQ+.

    If pushing from Assure DQ or ER DQ, this will automatically create data stores in Data360 DQ+ for you. These data stores will be located in an incoming pipeline, containing paths based on the controls that have been configured in Assure or ER.

    Note: If you intend to associate an internal database data store from Assure DQ to a case store in Data360 DQ+, it will be labeled as a "Case Output" data store within the incoming pipeline in Data360 DQ+.
  3. Select and move data stores.

    To use your newly created data stores, move them out of the incoming pipeline and into another pipeline and path. Moving the data stores lets the external application know that it should push data to those data stores the next time an execution occurs.

  4. Execute the entity in the external application to push data to the data store.

    Once you have moved a data store from the incoming pipeline to another pipeline, this will signal that data should be pushed to this data store the next time the associated entity is executed within an external application. Only data stores that have been moved out of the incoming pipeline will have data pushed to them. All data stores residing in the incoming pipeline are effectively empty definitions until they are moved.

    Note: It is important that you move the data store out of the incoming pipeline and do not just copy it. To move a data stage, you need Write permission to the destination pipeline and path.
  5. Configure the data store's properties and use it to create other data stages. See Configuring data stores.

    If you are planning to create an analysis, you can create an internal data store to serve as the analysis' output ahead of time. Otherwise, you can simply create this type of internal data store while you are designing the analysis.