I am currently replacing a poorly implemented MSSQL DB structure, by developing a properly structured schema in parallel. The old tables are dbo., and the new tables being moved are Logistics.
While creating the new schema using a third-party DB editor(Beekeeper Studio), I went back to the DB query browser while working on a Transaction Group. And to my horror, all the new tables were appearing with the exact same names as the old, which seems as if it can easily lead to undefined behavior elsewhere in the project. As of current the table info Ignition pulls in the DBQ browser does not show the correct structure for the Logistics. entries either:
dbo.Farms(correct)
Logistics.farms(incorrect)
Logistics.farms(actual, screenshot from beekeeper studio)
The issue I am now facing is whether or not turning on "Include Schema in Table Name" will help to alleviate this issue, from Ignition's standpoint. The fact that it's off by default and considered an "Advanced" setting makes me believe that there are some bad things which can happen if it's enabled carelessly, so I would like a bit more information before proceeding.