Database Studios Some Criticism

Many of database studios like MySQL Workbench, Devart dbForge Studio for MySQL and  JetBrains DataGrip provides very strange and limited support of SQL files. The only thing you can do with SQL file is run it and see some results, most often limited number of rows.

But it is very strange functionality.

If SQL query returns million of rows, there is no sense to show 1000 of them. If SQL query modifies some table, there is no sence to keep it opened.

From my experience, SQL queries are always parts of some manual or automated procedures, i.e. organized in sequences or trees. So, I would like is SQL studio software provide some sort of “schema” or any other type of organization chart for SQL files.

It can be something like this:

example-of-sql-dependencies

(drawn in EA)

BTW, dbForge has very nice “dependency” feature for server side objects:

dbforge-dependency-feature

Would like something close to development-machine-sided SQL files.

One thought on “Database Studios Some Criticism

  1. dbForge Studio for MySQL is a very cool tool for MySQL management, administration and development. I recommend it to you.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s