MSSQL Invalid layer

[qgib]

Author Name: Zannis Kostalas (Zannis Kostalas)
Original Redmine Issue: 20607
Affected QGIS version: 3.4.1
Redmine category:data_provider/mssql

---

The case:
On the same server, created an exact copy of a polygon table on a different db
SELECT * INTO db2.dbo.geom_table_copy FROM db1.dbo.geom_table

While QGIS was reading the original table normally, when attempting to insert the copied table I would get
"WARNING dbname='db2' host=www.myhost.com user='user' password='pwd' srid=4326 type=Polygon disableInvalidGeometryHandling='0' table="dbo"."geom_table_copy" (POLYGON) sql= is an invalid layer - not loaded"

The problem got solved when I populated the "sql" field on the table selection with a random, valid query, loaded the table and then deleted the query. As it seems, for some reason, when creating the connection to the 2nd db, that field, enev though appearing blank, was populated in the background with an invalid expression (that's my best guess at least)

Once you know how to fix it it's easy but this was bugging me for close to 6 months now and no solution exists on the internet

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Does it works as expected on 2.18?

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Zannis Kostalas (Zannis Kostalas)

---

Giovanni Manghi wrote:

Does it works as expected on 2.18?

QGIS 2.18.15 loads the layers properly

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• regression was changed from 0 to 1
• priority_id was changed from Normal to High
• status_id was changed from Feedback to Open

[alexbruy]

Is this still an issue with latest master?

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.