Replication: Error: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In the current row format, the BLOB prefix of 0 bytes is stored inline.
When performing replication to MySQL you can encounter this error: An error occurred while creating table 'Invoice'. Error: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
This error arises because the total size of the columns in a row exceeds 8126 bytes (e.g., VARCHAR(50) + VARCHAR(50) + VARCHAR(100) ...). This is due to multiple fields with variable-length data types.
To resolve this error, consider the following options:
- Convert some columns to TEXT or BLOB. These data types allocate only a few bytes in the row to reference the data stored elsewhere, allowing more columns to fit within the row size limit. Note that this requires server-side configuration changes.
- Increase the row size limit (> 8126 bytes) by modifying relevant server settings, as detailed in the article. Note that this requires server-side configuration changes.
- If feasible, remove unnecessary columns from the table schema to decrease the row size.
The simplest solution is to eliminate non-essential columns, if possible, to avoid server-side modifications.
Related Articles
MySQL: Resolving "Lost connection to MySQL server during query" Error
To resolve the "Lost connection to MySQL server during query" error, please follow the steps below: Go to the Connections page and select your MySQL connection. Click Edit. In the Connection Editor, go to Advanced, then increase or set to 0 the ...
Advantages of the New Replication Runtime Compared to the Old Runtime
The new replication runtime offers several key advantages: • Object-level LastSyncTime, enabling incremental replication for each object • New runtime modes: Standard, Resync, and Resync on Demand • Improved performance by removing direct ID checks ...
Replication creates extra tables in the database
In some cases, as a result of Replication, in addition to the main tables (for example, dbo.Account ), empty additional tables are created in the database with names of the following types: dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52 ...
Replication: Table '...' Schema Validation Failed (Resolving 'Absent Columns' and 'Redundant Columns' Errors)
If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: Error: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...
HubSpot: 414 Request-URI Too Large & 400 Request Header or Cookie Too Large
This error occurs when the object you are querying contains too many custom fields. To resolve this issue for ContactListContacts, Contacts, and Deals objects, enable the Column-wise chunking option in the HubSpot connection editor (located under ...