My problem is the following:
I've created a SSIS package that will run without any problems in my development environment, but when I move the databases and SSIS packages to another testenvironment it will trigger the SQL Server to dump on every sub-sequent command.
The chain of events:
- Create the SSIS package and databases in my development environment.
- Run tests wich has no problems.
- Move the SSIS package and create backups of the database from my development environment and restore the database in the testenvironment which is in an different AD using an AD-account from that AD.
- I run the SSIS package without any problems.
- But when I look in the SQL Server logs I can see that the SQL Server is dumping on what I presume is every access. The SQL Server service continue running but won't return any results and the databases are not connectable.
When debugging the problem I think I've located the problem to when I run the following code.
TRUNCATE TABLE claim
When I searched the MSDN Forums I found a thread with at problem that seems similiar to mind.
Has anyone seen this problem before
If it is the same bug as in the linked thread is there any known Hotfix for this problem