Field that should have been a file

  • Hello all,

    Funny thing happened when I inherited a database....

    A few tables have analytic output in varbinary(max) large fields. The data is hex, some over 24 million characters in one field... Mercifully the table only has 1,000 records. Average field size is still over 10 million bytes.

    Problem is that I need to parse large pieces of data and analyze, count, lather-rinse-repeat from the field. I'm not sure how to scale the standard convert to handle this much data in a single field.

    Previous posts referenced this construct which works on reasonably sized data: CONVERT(varchar(2000), left([MyBigField], 2000), 1)

    This may be time to resurrect CLR app to parse out a few dozen metrics n times per monster-field...

    Well maybe it wasn't such a funny thing after all, :w00t:

    TIA

    Tom in Sacramento - For better, quicker answers on T-SQL questions, click on the following...http://www.sqlservercentral.com/articles/Best+Practices/61537/

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply