5
5by5
We are encountering application hangs, followed by a timeout under the
following circumstances when running a ProjectTasksCreate method with the
PDSTEST utility.
We have a trigger on table MSP_TASKS.
1. If the trigger has only SELECT's (on inserted/deleted tables) and
DECLARE's/assignment statements, ProjectTasksCreate succeeds. SQL trace
shows only one database connection established, with relevant SQL calls
(INSERTs and SELECTs) all occurring with the BEGIN TRAN...COMMIT TRAN scope.
2. If we modify the trigger on MSP_TASKS to INSERT a row into a user table,
PDSTEST hangs on the ProjectTasksCreate. The SQL trace now shows the same
SQL calls, but now broken across 2 separate database connections:
- The first connection does its BEGIN TRAN and INSERT of the new task into
MSP_TASKS
- The 2nd connection is then established and waits on a "SELECT TOP 1
TASK_IS_SUMMARY FROM MSP_TASKS WHERE PROJ_ID = 7 AND TASK_ID > 0 ORDER BY
TASK_ID DESC" because the first connection is in the middle of its BEGIN TRAN.
Any idea why PDS is creating 2 database connections, just from having an
INSERT statement within our trigger? We re-GRANTED INSERT, UPDATE, etc. on
the user table to MSProjectServerRole just to be sure, to no effect. No
timeouts occur when creating a task with Project 2003 client, only PDS.
Thanks for your help.
following circumstances when running a ProjectTasksCreate method with the
PDSTEST utility.
We have a trigger on table MSP_TASKS.
1. If the trigger has only SELECT's (on inserted/deleted tables) and
DECLARE's/assignment statements, ProjectTasksCreate succeeds. SQL trace
shows only one database connection established, with relevant SQL calls
(INSERTs and SELECTs) all occurring with the BEGIN TRAN...COMMIT TRAN scope.
2. If we modify the trigger on MSP_TASKS to INSERT a row into a user table,
PDSTEST hangs on the ProjectTasksCreate. The SQL trace now shows the same
SQL calls, but now broken across 2 separate database connections:
- The first connection does its BEGIN TRAN and INSERT of the new task into
MSP_TASKS
- The 2nd connection is then established and waits on a "SELECT TOP 1
TASK_IS_SUMMARY FROM MSP_TASKS WHERE PROJ_ID = 7 AND TASK_ID > 0 ORDER BY
TASK_ID DESC" because the first connection is in the middle of its BEGIN TRAN.
Any idea why PDS is creating 2 database connections, just from having an
INSERT statement within our trigger? We re-GRANTED INSERT, UPDATE, etc. on
the user table to MSProjectServerRole just to be sure, to no effect. No
timeouts occur when creating a task with Project 2003 client, only PDS.
Thanks for your help.