SAS Office Analytics, SAS Add-In for Microsoft Office, and other integrations

which Lib we Need To Store Taget tables in DI Studio

Reply
N/A
Posts: 0

which Lib we Need To Store Taget tables in DI Studio

Hi All,

In DI STUDIO Generally which library we are store our taget datasets.

Appreciate Great Help

Regards,
Govind
Esteemed Advisor
Posts: 5,080

Re: which Lib we Need To Store Taget tables in DI Studio

Assuming that target was misspelled taget.
Well that depends on your needs.You can define you own libraries through New Library Wizard. I suggest that you engage as DW architect who can suggest what types of libraries you'll need, and what engine to use.

Regards,
Linus

PS This wasn't really an AMO question. On the other hand there is no Data Integration forum, which would be great to have!
Data never sleeps
N/A
Posts: 0

Re: which Lib we Need To Store Taget tables in DI Studio

Hi All,
Assume that my target is having Correct data .There is No mispelled data.Is there any specific library for that correct data.Can you Please elaborate on this.If my target data is mispelled data we will store that type of data in user defined libraries.I think so.

Appreciate your Great Help in Advance

Regards,
Govind
SAS Super FREQ
Posts: 8,643

Re: which Lib we Need To Store Taget tables in DI Studio

Hi:
Generally speaking, SOURCE tables are the INPUT to a DI Studio process or transformation. A lot of times, SOURCE tables might be legacy files, such as SAS files, mainframe files, database tables or other types of data sources.

TARGET (not "taget") tables are the OUTPUT from a DI Studio process or transformation. You usually want/need the TARGET tables to be defined in the metadata so other users (people using EG, WRS and the SAS Add-in for Microsoft Office) can access the target tables. Or, it's possible that the DI Studio process would build an OLAP cube or load into a datamart or data warehouse.

It is up to you to design the structure of the libraries for your TARGET (or OUTPUT) tables. Some installations design libraries by department (Accounting, Sales, Purchasing, etc) -- other installations design libraries the fit other functions -- Analysis libraries, Reporting libraries. Really, that planning process needs to be part of the job that your Platform Administrator or DATA Administrator would do.

When you say "user defined libraries", it implies to me that you mean your users will issue LIBNAME statements. Generally, once you have a target table in a library that's defined to the Metadata, you need to decide what kind of security is going to be used for that library. Depending on what you set up, the users never issue LIBNAMES to the data -- they access the data through EG or WRS or AMO -- which shows the user only the tables that they are able to read/work with.

If, by user defined libraries, you mean that the Data Administrator has to set up the libraries -- then, that is correct. You would use the New Library Wizard to set up a user defined library to hold your target tables.

Reading the Platform Administration documentation, the DI Studio user's guide or taking some of the BI Platform Data Integration classes might help you with these tasks.

cynthia
Post a Question
Discussion Stats
  • 3 replies
  • 171 views
  • 0 likes
  • 3 in conversation