Desktop productivity for business analysts and programmers

How to make a data dictionary

Reply
N/A
Posts: 0

How to make a data dictionary

Not sure if I'm in the right spot....my CIO is very interested in having data dictionaries made that users can view and use. However, being fairly new to SAS and data dictionary concepts, I don't know where to start. If anyone has hints/advice/help they are willing to share, or can point me to where I can get more information, I would be a happy camper.

Also, if this isn't the right place to ask questions like this, please let me know...I don't want to step on toes, so to speak. Thanks!
SAS Super FREQ
Posts: 8,720

Re: How to make a data dictionary

Hi, in my experience, data dictionaries were what I built when I was working with ADABAS (Software AG) or DB2 (IBM) -- data base systems in which the data dictionary was maintained and defined for the database system by someone called a DBA -- or data base administrator.

If we had a bunch of ad-hoc reports with the data in VSAM files and SAS data sets and sequential files, then I sometimes I had to map my columns or variables in those files to their corresponding matches in the data dictionary or, sometimes (most likely) there was no mapping -- which is why I was using them for ad-hoc access. If I worked in a shop where I had DB2, then there was one data dictionary for DB2. If I also had Oracle, then we might have a separate data dictionary for Oracle.

Every once in a while, somebody would rumble about have a corporate wide data dictionary and identifying all the data sources and we used to do HIPO charts or CASE charts to map the disparate data sources into one monster data dictionary -- but over time, as things changed, the last thing that changed was the documentation for the various systems.

I believe that in the strictest sense of the usage, a data dictionary is tied to a specific data base and each data base has its own way of using the data dictionary.

In some senses, the metadata that you are defining for your tables in the BI Platform represents the kind of "metadata" data dictionary that your boss wants to have.The big advantage of using Data Integration Studio or otherwise defining your tables and files in the metadata is that you can have disparate data sources, such as DB2 and Oracle and flat files all being used in your BI system and you essentially define that kind of metadata (about whether the columns are character or numeric, what format they should have, what transformations those columns need to undergo all in one place) for every data source you have.

In addition, the Metadata server contains information about user access and restrictions for each table, for columns within tables and even for rows within tables. When you define information maps, you are able to provide your users with a "friendlier" view of the data. Let's imagine that you have a list of orders that have an order number. Each item is provided by a vendor. It's inefficient to keep the vendor name and address in the order file. But, there may be somebody who is dealing with returned items, where they need to access both the item number of the returned item AND the vendor name and vendor address who provided the item. Should that person need to know about doing an SQL join of the returned items with the order file and the vendor file in order to get data in the right structure they want??? Probably not. You can build an information map for the person handling returns so the join is transparent to them -- they could open the information map in Excel or in Word and then the fact that a join is taking place is defined in the information map.

What I'm trying to say is that I think the SAS Metadata server is like having a super-charged data dictionary. For information on how to document your metadata or print out information from the metadata repository (which is what I think you're asking for), you should consult the Platform Administration documentation. Since everything in the BI Platform is stored in the metadata repository, that should be the first place you look. SAS Data Integration Studio does have a way to do impact analysis, again, the DI Studio documentation can be useful to you.

cynthia
N/A
Posts: 0

Re: How to make a data dictionary

Thanks, Cynthia,

That's "kind whatta" I was thinking, too..... however, I'm trying to keep my CIO happy, which is why I asked.
N/A
Posts: 0

Re: How to make a data dictionary

Are you trying to create a data dictionary for SAS datasets in Base SAS ?
or are you using BI, metadata server, etc.?

If you are you trying to create a data dictionary for SAS datasets in Base SAS, I will follow-up with a fairly simple automated method.

-Matthew
N/A
Posts: 0

Re: How to make a data dictionary

I can use base SAS! Looking forward to seeing your method.....thanks!
New Contributor
Posts: 2

Re: How to make a data dictionary

As you familiar with BASE SAS then you will know of the dictionary tables accessible from SASHELP or the dictionary libraries. This SUGI paper details some of the nice additions to these in SAS 9: www2.sas.com/proceedings/sugi31/045-31.pdf

In terms of metadata typing in 'Metabrowse' into the command line window of your BASE SAS session will give you an idea of what is available. There are many objects. 'Metafind' is also a good one, should you know the metadata ID. For more details on getting into the metadata you should have start to have a look at: http://support.sas.com/onlinedoc/913/getDoc/en/omags.hlp/a003160218.htm

There is alot to read on the area. When changing metadata it would be recommended to always use the GUI tools available to you.
Ask a Question
Discussion stats
  • 5 replies
  • 432 views
  • 0 likes
  • 3 in conversation