---
title: "Why does the Uniprint database run in SQL compatibility mode?"
slug: "why-does-the-uniprint-database-run-in-sql-compatibility-mode"
updated: 2024-04-01T07:11:56Z
published: 2024-04-01T07:11:56Z
canonical: "kb.pharos.com/why-does-the-uniprint-database-run-in-sql-compatibility-mode"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why does the Uniprint database run in SQL compatibility mode?

Why does the Uniprint database need to run in SQL Server compatibility mode?

---

Uniprint runs in compatibility mode of the lowest SQL Server version that we support. There are slight nuances in how different versions of SQL Server handle our stored procedures

Uniprint 7.x supports SQL databases down to the SQL version 7.0 (compatibility mode 70).

  

Uniprint 8.x supports SQL databases back to SQL 2000 (compatibility mode 80).

Uniprint 8.x supports SQL databases back to SQL 2000 (compatibility mode 80).

## Related

- [How to manually upgrade a Pharos Uniprint Database](/how-to-manually-upgrade-a-pharos-uniprint-database.md)
- [Uniprint Suite - Rundll32 Printui Error: Operation could not completed](/uniprint-suite-rundll32-printui-error-operation-could-not-completed.md)
- [When Will Your Database Run Out Of Space?](/when-will-your-database-run-out-of-space.md)