{"id":134,"date":"2017-05-02T08:03:41","date_gmt":"2017-05-02T08:03:41","guid":{"rendered":"http:\/\/www.yohz.com\/blogs\/?p=134"},"modified":"2018-11-01T07:53:37","modified_gmt":"2018-11-01T07:53:37","slug":"why-use-sql-multi-select-in-addition-to-pgadmin-4","status":"publish","type":"post","link":"https:\/\/www.yohz.com\/blogs\/2017\/05\/02\/why-use-sql-multi-select-in-addition-to-pgadmin-4\/","title":{"rendered":"Why use SQL Multi Select in addition to pgAdmin 4"},"content":{"rendered":"

Let me start by saying pgAdmin 4 is a great tool for PostgreSQL. \u00a0It makes a lot of the admin and monitoring work easier. \u00a0It’s also cross-platform, and it’s free. \u00a0On the other hand, SQL Multi Select<\/a> is just a query tool, that runs only on Windows. \u00a0Well, it runs on Ubuntu using Wine<\/a>, and on Fedora via PlayOnLinux. \u00a0 \u00a0The Basic Edition<\/a> is free, and here are some reasons you may want to use SQL Multi Select<\/a>\u00a0as your PostgreSQL query tool instead of pgAdmin. \u00a0Note that pgAdmin 4 (1.4) was used for this comparison.<\/p>\n

Multiple server targets<\/strong><\/p>\n

You can run queries on multiple PostgreSQL databases simultaneously with SQL Multi Select. \u00a0For example, say you want to run a script that returns every databases’ size. \u00a0Just set up a group containing the databases you want to run the query on:<\/p>\n

\"\"<\/p>\n

Set up the scripts on run on each of those databases:<\/p>\n

\"\"<\/p>\n

Run the script, and you’ll see the results for each of those databases, across all servers in the server group.<\/p>\n

\"\"<\/p>\n

Multiple result sets<\/strong><\/p>\n

When you run the following in pgAdmin:<\/p>\n

\"\"<\/p>\n

only the last result set is returned.<\/p>\n

\"\"<\/p>\n

In SQL Multi Select, the same script returns multiple result sets.<\/p>\n

\"\"<\/p>\n

To make things clearer, you can place comments before each individual script:<\/span><\/p>\n

\"\"<\/p>\n

and SQL Multi Select will use those comments to identify the result sets instead of arbitrary numbers.<\/p>\n

\"\"<\/p>\n

Image display<\/strong><\/p>\n

In bytea columns storing images, pgAdmin displays the hex values.<\/p>\n

\"\"<\/p>\n

SQL Multi Select displays a thumbnail of the image (gif, jpeg, png, bmp, dicom), and some image properties. \u00a0Note that SQL Multi Select inspects the bytea values and identifies the image format automatically. \u00a0There is no need to provide another column that tells SQL Multi Select the image format.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Blob data identification<\/strong><\/p>\n

In bytea columns containing files, pgAdmin displays the hex values.<\/p>\n

\"\"<\/p>\n

SQL Multi Select displays details of the data contained in those columns. \u00a0Note that SQL Multi Select inspects the bytea values and identifies the data type accordingly.<\/p>\n

\"\"<\/p>\n

Result sets containing bytea columns return very slow<\/strong><\/p>\n

If your query returns bytea columns a few MBs in size, pgAdmin takes an extremely long time to return the result set when compared to SQL Multi Select. \u00a0For e.g. this query returns a single bytea column that contains a 13 Mb zip file. \u00a0pgAdmin takes 7 minutes to display the single row:<\/p>\n

\"\"<\/p>\n

SQL Multi Select returns the same result set in 1 second.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Search function<\/strong><\/p>\n

In SQL Multi Select, you can search for a value in the result sets. \u00a0You can also use a regular expression to search for values.<\/p>\n

\"\"<\/p>\n

pgAdmin is still great for administrative tasks, but as a query tool, SQL Multi Select<\/a> may be better in some cases. \u00a0Download<\/a> SQL Multi Select and give it a try now. \u00a0The 14-day trial will be automatically converted to the FREE Basic Edition<\/a> once the trial period has elapsed.<\/p>\n

Related blogs:<\/p>\n