In our SQL Server Job Activity Monitor I saw, that 2 of our Cireson jobs fail every day: Cireson Insert New Incidents: There is already an object named 'tempTable_Incident' in the database. [SQLSTATE 42S01] (Error 2714). The step failed. Cireson Update Existing Changes: There is already an object named 'tempTable_Change' in the database. [SQLSTATE 42S01] (Error 2714). The step failed. I thought the "IF NOT EXISTS(SELECT [name] FROM tempdb.sys.tables WHERE [name] like 'tempTable_Change%') BEGIN" checks if the temp table already exists? How could I solve that?

Hi Simon, That's a new job since v 11.2. Can you please log an Incident with our support team on this? Do you know how? Geoff

Options

2 Cireson SQL Jobs fail

Simon_Zeinhofer Customer Ninja IT Monkey ✭✭✭✭

November 2021 edited November 2021 in SQL Server

In our SQL Server Job Activity Monitor I saw, that 2 of our Cireson jobs fail every day:

Cireson Insert New Incidents: There is already an object named 'tempTable_Incident' in the database. [SQLSTATE 42S01] (Error 2714). The step failed.
Cireson Update Existing Changes: There is already an object named 'tempTable_Change' in the database. [SQLSTATE 42S01] (Error 2714). The step failed.

I thought the "IF NOT EXISTS(SELECT [name] FROM tempdb.sys.tables WHERE [name] like 'tempTable_Change%')

BEGIN" checks if the temp table already exists? How could I solve that?