Stored Procedure and view does not show up in db explorer tree


I am using DataGrip 2018.3 to access a SS 2017 database.

There is 1 view and 1 stored procedure I noticed that do not show in DG but exist ( and can be viewed in SSMS).

I've tried "Sync" from the toolbar and File menus.

I've also tried to "Invalidate and Restart".

None of these help. 

This rather annoying and raises my suspicions that what DG is provided me may not be 100%  accurate or reliable.

The workaround is to use SSMS which *is* 100% accurate and reliable.


Is there a fix for this problem?






Hi! Does Forget Chached Schemas and then Sync helps? 

ÐаÑÑинки по запÑоÑÑ datagrip forget cached schemas


I ran into this too


Alan, a screenshot please


Let me rephrase:  I had a similar experience wherein I did not see stored procs in the DB tree view.  I then found this thread which suggested "Forget Cached Schema" and that worked to fix the issue for me.  So I do not consider this a bug or issue, just a minor nuisance. So I no longer have the screenshot.


Anyway, it's not ok. What database it was?


bruce radtke,

Is it possible for to update DataGrip to 2020.1 and try to reproduce your issue?


Alan Berezin1,

Could you specify DataGrip version you work with?


It was a sqlserver2019 database and I was on the DataGrip version just previous to 2020.1 at the time.  I have since upgraded to 2020.1 .  I haven't seen the problem but I have serious doubts as to how I could repro it.  I will definitely report it in this thread if I see it again.


I use oracle in Datagrip, and not show procedure too


Please follow the troubleshooting guide at
Does it help?
If no, please share the screenshot of "Test Connection" result like that:
And chosen schemas to introspect here:


Every time I start to get momentum in using dg I run into this sort of garbage.

I HATE ssms, its awful, archaic, stupid and its keystrokes are unintuitive and dumb.


Its ALWAYS correct and accurate with the actual state of a db.

I deactivated, re-activated, refreshed, refreshed selected,, about to try the forget cache “fix”, but this is just useless if it requires us to do the equivalent of invalidating caches and restarting to get idea to see a file change in a wsl ubuntu install. A tool stops being useful if i have to defrag it every time i use it just to make sure i'm not missing any new objects/changes. 

Same user, db… not sure what else i could have checked.


Ok so pretty dated I guess. in the end I got it top show up after changing the shown schemas from dbo to All. 99% sure the only reason that worked is because it actually checked.

There was no option in menus to forget caches. I presume invalidate caches would have done it, but thats some toxic command.

Datagrip 2023.1, SS 15.0.4335.1




Hi Dave, 

Does it happen only to procedure objects, or are there other database objects involved in the changes not being reflected in the Database Explorer? 

To reflect changes immediately, please ensure you have the Auto synch option checked in your data source properties

I'd also suggest upgrading to DataGrip 2023.2.3 and see if this improves the situation.


Please sign in to leave a comment.