Is it possible to register an entire server? or just DB by DB

Hello Damian,

In the connection url string to the server with multiply databases, please omit specific database name. Then please select needed databases and schemas in Shemas tab https://www.jetbrains.com/datagrip/help/data-sources-and-drivers-dialog.html#schemasAndTablesTab of the created Datasource (please note do not select them using asterisk, as currently there is an issue with it: https://youtrack.jetbrains.com/issue/DBE-2061 ).

Perfect, worked as you said

Im not sure if i should raise another thread for this but im having trouble getting the object filter to work at the bottom of the schemas tab
i want to filter out everything except databasename.dbo
the background to this is that the databases im looking at all have 14 schemas (this is sqlserver). So some servers have 10-15 databases on them, each with 14-15 schemas it would be great if i could get the filter to work based on the regex .*dbo
cheers

It works for me:


Could you attach similar screenshot with your settings?

You are right it does.
I was expecting the Dialog to filter in place where you see the list of all the avaliable schemas. i didnt check back on the main UI.
Many thanks to you all
Happy Christmas

It doesn't work using PostgreSQL.

Could you please specify what does not work exactly for you: multiply databases displaying or Schems object filtering?

Please ensure to run Synchronize action for the datasource after checking the needed schemas. If issue remains, could you please attach output from Test Connection button for the datasource and similar  screenshots of Database Tool Window,  Schemas and General tabs and idea.log . Thanks.

Registering multiple databases doesn't work.

Filtering schemas of a single database works fine.

Sorry, I can not open the images. Could you please re-attache them. Also could you please invoke Synchronize action for the datasource and attach idea.log after this? Thanks.

Upon further inspection it half does what i was hoping it would do. ( clearly i didnt check correctly on christmas eve, other things on the mind, cant think what...)
As i said it does filter the databases as expected in the main UI, but once filtered none of the tables or views show in the main UI only the dbo shema with a tables folder under them (which is empty).

my screen shots look exactly the same as Andrey Dernov post on the 22nd. Notice that there are no tables visible and no arrow to show you can expand the tables either


test connection reveiled this:
Database: Microsoft SQL Server/12.00.2000
Driver name: Microsoft JDBC Driver 4.0 for SQL Server
Driver version: 4.0.2206.100
JDBC version: 4.0
Case sensitivity: MIXED (quoted: MIXED)
Connection successful

this is the last set of logs from the log file:
2015-12-29 09:56:02,698 [2377952]   INFO - ution.rmi.RemoteProcessSupport - "C:\Program Files (x86)\JetBrains\DataGrip 1.0\jre\jre\bin\java" -Djava.net.preferIPv4Stack=true -Ddomain.auth.library=/x86/sqljdbc_auth.dll -Dfile.encoding=UTF-8 -classpath "C:\Program Files (x86)\JetBrains\DataGrip 1.0\lib\util.jar;C:\Program Files (x86)\JetBrains\DataGrip 1.0\lib\trove4j.jar;C:\Program Files (x86)\JetBrains\DataGrip 1.0\lib\groovy-all-2.3.9.jar;C:\Program Files (x86)\JetBrains\DataGrip 1.0\lib\jdbc-console.jar;C:\Program Files (x86)\JetBrains\DataGrip 1.0\lib\dekaf-single-2.0.0.228.jar;C:\Users\damian\.DataGrip10\config\jdbc-drivers\sqlserver-driver-license.txt;C:\Users\damian\.DataGrip10\config\jdbc-drivers\sqlserver-win-auth.jar;C:\Users\damian\.DataGrip10\config\jdbc-drivers\sqljdbc4-4.0.2206.100.jar" com.intellij.database.remote.RemoteJdbcServer com.microsoft.sqlserver.jdbc.SQLServerDriver
2015-12-29 09:56:03,034 [2378288]   INFO - ution.rmi.RemoteProcessSupport - Port/ID: 38320/RemoteDriverImplb850af7b
2015-12-29 09:56:03,091 [2378345]   INFO - ase.dataSource.LocalDataSource - Connecting to: jdbc:sqlserver://vs-uktest01:1433
2015-12-29 09:56:03,573 [2378827]   INFO - ution.rmi.RemoteProcessSupport - Terminating: 38320/RemoteDriverImplb850af7b
2015-12-29 09:56:03,599 [2378853]   INFO - ution.rmi.RemoteProcessSupport - Process finished with exit code -1

i want to filter out everything except databasename.dbo

It looks, currently the object filter does not work well for filtering both database schemas and object names. It is supposed that you filter database/schema using Schemas tab and then use this filter for filtering database objects in Database tool window. I've created the https://youtrack.jetbrains.com/issue/DBE-2105 for this. Please follow for progress in YouTrack.

Thanks thats great
do we need to link back to this thread for some more context?

As requested.

Thanks! It looks like there is a bug. Created the https://youtrack.jetbrains.com/issue/DBE-2109 for this, please follow. Please try workaround mentioned in the issue (with specifying different database name).

I've added the link to this thread in YouTrack in the internal comment for the developers. Thanks for your concern.

Thanks, Andrey, you solved my problem.

I'm coming to DataGrip from Navicat. Of course, I started with my local server, and immediately hit a wall. I frequently download the live database from my server to local, and therefore have dozens of DBs. I expected that I could view them all once I put in my connection info, but I had to find this thread (and then find the schema tab... I had already closed the connection dialog and was looking for schema from the database view).

To start with, not showing all the DBs will cause people to give up on DataGrip before giving it a real try. Additionally, I will need an "extra step" (adding the DB) every time I grab a new version from the server... something that's not necessary in Navicat.

I would suggest that all DBs be shown by default... should I open an issue for this?

The IDEA of DataGrip is great... looking forward to see how it compares with NaviCat.

Thanks,
Ed Eichman
Cambrils, Spain

Hello Edward,

Thank you very much for sharing the experience. I've forwarded your feedback the the team. Not sure that enabling all databases and schemas by default will be a good idea as it could lead to a long synchronisation time especially for very big databases. But indeed some enhancement could be made here.