An Idea Exchange for SAS software and services

by Respected Advisor
on ‎09-16-2015 02:12 PM

I suppose you are talking about the query builder behavior, and the answer is a big NO. If you see the code generated by the query builder, all the requested columns are selected explicitly, even the case when you need all of the columns. There are underlined reasons for SAS choose to do this (select * vs select columns), the advantage of choosing 'select colunms' over 'select *' becomes obvious when you deal with RDBMS data, which is a common task for SAS. Please feel free to google the reason if you are interested.

Now get back to your problems, the only way to get around is to code it such as (select *) all along in your project after you rename your variable. And I am also puzzled by your statement, "but I'd like to be able to run with the correct variable name through-out the whole flow." Why?


by Regular Contributor
on ‎10-29-2015 10:13 AM

I think this is a horrible torturous thing to ask the developers to do...   But I would SO use it.  To my defense, this is the only time I've ever supported torture.

by Community Manager
‎05-18-2017 01:33 PM - edited ‎05-18-2017 01:34 PM
Status changed to: Not Planned

SAS Data Integration Studio (and related SAS Data Management tools) are much better suited to support the discipline of following the chain of changes and impact analysis.  Table and column metadata is a baked-in component of those tools.  However, SAS Enterprise Guide doesn't track the data and column use to that level -- and there aren't near-term plans to add it.  For folks who need this level of governance, we usually recommend the data management solutions.


(I appreciate @PhilC's concession that this might be a difficult thing for R&D to implement.)

Idea Statuses
Top Liked Authors