My question - is there a known issue with loading a SQL Server 2000 table and using a SQL Insert/Update/Delete Triggers with Vimp 4.5.10.
If so, is there a solution to this issue.
Here is some background:
When trying to load from excel spreadsheet to SQL Server 2000 Table with Insert/Update/Delete trigger on it.
We received the following message from Vimp 4.5.10 in the Transformation Log -- HY000[Microsoft][ODBC SQL Server Driver] Connection is busy with results for another hstmt --
And then Vimp just hangs and the cpu usage goes to 100%.
The only way to break out of this is to end the .exe process in task manager.
After researching this issue - the problem is related to Sql Triggers on the table we load information to. We had an insert/update/delete trigger on this load table so we could keep track of how many changes are made to this table. If the trigger is applied, we get the message listed above from Vimp but if we remove the trigger Vimp inserts the records just fine.
The funny thing is that these triggers have worked for us in the past and have just started failing this week.
We did test the triggers outside of Vimp and they work as expected.
We are able to work around this issue but we thought we would ask to see if this issue has happened to anyone else.
Any info would be appreciated. Thanks.
