Primentra vs SQL Spreads

Pricing

What you actually pay

Feature comparison

Primentra vs SQL Spreads — what each platform covers

In depth

How Primentra and SQL Spreads differ once you get past the feature list.

What SQL Spreads does

SQL Spreads is an add-in for desktop Excel on Windows. A Designer picks a SQL Server table, decides which columns show and which are read-only, and hands the workbook to Data Editors. They edit rows in Excel and save straight back to the table. There is no server to install. The add-in talks to the database directly, under each user's own SQL Server or Windows sign-in, or Entra ID on the Pro plan and up.

It does more than plain write-back. SQL Spreads checks each entry against the column's data type as you type it. The Pro plan adds lookups, which show a name where the table holds a key, and change tracking, which writes who changed a row and when into columns you choose. Premium adds conflict detection, which warns you before you overwrite a row somebody else saved after you loaded it. Post-save SQL scripts can clean or validate data once it lands.

Where the data lives

This difference decides most cases. SQL Spreads edits the tables you already have. Point it at an ERP setup table or a forecast table, and people edit that table in place the same afternoon.

Primentra keeps master data in its own model, made of the entities, attributes and domain references you build in the app. Other systems read it through integration views, which are real SQL views, through staging tables, or through the REST API. You get one governed copy that every system reads. You do not get an editor for a table that another application owns.

Who checks a change before it is saved

In SQL Spreads, the check is the column's data type plus whatever your SQL scripts do after the save. Their features page and documentation list no approval step in which a second person signs off before SQL Spreads writes the change.

In Primentra, a change first runs through the business rules you build in the UI: a required field, a format, an IF/THEN condition. On an entity with an approval workflow, the change then waits as a proposal until an approver accepts it. The record stays as it was until then.

What the audit trail holds

SQL Spreads change tracking stores a user name and a timestamp on each row. For the full history of a row, their documentation points you to SQL Server temporal tables, which you set up yourself.

Primentra records every save. The audit panel on a row lists each change with the user, the time, the comment typed at save, and every changed field as old value and new value. When an auditor asks what a cost center code was in March, you open the row and read it.

Ask for a feature, and follow it in public

When you need something Primentra does not do yet, you file it on our public tracker, and you can follow it there from request to release. Two recent examples:

• On 2 August 2026 a customer asked for the code of a referenced entity in a flat integration view. Version 1.2026.8.2 added that code next to the internal row id, and issue #6 closed the same day.
• On 6 August 2026 a customer asked to filter the grid on a date, and on a whole month at once. Version 1.2026.8.6 added a date filter that lists the years and months in the column, and issue #8 closed the same day.

Bigger requests take longer. Every request and our answer stay on the public tracker with their dates, and every release is in the changelog.

Where these facts come from

We took every SQL Spreads fact on this page from sqlspreads.com on 17 October 2026: the home page, the features page, the pricing page, the FAQ, the Replace MDS page, and in their documentation the pages on change tracking, supported databases and purchases, plus the documentation index. Products change. If something here is out of date, tell us and we will correct it.

Which one is right for you?

Frequently asked questions