@ChrisBrooks,   I've checked the name several times. I think it is something else. If someone knows why it could be happening, please share 🙂   Anyway, the step by step you've said makes sense and it works with the _all_ option, so thanks again.     May15 ... View more

Hi @ChrisBrooks,   Using the ic delete _all_ it actually works. I have no idea why it doesn't when I name the keys.     Thanks,   May15 ... View more

Hi @JBailey,   Many thanks for sharing your code. One question, why do you say it doesn't help me? Actually, the process I mentioned works in order to make the file smaller: I've tested it. To replace the original table with the data I want, the table loader transformation in SAS DIS generates a proq sql with the CREATE TABLE AS statement and, as you also checked in your code, it saves space. The issue, as I said above, is when I have referential integrity constraints. Thus, I'd like to know what I could change in this kind of process in DIS to eliminate the errors I mentioned above. Any help will be appreciated.     @mkeintz, thanks for your point of view.     Thanks,   May15 ... View more

Hi all again,   Unfortunately, the idea I've posted in the original post isn't working. I'm getting the following errors:     WARNING: Target table is referenced by constraints in another table WARNING: Replacing entire table will fail. Consider an alternate load technique or revising constraints. ERROR: A rename/delete/replace attempt is not allowed for a data set involved in a referential integrity constraint.     In fact, this table has a primary key which is related to a foreign key in another table and also has a foreign key that is related to a primary key in another table. Just to remember, in order to save space, the process is to extract only the data I want and then load it to the same table. The load process was done with the table loader transformatin using the "Replace" style and with the default constraint conditions:   Before load: On table creation After load: Leave on     Any help to solve this issue??       Thanks,   May15 ... View more

Hi @JBailey,   Let me ask, what yould you suggest to clear the "slack" space in a SAS data set?     Thanks,   May15 ... View more

Hi @Patrick,   Maybe it is a redundant question but it has come up: Even if we create a data set with a different name from the one that is in the "set" instruction, we also lose the indexes and constraints information from A, right? I mean:   data B; set A; if <condition>; run;   Thanks,   May15 ... View more

Sure LinusH.   Thanks,   May15 ... View more

Hi JBailey,   Thanks for your tips. In fact, it's a shame that the delete transformation doesn't save any space.       Thanks,   May15 ... View more

Hi LinusH,   I've found the issue... The extract transformation had the option "Create as view" checked. I unchecked this and now it works.   By the way, using this approach, we don't lose any constraints and indexes of the data, right?     Thanks,   May15 ... View more

Hi LinusH,    Thanks for your reply.   I've tried but it doesn't work. I've got the following error:   ERROR: Attempt to append a view to itself.   However, it results in a table, not in a view. I don't know if I understood the restriction you've said.     Thanks,   May 15 ... View more

I can't specify the real fields but it is like you said:   proc datasets library=myLibrary nolist; modify mytableB; ic delete forkeymytableB; modify mytableA; ic delete primkeymytableA; quit;   where forkeymytableB has the same name as the primkeymytableA (forkeymytableB refers to primkeymytableA)   And this is the output running the proc contents of mytableB:     Thanks,   May15 ... View more

Hi ChrisBrooks,   Many thanks for your answer.   I've tried something like that but when I try to delete the foreign key I've got a warning saying the foreign key doesn't exist... It doesn't make sense because when I run the proc contents of that table I actually can see it and also in the metadata of the table...   I have no idea why it is happening. I've checked the syntax and it is ok. I'm doing this in the user written code of SAS DIS, I don't know if it has any impact.       Thanks,   May15   ... View more