
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SQL##f - SqlState: S0002, ErrorCode: 208, ErrorMsg: [Microsoft][ODBC SQL Server Driver][SQL Server]I
HI Team ,
how to resolve below issue :
SQL##f - SqlState: S0002, ErrorCode: 208, ErrorMsg: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name '#Temp'.
please help us my document is failing in qmc continuously.
Thanks In Advance
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @SNR1
This is related to temporary tables in SQL Server, please refer to the following documentation that might help:
Look at the "Temporary Tables" section
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-table-transact-sql?view=sql-server-2017
Have you executed the SP from the Microsoft SQL Server Management Studio and verify that it runs successfully ?
Have you asked to your internal team, dba admin if temp files are deleted at some point or if there is something going on in the TempDB?
Kind regards.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @SNR1
This is related to temporary tables in SQL Server, please refer to the following documentation that might help:
Look at the "Temporary Tables" section
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-table-transact-sql?view=sql-server-2017
Have you executed the SP from the Microsoft SQL Server Management Studio and verify that it runs successfully ?
Have you asked to your internal team, dba admin if temp files are deleted at some point or if there is something going on in the TempDB?
Kind regards.
.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nikhil, did Nadia's post get you what you needed, or are you still working upon things? I do agree with her that this is a SQL issue, not a Qlik issue, we are simply returning the error sent back from the ODBC/OLE DB client connector in this case in our log... Microsoft Support would be the likely experts on this one, but I suspect your SQL DBA's can likely assist as well. Please leave an update as to where things stand, and if Nadia's post did help, be sure to circle back and use the Accept as Solution button to give her credit for the help. You use the button on the post with the information that helped with things.
Regards,
Brett
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Brett/Nadia
