My experience with PROC SQL pass-through to Amazon Redshift (and this probably applies to many other databases) is that character variables are often created much larger than they need to be. I'd like to see an option added to PROC SQL that will automatically scan the data returned from the external database to determine the maximum length needed for each character variable and apply that length when building the output SAS dataset.  Granted this will increase processing time which is why it should be optional, but this would be an improvement over having to post-process the dataset to shorten the character variables as we do now.   Perhaps something like this? PROC SQL SHRINK; ... View more

See how SAS 360 Marketing Decisioning can be deployed into customer cloud environments while keeping customer data local and close to the systems that make real-time decisions possible. Discover the architectural concepts, deployment patterns, and operational considerations behind running real-time decisioning in customer cloud environments and see why SAS-Managed is the recommended approach for most customers. ... View more

Team Name Salinas Track Banking Use Case Transform global financial news into quantitative textual factors and combine them with traditional factors to develop and backtest investment strategies. Technology SAS Viya, NLP, multilingual text analytics, machine learning, and quantitative factor modeling. Region (North America) NA Team lead Acorn Shi Team members Communities @lzha_ncstate Communities @shaymj Social media handles www.linkedin.com/in/acorn-shi www.linkedin.com/in/lezhi-zha-126799328 www.linkedin.com/in/mingwei-shay-jiang Is your team interested in participating in an interview? Yes Optional: Expand on your technology expertise     ... View more

SAS Viya column lineage is only available for flows that are stored in Content. However, Git is only available for flows on NFS. Unfortunately, these are mutually exclusive options. Are more people running into this issue, and are there any ideas for possible workarounds ... View more

I'm looking for team members!   I'd like to experiment with creating a data pipeline for real world evidence generation, with a big emphasis on traceability. One possible approach could be: Load real-world data using APIs Map the data to a CDISC-like structure Apply quality and traceability checks Then either: assess whether a real-world data source is fit for purpose for a hypothetical study protocol (as per FDA guidance), or perform monitoring and trend analysis similar to post-market surveillance About me: I currently work as a Statistical Programmer in the biotech industry. My goals for the hackathon are to try out SAS Viya (I use EG professionally), explore API connectivity from SAS, and refresh my knowledge of CDISC standards.   I'd love to find teammates with expertise in CDISC, cloud technologies, or AI/ML.  Please message me on here if you're interested 🙂  ... View more