https://communities.sas.com/t5/SAS-Programming/Re-SAS-optimizations-with-MS-T-SQL-and-robust-systems-servers/m-p/242751#M45129 <P><SPAN class="login-bold">saskiwi&nbsp;this ended up being a fun proof of concept for creating two tables I could then compare in sas. &nbsp;I still run into issues with nulls vs missing values (some columns may have both '' and nulls in sql, blank = '' in sql while it could represent null in sas). Anyway to mass state "if missing or null treat as null" so that '' = null? Otherwise I can do case statements and cast blanks as nulls in sql.</SPAN></P><P>&nbsp;</P><P>The second question... how could I post the work table back to sql using sql passthrough? thanks!</P> Mon, 11 Jan 2016 16:45:52 GMT jroe 2016-01-11T16:45:52Z https://communities.sas.com/t5/SAS-Programming/Re-SAS-optimizations-with-MS-T-SQL-and-robust-systems-servers/m-p/242751#M45129 <P><SPAN class="login-bold">saskiwi&nbsp;this ended up being a fun proof of concept for creating two tables I could then compare in sas. &nbsp;I still run into issues with nulls vs missing values (some columns may have both '' and nulls in sql, blank = '' in sql while it could represent null in sas). Anyway to mass state "if missing or null treat as null" so that '' = null? Otherwise I can do case statements and cast blanks as nulls in sql.</SPAN></P><P>&nbsp;</P><P>The second question... how could I post the work table back to sql using sql passthrough? thanks!</P> Mon, 11 Jan 2016 16:45:52 GMT https://communities.sas.com/t5/SAS-Programming/Re-SAS-optimizations-with-MS-T-SQL-and-robust-systems-servers/m-p/242751#M45129 jroe 2016-01-11T16:45:52Z