Problem Note 69967: An SQL Server pre-assigned library uses the wrong schema
 |  |  |  |  |
After applying Hot Fix J6Q006, a pre-assigned LIBNAME using the SQLSVR engine might specify the wrong schema name.
There circumvent this issue, complete either of the following workarounds:
- Set the extended attributes metadata property on the library to specify AssignMode=1.
- Mark the library as not pre-assigned. Then, assign the library via an autoexec or code.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Microsoft SQL Server | Microsoft® Windows® for x64 | 9.4_M7 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8 Enterprise x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8 Pro 32-bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8 Pro x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 8.1 Pro x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 10 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows 11 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 R2 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 R2 Std | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 Std | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2016 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2019 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2022 | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Enterprise 32 bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Enterprise x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Home Premium 32 bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Home Premium x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Professional 32 bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Professional x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Ultimate 32 bit | 9.4_M7 | 9.4 TS1M7 | ||||
| Windows 7 Ultimate x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| 64-bit Enabled AIX | 9.4_M7 | 9.4 TS1M7 | ||||
| 64-bit Enabled Solaris | 9.4_M7 | 9.4 TS1M7 | ||||
| HP-UX IPF | 9.4_M7 | 9.4 TS1M7 | ||||
| Linux for x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Solaris for x64 | 9.4_M7 | 9.4 TS1M7 | ||||
A fix for this issue for SAS/ACCESS Interface to ODBC 9.4_M7 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J2X.html#69967A fix for this issue for SAS/ACCESS Interface to Microsoft SQL Server 9.45 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J6Q.html#69967
Pre-assigned libraries that use the SQLSVR LIBNAME engine might specify the wrong schema.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2023-04-04 11:06:40 |
| Date Created: | 2023-03-22 11:34:00 |