A new update is available for SAS Studio , version 3.82 : Hot Fix: M3T010 - Published 28NOV2024 , Download link for M3T010 Component name: SAS Studio Related SAS release: 9.4   Issues addressed in M3T010 SAS Note 71019 The SAS® Studio query builder might not display a complete list of values when you select \"Get Distinct Values\" This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for M3T010   Note: A comprehensive list of all SAS hot fixes is available from support.sas.com. You can use the SAS Hot Fix Analysis, Download, and Deployment (SASHFADD) tool to manage your SAS hot fixes. ... View more

I use SAS 9.4 to do anova analysis, and fallow the instruction, the result only shows anova but didn't show tukey. Are there any problem with software. ... View more

One of the best ways to learn is from experience. It’s perhaps even better to learn from other people’s experience, to avoid making the mistakes yourself. It is therefore always good to hear from SAS customers and partners about their experiences using SAS and particularly migrating to new versions or upgrading their infrastructure. I recently hosted a webinar featuring Coskan Yetginer, the Data Engineering Manager at energy company Enerjisa, and Vedat Cumhur Özkan, Head of Data Management at Sade Software and Consultancy, a leading SAS partner in Turkey, talking about Enerjisa’s experience of moving from SAS 9 to SAS Viya. Here are my top takeaways from the event.   Relationships with and between customers and partners are often built over many years We talk a lot about the importance of relationships in B2B marketing and sales. However, we don’t very often look in detail at particular partnerships, and that may blind us to the fact that many partnerships—both direct with customers, and via partners—have been built up over many years. Cumhur explained that SADE and Enerjisa had been working together for more than a decade, delivering successful projects with the SAS environment. I believe this long-term working relationship is an essential element in the success of big IT projects.   Kotter was right about needing a ‘burning platform’ to drive change John Kotter’s eight steps to change start with the creation of a sense of urgency: a so-called ‘burning platform’ from which to drive change. This is a long-established model of change management, but clearly still relevant. Coskan talked about four main reasons for needing to move from SAS 9 to SAS Viya. The first was the growth in data volume that had made it hard to track and manage data effectively in SAS 9. He explained that working at 90% capacity was making the system unstable. The second reason was the inability to set up a disaster recovery system because of the high disk space requirement. The third was the inability to meet requirements for automation security and internal audits, and finally, there was a desire to reduce management and maintenance costs by moving to a more modern infrastructure. The lack of capacity in particular had become an urgent problem and was driving the move.   Every customer has a slightly different approach to using SAS I always like to hear how customers use SAS. Coskan explained that Enerjisa has been using SAS since 2014. Projects and reports on SAS range from field operation reporting to financial revenue assurance projects. The company primarily uses SAS as a business intelligence tool across almost all business units. The low code/no code environment had enabled this to spread across the company, supported by the ability to gather data from multiple sources. However, Enerjisa also uses SAS in a more sophisticated way, as an AI tool to forecast demand for electricity using a multi-model structure. Machine learning models are also an important part of predicting electricity meter failures and other field operations. This history of both high-level use of very advanced capabilities and broad company-wide use of a much less specific capability is a reminder that customers may have a wide range of uses for SAS products.   You need to build the right team to support migration Coskan reported that building the right team was the most important step in delivering the migration—even before building the infrastructure. The team included the entire data engineering core team, 21 people, working with 10 consultants from SADE with support from SAS Turkey. There were also 15 members of the data management team and 40 people from business units to test and finalise the project. This gave a total of 86 people, over a period of 200 days. The team spent a lot of time communicating with business units to keep them abreast of developments. Coskan added that it had been crucial to involve other IT teams in the migration work, especially the information security and network teams. This had enabled resolution of critical issues such as getting hardware ready and managing security updates.   Adequate planning and organizing is essential in delivering change Coskan described the process across eight months, three for planning and six for execution, with an overlap in the middle. In the discovery phase, the team identified which teams used SAS, to work out who should be involved, reviewing all workflows with the Viya team and the business units. They identified 200 workflows, each of which was considered a mini project. This enabled the system to be cleansed of unused workflows—helpful given that Enerjisa had been running the same system for more than 10 years. A specific tool was used to divide projects into tasks, and assign the tasks, which were evaluated using the Scrum methodology. This provided a clear plan, which had enabled the project to be managed.     Documentation may be dull, but it can be critical to success Coskan emphasized the importance of documentation in delivering the migration project. He explained that at the start of the project, there had been some confusion about coding practices, library naming, and comments, particularly how to comment. To address this, the team held three-day sessions to create a guide with key stakeholders. They then used this documentation throughout the project, updating it as new issues arose and were resolved.   Measuring success is important to demonstrate value for money Coskan described the benefits that have been delivered through SAS Viya. There had been a 95% reduction in use risk and a 50% reduction in disk needs, from 200 terabytes to 100 terabytes, plus a 40% reduction in average process time for each workflow. These achievements had been possible through data compression, and because of the capabilities of SAS Viya. The migration had therefore made the system sustainable for the future. It had also solved the issues of information security and internal audits, as well as providing some unexpected benefits and opportunities.    If you would like to delve deeper into the topics discussed during our webinar, you can watch the on-demand recording at your convenience for more insights and valuable information. ... View more

Hi,   Just wondering if anyone here tried integrating SAS Job Execution in SAS Visual Investigator. I tried putting the link of the job via Page's hyperlink but it does not work. The link indicated ".../SASJobExecution/..." becomes ".../SASVisualInvestigator/..." when I tried to preview the page and checked the link.   Can someone help how to do it? Thanks.   Regards, Rian ("Ryan") ... View more

I have run these codes but in the last step the choice sets are not coming in blocks %MktRuns(3 3 3 3 2 2) %MktEx (3 3 3 3 2 2, n=36) proc print; run; %macro res; do i = 1 to nalts; do k = i + 1 to nalts; if all(x[i,] >= x[k,]) then bad = bad + 1; /* alt i dominates alt k */ if all(x[k,] >= x[i,]) then bad = bad + 1; /* alt k dominates alt i */ end; end; %mend; %choiceff(data=design, model=class(x1-x6/sta), nsets=36, flags=2, seed=123, options=relative, beta=zero); proc print; var x1-x6; id set; by set; run; proc format; value x1f 1 = 'Crop-specific advice' 2 = 'Weather forecasting' 3 = 'Market price and trend information'; value x2f 1 = 'SMS' 2 = 'Internet' 3 = 'Face to face'; value x3f 1 = 'Within 24 hours' 2 = 'Weekly' 3 = 'Monthly updates'; value x4f 1 = 'Free of cost' 2 = '₹100 per month' 3 = '₹300 per month'; value x5f 1 = 'Government extension services' 2 = 'Private extension services' ; value x6f 1 = 'General' 2 = 'Based on farm-level data'; run; proc print label; label x1 = 'Type of Service' x2 = 'Service Delivery Mode' x3 = 'Response Time' x4 = 'Cost of Service'; x5 = 'Service Provider Type' x6 = 'Customization of Advice' format x1 x1f. x2 x2f. x3 x3f. x4 x4f. x5 x5f. x6 x6f. ; by set; id set; var x1-x6; title "Formatted Choice Sets with Labels"; run; proc print data=bestcov label; title ’Variance-Covariance Matrix’; id __label; label __label = ’00’x; var x:; run; %mktblock(data=best, nblocks=4, out=blocked_design, seed=114) title; %mktdups(generic, data=best, factors=x1-x6, nalts=2) ... View more