Integration Studio - Import SAS code: execution upon import?

[hulst]

Why does importing sas code also need to execute it?

Can I skip the execution of the SAS code when importing the code?

If the SAS code takes 1 hour to run and I have n files to import it will take (n x 1) hours.:smileyshocked:

I already know the .sas code is perfect and will run. :smileylaugh:

[LinusH]

Yes, you could wish for a more syntax analyzing import rather than a full execution.

Consider to add a options obs= in your code, which you could remove after the import.

[hulst]

A good point. Execution with less observations will run faster.

However an EG file with somewhere "proc SQL; drop table; create table as select * from other table;" does a lot of "damage" if just imported in the wrong server environment.

[LinusH]

This is typically part of a development process, and should NOT be done in prod environment.