Question

Certainly there is some type of context switching, marshaling, serializing, etc that takes place when you choose to write a stored procedure in NET vs T/SQL.

Are there any hard facts about this overhead as it relates to making a decision about using .NET vs T/SQL for stored procedures?

What factors do you use in order to make the decision?

For me, developing in C# is 1000% faster than developing in T/SQL due to my learning curve, but when does this gain not offset the performance hit (if there even is one)?

Answer 1

I’d say it depends.

Some things you will find using CLR procedres are better

1. Using native .NET objects — file system, network, etc
2. Using features not offered by TQL or not as good as .NET e.g regular expressions

For yet others you will find TSQL procedures are better, either in terms of ease of use or raw execution speed

1. Using set based logic (where abc in def or abc not in ghi)
2. CRUD operations