![]() I have used it quite extensively as well. I have received comments from some that such techniques are inefficient compared to SQL processing, however this is very rarely the case when all factors are considered. I tend to prefer the merge construct over SQL, particularly when developing complex joins involving multiple tables with complex rules for inclusion/exclusion in the resultant file, simply for the reason that it is possible to consider all records and output the "exclusions" to a separate file such that they may be reviewed. In my many years of working in IT, I have far too often seen SQL code that did not quite accomplish what was intended - records were unintentionally dropped due to incorrect coding of the where statement (note that the SQL where clause can be used to imply an inner join) or worse still, records were unintentionally duplicated due to improper key selection. I also liked the statements by Anders Skollermo concerning many-to-one and many-to-many joins, which are also quite correct. I especially like Chris Graffeuille's comment, "These diagrams are correct when the values of the key (ID) variables are not unique in *at most one* table." Very well stated and absolutely right. It's great to see the interest sparked by my comment. We also have a video on this topic, check it out:ĭid you find my PROC SQL join with data step comparison useful? Do you have any visuals that you go to time and again that you’d like to share? Have you taken a SAS training class yet? I’d love to hear from you, and hope to see you in class soon! Especially breathtaking is to watch how customers light up with the knowledge that they can now apply at work. It’s totally worth the years of ongoing research we do. As instructors, it’s rewarding to see how customers benefit from our training. ![]() That’s why they appreciate the top-notch content they receive in class. They poke around all kinds of resources to help manage their SAS jobs, whether online, peer-to-peer support or coming to take a class. I love to see the value savvy customers get from taking a SAS training course. They need to be admired, put on a pedestal and worshiped for the value they bring businesses! The sheer amount of work they do to streamline code and process so that business can become more efficient is bound to take anyone’s breath away. You guessed right - SAS programmers are a brilliant bunch. Since this captured the attention of the entire class as well, I thought it would be helpful to share with you as well, dear reader.Īs a SAS instructor, I’m very fortunate to rub shoulders with some of the most brilliant minds in the world. That student was referring to the tip I shared – the compare and contrast SAS data step with PROC SQL join slides. ![]() “Before, I would have to read about ten Google search results before I could find that content of the sort you shared in class.” “Phew! That tip alone was a life saver,” said a student in one of my SAS SQL classes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |