Situation: TransactionScopeRequired OperationBehavior WCF Service. A process that inserts several rows into a database using SqlBulkCopy is conducted by WCF Service.
SqlBulkCopy successfully inserts records when used without the TransactionScopeRequired behavior, however when this behavior is set to true, not even a modest number of records can be placed.
More details - The MSMQ Endpoint is used by the WCF Service.
Okay, I apologize for posting this so late. :)
After further research (I'm embarrassed to write this! The Task Processing Library was used to create my service, thus I had numerous processes performing DB requests wrapped inside of a TransactionScope, for example.
-The first process acts on the database. This operation resulted in a database lock and appended a transaction to the transactionscopes transaction.
A second process is subsequently launched, however it is unable to write to the same table since the transaction was not included in the first transaction scope.
The best way to offer improved transaction management is to redesign.