We are using the SQL Server provider for logging AppFabric WF tracking data, and it appears to be truncating variable values at 318 characters when extracting values from the staging table. Is there a reason for this length being used, as opposed to, say, nvarchar(max)?
CREATE function [dbo].[ASInternal_ExtractCustomPropertiesFromXml] (@propertiesXml xml) returns table as return ( select T.p.value('@name', 'nvarchar(128)') as [Name], T.p.value('@type', 'nvarchar(128)') as [Type], case T.p.value('@type', 'nvarchar(128)') when N'System.Char' then cast(T.p.value('.', 'nvarchar(318)') as sql_variant)
19 ธันวาคม 2554 18:05
- แก้ไขโดย wongnation 19 ธันวาคม 2554 18:05
I am not sure why this is being used and this sounds like an unusual value for the length of the tracking property. I can submit your question on the Connect site for AppFabric. As far as I know this forum is not actively monitored by Microsoft.
If this answers your question, please use the "Answer" button to say so | Ben Cline20 ธันวาคม 2554 20:42ผู้ดูแล
Yes, that would be great. Let me know if you need any other information. Thanks.
Edit: I would also add that since this is a UDF, we changed this to nvarchar(max), which seems to work, but are concerned about any downstream functional implications of this change.
20 ธันวาคม 2554 21:20
- แก้ไขโดย wongnation 21 ธันวาคม 2554 4:29