Hi there,

THanks for your thoughts. let me explain the problem scanerio:

We have a BOMWALKDOWN which is a lengthy process and every child in the BOM will be exploded and if there is an impact to one it ripples to lot of children and as well we do BOMWALKUP where Parents get affected. This result will be quite a pain for the customers. They have to wait for more than 5 mins or sometimes they will not be able to get the results because of timeout issues. So what we proposed is that user can give the data in chunks of 5% of the load everytime and then SP will do a BOMWALKDOWN or BOMWALKUP for those materials. Then once that gets completed the client will send the next 5% data to the same SP. This will be ok and the overhead will be maintaining a counter for the transaction all the time. So I was thinking if we can use CLR to do the same task, client need not bother about maintaining a counter for the batch mode. We can spawn threads to call the SP, all the data can be consumed in one time by the CLR SP and then it would inturn call the transaction SP (this does the real BOMWALKDOWN or BOMWALKUP).

By the way we are not doing any BULKINSERT in these scanerios it is just a SELECT which will be sent to the client (internally the SP will use table variables for storing the impacts and joining with different tables).

Thanks

John