Upgrading a SAS 9.4 environment is not like a standard software patch. You must use the and SAS Deployment Wizard .
Many banks and hospitals were forced to isolate older SAS versions behind firewalls. M8 can sit safely on the corporate network.
Output Delivery System (ODS) graphics have always been a strong suit of SAS. In M8, users will find incremental improvements in the rendering of graphics and the handling of ODS destinations. These updates ensure that reports generated in SAS remain compliant with modern web standards (HTML5, PDF accessibility standards), which is a requirement for many government and public-facing organizations. sas 9.4 m8
: SAS has established a dedicated SAS 9 Division to manage the platform, ensuring quarterly security updates and future maintenance releases (such as the June 2025 release of 9.4M9) are available as customers plan their eventual transition to the cloud.
If you are a regulated industry (Pharma, Banking) with validated SAS 9.4 workloads that run perfectly, stay on M8 through 2028 . SAS will support M8 with security hotfixes until at least 2030 (standard SAS lifecycle: 5 years mainstream + 5 years limited). Upgrading a SAS 9
: Replaces VMware tcServer as the underlying web application server.
: SAS 9.4M8 is under Standard Support until February 1, 2028 . M8 can sit safely on the corporate network
| ID | Description | Workaround | |----|-------------|-------------| | M8-001 | PROTOPY requires Python 3.8+ and saspy installed separately for now. | Install saspy via pip; SAS will bundle in M8 hotfix 1. | | M8-002 | SAS Studio Git integration fails with self-signed certs. | Add cert to Java truststore. | | M8-003 | PROC HTTP OAuth2 refresh token not automatically renewed. | Manual refresh using REFRESH_TOKEN parameter. | | M8-004 | SAS Work encryption (AES-256) increases I/O by 10–15%. | Use only for sensitive data. |