Monday, December 19, 2011 6:05 PMWe 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)
- Edited by wongnation Monday, December 19, 2011 6:05 PM
Tuesday, December 20, 2011 8:42 PMModerator
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 Cline
Tuesday, December 20, 2011 9:20 PM
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.
- Edited by wongnation Wednesday, December 21, 2011 4:29 AM