I've got what's likely a basic question.   I've inherited a warehouse that has multiple records on a fact table that represent the same individual. For example, they were originally loaded with an Id number of 12345 and assigned a key that we shall call 333. A year or two later the same individual was loaded again but a different Id number was given (12354) so when loaded they were thought to be a new individual thus assigned a new foreign key (444).   Now a few months ago we were sent a new dataset telling us that ID 12345 and 12354 should be the same, so the two Ids were merged and now the fact table has the following two rows for this individual:   Key          ID 333          12354 444          12354   That part was easy enough. Trick is the keys are used on various tables. Now, some tables will link to ID 12354 via key 333 and other tables from 444. Obviously, this isn't good, especially since several Ids were incorrectly loaded originally..   Is there a better answer than deciding on one key to use, combing through every fact table we have, checking to see what key is used, then assigning it the correct key of the so that all tables use the same key for an ID, then close out either 333 or 444?   Does that make any sense? Seems to be the way to go, but am curious if anyone has had to deal with anything similar.   Thanks, all! ... View more

I seem to be having difficulty getting this SCD Type 2 Transformation to do what I think it should. I have two questions.   1) We use Beginning Date and End Date in our target fact table for purposes of historical record. In the source file, we have a new Begin Date, so I want to close out the current End Date on the target and have a new row that opens with this new Begin Date.   2) We have a Business Key (Student_ID) and a Surrogate Key (STD_KEY). On these new records from the source, it is the Student_ID that has new values, so I would think that is the column I need to check for changes on. However, it is the Business Key. I want to retain the exisiting Surrogate Key.   Ultimately where we have: STD_KEY 02 STUDENT_ID 1234 BEGIN_DATE 01JAN2006 END_DATE 01JAN5999   I want the new source data to generate a second row for this Surrogate Key with the new Student ID value with both rows looking like: STD_KEY 02 STUDENT_ID 1234 BEGIN_DATE 01JAN2006 END_DATE 14JAN2008   STUD_KEY 02 STUDENT_ID 5678 BEGIN_DATE 15JAN2008 END_DATE 01JAN5999   What I'm getting is the following that will come across as two totally unrelated records on our target table: STD_KEY 02 STUDENT_ID 1234 BEGIN_DATE 01JAN2006 END_DATE 01JAN5999   STUD_KEY 03 STUDENT_ID 5678 BEGIN_DATE 15JAN2008 END_DATE 01JAN5999   This seems like it should be very easy to do. What I'm doing though is adding more rows with new Surrogate Keys to my target table and I'm not closing out any dates.   Thoughts? ... View more

DI Studio 4.9 SAS 9.4   I'm working with several DI Studo jobs that seem to no longer recognize a library, where when they were run last year they did. Between then and now, we have migrated from 9.3 to 9.4 and moved to a new repository.   Most jobs in this process are working but there are a few that aren't.   Here's the behavior:   I'll open a job and I'm able to open the datasets referenced within no problem at all. All the Librefs seem to work fine. I'm opening the datasets and able to sort and filter the data.   However, once I run a node in the job (say, an extract) I get a message that all is successful. However, once I attempt to open the extract's work file, _or_ the tables that I could open, I get an error message:   "There was an error while initializing View Data. Details of the error are mentioned in the details section.   com.sas.workspace.WsAppServerLibraryException: Libref XXXXX is not assigned."   So, why were the tables and their data accessible prior to running any node and how do I resolve this besides rewritting all the jobs...   Thanks! ... View more

Hi all,   We've got several duplicate metadata folders in DI Studio within a folder 'System/Repaired Objects'. These folders contain objects such as tables and reports. I can delete the duplicate tables, but when I attempt to delete a duplicate report I get the following messages.   When trying to delete from DI Studio: "(report) in (folder) is of a type whish is not recognized and will not be deleted."   When trying to delete from Management Console: "Delete is not supported as information to delete this object is unavailable."   Does this look familiar to anyone? How is there a way to get these removed?   Thanks! ... View more