Deadlock in tempdb under SQL Server 6.5

  • I am using SQL Server v6.5 sp5 under Windows NT 4.0 sp6.

    Recently, I turned on trace flags 1204 and 3605 to keep track of deadlock problems.

    I found that the deadlock database displayed in SQL server log was always tempdb (dbid =2) and the input buffer showed sp_ddopen.

    Our applications do not create user-defined temporary tables.

    How can I find out the possible reasons?

  • Also be aware that subqueries and orber by generate space in tempdb for storage. Are you using either in you code. If so it may be these type processes.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • Itis understood that clause "order by" will use tempdb. However, the temporary space in this case is fully controlled by SQL Server v6.5 If I encountered deadlock because I used "order by". How can I solve the problem?

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply