Missing datatypes on MS-SQL schemas in DG 2025.2.3

Hi Scott V.,

Do you have Comments enabled?

If yes, does disabling it help?

 It seems to be on the 2016 servers, the 2022 ones appear to be fine.

Could you share a screenshot for 2022?

Hi! thanks. the ‘Comments’ does toggle the datatypes - however it seems to have no effect on the ones NOT showing any datatype.
 

And after experimenting a little further, I noticed that it does not appear to be related to any specific SQL Server versions (ie, that was just a coincidence) - the one in the example happens to be 2016.  I've fallen back to a previous version of DG, and it works fine - so I'll just use that for now (2024.3.5). Thanks though, I appreciate your answer as I learned about the ‘Comments’ feature :)

(*I've also edited the original question to better shape it and remove unrelated info).

Scott V.,

I've managed to reproduce similar behavior with one of my schemas. Could you try right-clicking the table name and selecting Navigation > Go to DDL? Do you initially see the data types listed as UNKNOWN in the DDL?

In my case, the data types first appear as UNKNOWN, but then the DDL loads correctly, and the data types show up properly in the Database Explorer. However, after performing a Force Refresh, I can no longer reproduce the issue with any schema anymore.

HI Anastasia - tried your suggestion (right-clicking the table name and selecting Navigation > Go to DDL). It generates the DDL, but it still doesn't show anything next to the column names (not even UNKNOWN).  Did the usual, restart DG/Forget cached schemas/Force Refresh, etc…  Weird thing is that It shows the datatypes for the same schema on a different instance of SS configured identically. And it will show for the dbo schema in the same database… just doesn't want to show them for that one schema…  Like I said, everything works fine in DG  2024.3.5 so I can fallback on that for now. It's like it seems to somehow be related to the new introspection feature introduced since that release. Thanks for trying though, I appreciated it :)

It's like it seems to somehow be related to the new introspection feature introduced since that release.

Yes, it can be. At least the mentioned issue with the UNKNOWN data types seems to be related (see DBE-24074).

Regarding your issue, would you be able to share the DDL of one of the problematic tables (the one returned by DataGrip and the original one, e.g., from SSMS or mssql-scripter) so I can try to reproduce the behavior on my end? Additionally, if you could provide the logs from version 2025.2.3, I'll check for any errors or exceptions that may be related:

• idea.0.log file (Help > Show Log in …),
• database.0.log file (Help > Show SQL Log in …).

The idea.0.log file can also be found in the logs directory, and the database.0.log file can be found in the system directory. The files can be privately attached to https://uploads.jetbrains.com; please share the upload ID once done.

Weird thing is that It shows the datatypes for the same schema on a different instance of SS configured identically.

Does duplicating the data source make any difference in how schema data types are displayed?

Hey thanks for bringing this up. If the MS SQL schemas are missing datatypes in DG 2025.2.3, it might be a regression. Two suggestions:

1. Try comparing with an earlier version of DG to confirm whether this bug is new.
2. If possible, capture and share a small reproducible example (schema plus screenshots) on JetBrains issue tracker that often helps the devs pin down what broke.

Anastasia Zhukova uploaded the logs as requested, but wasn't sure where to share the id (in here or email?). 
I duplicated the datasource but the result was the same: dbo shows datatypes, but the ppl schema doesn't.

Matt, thanks for the suggestions; to your first point, everything is working with the fallback version 2024.3.5.  To the second, I didn't want to rush to create a ticket w/o first ruling out stuff on my side ~ haha. Was kinda taking my lead from Anastasia, and see if she feels it is warranted. Like she mentioned above, she was able to repro but then wasn't. 

I had the same issue with datatypes not showing up even after enabling comments.
In Quick Documentation my datatypes also appeared as unknown.

After I tried Navigation > Go to DDL, I disabled and re-enabled comments. Now the datatypes are visible both in the explorer and in Quick Documentation. But I have to do this for every table in my database.

Hi Scott V. ,

uploaded the logs as requested, but wasn't sure where to share the id (in here or email?). 

You can share the id here, as only employees have access to view the uploaded files.

I duplicated the datasource but the result was the same: dbo shows datatypes, but the ppl schema doesn't.

To confirm, using the 3rd Introspection Level with Force Refresh didn't make any difference, right?

Hello, I seem to be having the same problem and for me it's limited to specific schemas as well.

What's even weirder is, when trying to Right Click → Modify Table any table in the affected schema. I get the
“Low Introspection Level for Modify Table” warning. Even after I click “Abort and Introspect this schema” and try to Modify the table again, I get the same warning right away.

When I click Force continue I still don't see the datatypes in the left-side Modify menu, but I can click any column and it shows me the correct datatype

Grabov Robert, 

Does selecting Introspection Level 2 or 3 help in your case?

It doesn't change anything. In my case the affected schemas seem to be “stuck” on Level 2. Even when refreshing the whole database, the affected schemas show “Introspection schema X at level 2” in the bottom right.

Grabov Robert,

Would it be possible to collect and upload the below logs to https://uploads.jetbrains.com and share the upload ID here once done?

1. Generate the diagnostic dataSource*.log as described here, but instead of Step 2. "Run the introspection ..."  run Refresh for the affected schema on the Introspection Level 2. If the introspection gets stuck, please wait for some time before disabling the Diagnostic Mode.
2. Collect the log archive via Help > Collect Logs and Diagnostic Data.

Sure, hope it helps

2025_10_02_oNB3GHFpaGHew6s9daSMw7

Edit: Added the refresh for a schema in the same database that is displayed correctly.

2025_10_02_nsmbHRbgjm1inYczgmSzHT

Thank you. Could you also let me know whether refreshing just one of the tables within the affected schemas is sufficient to retrieve the column types?

No sadly just refreshing the table does nothing. And hiding/showing the schema again doesn't do anything either.

I even tried creating a new connection with the same credentials and that didn't help either.

Hi Anastasia Zhukova!   The logs (database & idea) you requested are uploaded to the JB Server as:
29527663978898-Missing-datatypes-on-MS-SQL-schemas-in-DG-2025-2-3.zip

2025_11_05_zNZff2HEdCZqTWS7p88KCf

using the 3rd Introspection Level with Force Refresh didn't make any difference, right?

correct, it did not.

Thanks, Scott.

Hi,

Could you please check if this issue is still observed for you in 2025.3.1?

For me the issue is fixed.
Right Click → Force Refresh on the affected Data Source after updating to 2025.3.1 dit it.

Thank you for the support and implementation

Keep it up guys, much appreciated!

Grabov Robert, thank you! I’m glad to hear that it’s working for you now.