Unanswered

Help: Maximum allowable table row size of 8060 bytes error

(0) Share

Report

Posted on by Nerd_Gorilla1

When importing my Power Pages solution from dev to test I'm getting:

Error code 8004801E. Import failed: Creating or altering table 'msgov_ApplicationBase' failed because the minimum row size would be 9046, including 1725 bytes of internal overhead. This exceeds the maximum allowable table row size of 8060 bytes.

It seems my table is too large? I've never had issues before, but it seems like I need to trim down my table. I have a few questions:

How come there is no warning in my dev environment that I've exceeded my row size? Can I check this somehow?
My DB is mostly empty now. What type of impact will actual data have on row size?
Is there any quick permeant solution where I don'y have to make major modifications to my schema?
If no to above, are there any "bandaid" type recommendations that I could use until I'm able to split up my table

I would be extremely grateful for any advice you can offer. Thank you in advance.

Categories:

Microsoft Dataverse with Power Apps

All responses (5)

Answers (0)

Sort by

AhmedSalih

6,680 Moderator on at

Like (0)

Report

Copy link

Link copied!

Hello @Nerd_Gorilla1, The error message you're encountering in is related to SQL Server, not Power Pages directly (Dataverse backend Database is SQL). It means that the size of a row in a table has exceeded the maximum allowed size of 8060 bytes. In SQL Server, each row can only store up to 8060 bytes of data, excluding certain data types like text, ntext, image, varchar(max), nvarchar(max), and varbinary(max).

My question is what type of data you are saving in your rows? and also, is this table "msgov_ApplicationBase" a system table?

If my reply helped you, please give a 👍 , & if it solved your issue, please give a 👍 & Accept it as the Solution to help other community members find it more.

I am primarily available on weekdays from 6-10 PM CT and 5-10 PM CT on weekends.

Visit my Blog: www.powerplatformplace.com

Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos

New Project.png

Nerd_Gorilla1 31 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @AhmedSalih ,

I understand the warning but what are my options? Is the only solution to reduce the number of columns?

I could split off some of my column into another table, but dataverse does not make it easy to create 1:1 relationships which is what I would need for my scenario.
AhmedSalih 6,680 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@Nerd_Gorilla1, yes, that is the only option is to normalize the schema.
joe12 2 on at

Like
a
(0)

Report
Copy link

Link copied!

@AhmedSalih I've removed over a hundred columns and even cleared some relationships and I'm still getting the error. What's strange is I just did an upgrade last week when I had many more columns and it was succesful. I've also noticed the bytes are going up not down after deletion. How?? Here is the error after my last import attempt:

Import failed: Creating or altering table 'msgov_ApplicationBase' failed because the minimum row size would be 9977, including 1949 bytes of internal overhead. This exceeds the maximum allowable table row size of 8060 bytes

Any other ideas or suggestions?
Nerd_Gorilla1 31 on at

Like
a
(0)

Report
Copy link

Link copied!

@AhmedSalih I've removed over a hundred columns and even cleared some relationships and I'm still getting the error. What's strange is I just did an upgrade last week when I had many more columns and it was succesful. I've also noticed the bytes are going up not down after deletion. How?? Here is the error after my last import attempt:

Import failed: Creating or altering table 'msgov_ApplicationBase' failed because the minimum row size would be 9977, including 1949 bytes of internal overhead. This exceeds the maximum allowable table row size of 8060 bytes

Any other ideas or suggestions?