Feedback
Did this article resolve your question/issue?

   

Article

DataDirect "The 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database" error with the Sybase ODBC driver

« Go Back

Information

 
TitleDataDirect "The 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database" error with the Sybase ODBC driver
URL Name000043015
Article Number000160721
EnvironmentProduct: Connect for ODBC Sybase driver
Version: All supported versions
OS: All supported platforms
Database: Sybase 12.5
Application: All ODBC applications
Question/Problem Description
The below error is received when calling SQLTables in a transaction. 
Steps to Reproduce
Clarifying Information
Error MessageThe 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database
Defect/Enhancement Number
Cause
Resolution
This is expected behavior.

The Sybase documentation states: "Avoid using data definition language commands on tempdb within transactions; doing so can slow performance to a halt. Always leave ddl in tran set to false in tempdb."

For additional information, refer to the Sybase documentation or contact Sybase technical support..

 
Workaround
Notes
Last Modified Date2/28/2018 9:37 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.