StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMoving C# in Process Functions to SQL Server CLR functions
primarykey
Id
3831898
data
AcceptedAnswerId
3831994
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-30T15:05:29.397
FavoriteCount
1
LastActivityDate
2015-10-03T19:21:44.177
LastEditDate
2010-09-30T15:14:07.300
LastEditorUserId
161852
OwnerUserId
161852
ParentId
0
PostTypeId
1
Score
3
ViewCount
582
LastEditorDisplayName
text
Body
What are the limitations, unexpected pitfalls and performance traits of moving from in process C# code to SQL CLR Functions? We currently have several data heavy processes that run very fast using in process C# Asp.net MVC project without using a db at all. Performance is very important. The application uses a static in memory cache and performs complex operations to arrive at a final result. Cache updating is a bit of a pain and we are considering moving some of these processes to SQL Server queries that would just output the final result so that less data caching is needed at the c# app level. The processes are complex and we know that moving to the database would require extensive use of SQL Server CLR functions. We see a lot of advantages in leveraging the database, but the required use of CLR functions gives pause for a few reasons: No Azure: SQL CLR functions are <a href="http://simonmunro.com/2010/02/08/is-spatial-support-needed-in-sql-azure/" rel="nofollow">not supported by Azure</a>, High Testing Cost: the SQL CLR functions could be slower and testing will take significant work Small User Base: An hour of googling reveals that use of CLR functions is somewhat uncommon which makes community support (and possible MS support) a concern. I would love to hear from someone who has moved a C# app from in process to CLR functions. In your answers please assume that custom SQL CLR functions are required.
Tags
<c#><sql-server><sqlclr><clrstoredprocedure>
Title
Moving C# in Process Functions to SQL Server CLR functions
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USGlenn
UserOwnerUserId
1. USGlenn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POMoving C# in Process Functions to SQL Server CLR functions
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POMoving C# in Process Functions to SQL Server CLR functions
 UserUserId
 USGlenn
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POMoving C# in Process Functions to SQL Server CLR functions
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.