Hello everyone!
So I have an old job in SAS Data Integration Studio which is about 200 SQL-joins which are passed trough to Teradata Server. I walked through that job, made some changes, added some new transformations and then noticed that some of the changes did not apply.
For example, in a couple of jobs in the middle of the flow I've changed mappings. When I save and then reopen the job changes disappear. Also I provided Teradata formats and indexes for all tables and for some of them they disappeared.
I tried creating a copy of the job and making changes there but it didn't help: changes still not saving.
What can be the cause of this situation and what can I do about it? (probably I should create new job from scratch but I don't have time for that).
Thanks for your replies
Since no one has answered any of this I will move the question to the data management area where DI things are typically discussed and may get an answer there.
Something to consider:
Are you attempting to save the new settings to an older file version (file name extension) of the DI project or to a new project? Some of these "project" files might be incorporating changes that the older file format just does not support and may need to save to a new version.
Hello, ballardw!
Thank for moving the question: I didn't know where to post the question about SAS DIS.
So, I've figured how to fix most of the problems: the mappings don't save because Teradata allows you to use already defined field in defining next fields. For example, I have a column OPER_AMT (operation amount) which is calculated from some source fields and OPER_TYPE which is defined as CASE WHEN OPER_AMT > 0 THEN 'DEBET' WHEN OPER_AMT < 0 THEN 'CREDIT' ELSE 'UNKNOWN' END. SAS DIS for some reasons can't handle this situation properly so I have to create a pre transform where only OPER_AMT is created and then the second transform where OPER_TYPE is created.
Teradata formats (which you specify in Options/Advanced tab in the properties window for the temporary output table) don't save because in "Physical storage" tab of the properties you should switch parameter "Location" from "Job's default library for temporary tables" to "Redirect to registered library" and select the library, then changes will save and apply.
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.
Find more tutorials on the SAS Users YouTube channel.