Problem Note 62579: You see "...Invalid object name..." after PROC SQL pass-through code creates an INSERT statement that excludes ## symbols from a temporary table name
SAS® Data Integration Studio jobs that contain automatically generated PROC SQL explicit pass-through code for Microsoft SQL Server temporary tables might fail. You see an error message that is similar to the following in the SAS log:
ERROR: CLI execute error: [SAS/ACCESS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Invalid object name
'temporary-table-name'.
The error is caused by the lack of double number symbols (##) in the name of the temporary table. When the SQL join transform generates code, the INSERT statement should look like this:
insert into ##table-name
select
However, when this problem with PROC SQL occurs, the same code portion is generated in this way and does not include the ## symbols:
insert into table-name
select
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Data Integration Studio | Microsoft® Windows® for x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise 32-bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Pro 32-bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Pro x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise 32-bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro 32-bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 10 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2008 | 4.901 | | 9.4 TS1M3 | |
Microsoft Windows Server 2008 R2 | 4.901 | | 9.4 TS1M3 | |
Microsoft Windows Server 2008 for x64 | 4.901 | | 9.4 TS1M3 | |
Microsoft Windows Server 2012 Datacenter | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Datacenter | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Std | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2012 Std | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Enterprise 32 bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Enterprise x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Home Premium 32 bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Home Premium x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Professional 32 bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Professional x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Ultimate 32 bit | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Ultimate x64 | 4.901 | 4.904 | 9.4 TS1M3 | 9.4 TS1M6 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
SAS® Data Integration Studio jobs that contain generated PROC SQL explicit pass-through code for Microsoft SQL Server temporary tables might fail. After a failure, you see an "...Invalid object name '
temporary-table-name'" error in the SAS log.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2018-07-09 15:37:36 |
Date Created: | 2018-07-05 11:08:07 |