# 8.1 to 8.3 Database Query Browser different behavor with SQL Server schema tables, columns issue

**URL:** <https://forum.inductiveautomation.com/t/8-1-to-8-3-database-query-browser-different-behavor-with-sql-server-schema-tables-columns-issue/115180>\
**Category:** Ignition\
**Tags:** ignition83, designer, ignition81\
**Created:** [April 21, 2026, 1:35pm UTC](https://forum.inductiveautomation.com/t/8-1-to-8-3-database-query-browser-different-behavor-with-sql-server-schema-tables-columns-issue/115180 "2026-04-21T13:35:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [April 21, 2026, 1:35pm UTC](https://forum.inductiveautomation.com/t/8-1-to-8-3-database-query-browser-different-behavor-with-sql-server-schema-tables-columns-issue/115180/1 "2026-04-21T13:35:15Z")

</div>

Between 8.1 and 8.3 behavior was changed with the database query browser with how it sees tables from sql server. In the database I am working on there are many schemas with similar structure, and though it never showed the schema, it did show a table per schema like so -

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/6/06cfbf23d6aa093e91e37df90165502a04a22de4.png)

Now in 8.3 it only shows one table name across all the schemas -

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/6/c6aa0ad5aa60b5915aa2d76cb60a62d312058876.png)

For **both** 8.1 and 8.3 you open it up the columns are mangled - it seems like a column per table per schema

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/5/05f26dd8f43a1c6a96f723b99bd884f895bef309.png)

Would be nice if this was fixed as a small quality of life improvement if possible

I know the schema in sql server doesn't generalize to all databases so I can live with not having that listed, but i do think each table should only show its own columns, not a copy of each column per schema.table that shares the same name.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 21, 2026, 3:53pm UTC](https://forum.inductiveautomation.com/t/8-1-to-8-3-database-query-browser-different-behavor-with-sql-server-schema-tables-columns-issue/115180/2 "2026-04-21T15:53:12Z")

</div>

Can you send this in to support?

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [April 21, 2026, 4:11pm UTC](https://forum.inductiveautomation.com/t/8-1-to-8-3-database-query-browser-different-behavor-with-sql-server-schema-tables-columns-issue/115180/3 "2026-04-21T16:11:05Z")

</div>

Just emailed it in.

Ticket 184473

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [May 1, 2026, 6:34pm UTC](https://forum.inductiveautomation.com/t/8-1-to-8-3-database-query-browser-different-behavor-with-sql-server-schema-tables-columns-issue/115180/4 "2026-05-01T18:34:13Z")

</div>

When configuring a database connection under SQL Compatibilty there is this checkbox

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/2/12c11884ec6ca838b0c39d8e80bb4d74372380f8.png)

Selecting True fixed the issue for me in 8.3 I then saw SchemaName.TableName and the columns were correctly listed. Did not test in my 8.1 prod live but I assume it will work there too.