René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Got a weird error msg: STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.","articleBody":"Awesome code, this is super helpful for a project I'm working on.\r\n\r\nOne thing that came up today was an error msg being returned from vStats view\r\n\r\n\"STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.\"\r\n\r\nLooking at the code I figured out I could toss a CAST statement in vStats view to make sure the return came back as NVARCHAR(MAX).  I think this happens when there's a large number of columns in a table or the column names are rather long?\r\n\r\n`select sc.object_id, sc.stats_id, string_agg(CAST(c.name AS NVARCHAR(MAX)), ',') as stat_columns...`\r\n\r\nI think this may be causing another issue when running the stored procedure StatsOptimize as below:\r\n`exec  dbo.[StatsOptimize]  @Tables=null, @StatisticsModificationLevel=null, @StatisticsSample=null ,@OnlyModifiedStatistics=null,@DeleteOverlappingStats='Y', @TimeLimit=null , @Execute=null `\r\n\r\nReturns Error:\r\nArithmetic overflow error converting numeric to data type numeric.\r\n\r\nI'm testing this out now in my environment and I'll let you know by responding to this post.","author":{"url":"https://github.com/jtbrown52","@type":"Person","name":"jtbrown52"},"datePublished":"2022-03-17T16:22:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/2/SynapseTools/issues/2"}