locked
Undocumented Managed Metadata Limit: 256 Terms Per Item RRS feed

  • Question

  • Hello all,

    I am running into a limit on the number of Managed Metadata terms an item can have. The current limit I have found is 256 terms across all Managed Metadata fields in an item. This is the same issue illustrated here:

    http://kellydjones.com/archive/2011/05/22/145485.aspx

    I am running the April 2012 CU.

    This is not a matter of bad architecture, but a need to tag multiple items, akin to an ecommerce situation in which a product category may have list of related products over 256 items. Others have this need and find themselves moving away from using SharePoint.

    In short, I will not "DESIGN AROUND" this limitation as that does not help SharePoint grow as a product.

    Can anyone confirm if this is a hard database limit or configurable. I don't believe it is a hard database limit since the User Profile Service can accept more than 256 terms.

    Does anyone know if there is a fix for this, or if it will be included in a re-released June 2012 CU? I know a lot of focus is on SP 2013, but hoping some focus for updates is still in progress.

    Thanks,

    Kelly


    Personal Blog: http://thebitsthatbyte.com

    Friday, July 20, 2012 9:07 PM

Answers

  • In my case, it was 192 terms; the 193rd introduced too many parameters.  I also had some Enterprise Keywords on there, as well as the other standard document properties.

    For this limitation, you're stuck.  You'd have to submit a Design Change Request to Microsoft to somehow 'bulk load' these Metadata terms into SQL using more than one term per SQL parameter.  Or you'd have to submit a design change for SQL Server to accept >2,100 parameters.  In order to start this process, you'll have to open a PSS case.  Keep in mind that a DCR can take well over 6 months to resolve (I'm still waiting for wording within a TechNet article to change nearly a year later after a DCR was rejected, but the documentation was to be updated to reflect a limitation).


    http://sharepoint.nauplius.net

    • Marked as answer by Kelly Rusk Monday, July 23, 2012 1:18 PM
    Monday, July 23, 2012 12:31 PM

All replies

  • What does the stack trace look like on the item you're running into an error with?

    http://sharepoint.nauplius.net

    Sunday, July 22, 2012 4:22 PM
  • Actually, it looks like this is a SQL Server limitation:

    http://msdn.microsoft.com/en-us/library/ms143432.aspx

    Parameters per stored procedure

    2,100

    2,100

    Parameters per user-defined function

    2,100

    2,100


    http://sharepoint.nauplius.net

    Sunday, July 22, 2012 4:28 PM
  • And here is what is happening in code:

    Here is my Managed Metadata keyword list; if you add one more value to this list, the save command will fail:

    1; 10; 100; 101; 102; 103; 104; 105; 106; 107; 108; 109; 11; 110; 111; 112; 113; 114; 115; 116; 117; 118; 12; 13; 14; 15; 16; 17; 18; 19; 199; 2; 20; 200; 201; 202; 203; 204; 205; 206; 207; 208; 209; 21; 210; 211; 212; 213; 214; 215; 216; 217; 218; 219; 22; 220; 221; 222; 223; 224; 225; 226; 227; 228; 229; 23; 230; 231; 232; 233; 234; 235; 236; 237; 238; 239; 24; 240; 241; 242; 243; 244; 246; 247; 248; 25; 250; 251; 252; 253; 255; 256; 257; 258; 259; 26; 260; 261; 262; 263; 264; 265; 266; 267; 268; 269; 27; 270; 271; 272; 273; 274; 275; 276; 277; 278; 279; 28; 280; 281; 282; 283; 284; 285; 286; 289; 29; 290; 291; 292; 293; 294; 295; 297; 298; 299; 3; 30; 300; 31; 32; 33; 34; 36; 37; 38; 39; 4; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 5; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 6; 60; 61; 62; 63; 64; 65; 66; 67; 68; 69; 7; 70; 71; 72; 73; 74; 75; 76; 77; 78; 79; 8;


    http://sharepoint.nauplius.net


    Sunday, July 22, 2012 5:39 PM
  • And here is a link to the SQL query with ~2100 parameters due to the update of the document.


    http://sharepoint.nauplius.net

    Sunday, July 22, 2012 5:43 PM
  • Thanks Trevor, this is extremely insightful. Any clues on how to get around this limitation... or I am stuck?


    Personal Blog: http://thebitsthatbyte.com

    Monday, July 23, 2012 2:46 AM
  • ... and how does the 2100 parameters equal +/- 250 managed metadata terms?


    Personal Blog: http://thebitsthatbyte.com

    Monday, July 23, 2012 2:49 AM
  • In my case, it was 192 terms; the 193rd introduced too many parameters.  I also had some Enterprise Keywords on there, as well as the other standard document properties.

    For this limitation, you're stuck.  You'd have to submit a Design Change Request to Microsoft to somehow 'bulk load' these Metadata terms into SQL using more than one term per SQL parameter.  Or you'd have to submit a design change for SQL Server to accept >2,100 parameters.  In order to start this process, you'll have to open a PSS case.  Keep in mind that a DCR can take well over 6 months to resolve (I'm still waiting for wording within a TechNet article to change nearly a year later after a DCR was rejected, but the documentation was to be updated to reflect a limitation).


    http://sharepoint.nauplius.net

    • Marked as answer by Kelly Rusk Monday, July 23, 2012 1:18 PM
    Monday, July 23, 2012 12:31 PM
  • Thanks Trevor. I went through this process as well with the Document Set Routing Limit. Hopefully SP 2013 will resolve this. Do you know if SQL 2012 has different capacity limits around parameters?

    Personal Blog: http://thebitsthatbyte.com

    Monday, July 23, 2012 1:17 PM
  • The parameter capacity I quoted is from SQL 2012.

    http://sharepoint.nauplius.net

    Monday, July 23, 2012 1:18 PM
  • Is this still a limit for SharePoint 2013? what about SharePoint Online? 2016?

    Alex Talarico

    Thursday, December 3, 2015 9:42 PM
  • This is a SQL imitation, not a SharePoint one.

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, December 4, 2015 5:10 PM