Syntax Error on Access Rule Violation detected by database Row Size too large(>8126)

[Supritha3]

Hi,

I have a Status report table under project which has 5 sections under it, each section having two HTML field types.

On entering a large row of texts on the fields I am getting the following error "Syntax Error on Access Rule Violation detected by database Row Size too large(>8126) ".

Also I could observe that if an extra line of text on "path to green"  field is getting me this error removing this extra line from "path to green" field and adding back to "status" field is not getting me this error.

I believe that this is because the texts along with the field size is crossing the allocated size limit on the table.

I did go through the below article which gave me an idea of what is causing the issue,

https://community.servicenow.com/community?id=community_question&sys_id=c6838365dbd8dbc01dcaf3231f9619a3.

I do have certain quires though:

1. What is the threshold limit to get this error.

2. If we don’t change the current table structure what are the other options to remediate this issue.

Thanks,

Supritha F

[Tom Sienkiewicz · Accepted solution]

Hi, basically it looks like you have too many large string or html fields on a single table.

Take a look at the below thread where I and others provide some more info around this 😉

https://community.servicenow.com/community?id=community_question&sys_id=c6838365dbd8dbc01dcaf3231f96...

Hopefully this will help. ServiceNow apparently have an "Offrow storage" offering which might help you if you do not wish to reduce the table/row size.

[Supritha3]

Before I could look up for Offrow storage I want to know how will I be able to check the max length I can assign to a HTML field in order to avoid this error.

Is there any threshold limit set for a table from service now, if so how do I verify?

[Tom Sienkiewicz]

Let me copy my response from the other thread. I don't think there is any calculator for this, I would suggest to open a ticket with SN for your specific case.

"Basically any field you add will use up some space depending on the field size - e.g. string with max. length 40 will be mapped as varchar(40) and will use up exaclty the number of bytes storied in it for each record (max. 40).

If you use true/false - this maps to tinyint(1) and should use only 1 byte of space - but I have to confirm this with SN as I'm not 100% sure.

If you add bigger fields, such as string field >255 length or any HTML-type field, it is a bit more complex. Every such field will use up to 768 bytes of your limit (less if the text in specific field is shorter), and if there is more content, all the remaining data is kept in a BLOB via reference - but you don't have to care how it works as it happens in the DB layer. You only have to know that if you put 10 HTML fields on a table, you are basically screwed as this eats up 7680 bytes potentially."