SQLPro for Oracle User Reviews

Top reviews

My Favorite SQL Tool for Oracle

This tool used to be rolled into the general SQLPro Studio before M1 Macs came along. I used it then too. It’s my goto SQL tool. The interface is pleasing and intuitive as well as customizable. It lets you save “Favorites” for commonly used queries and allows for SSH tunneling which I needed for a number of years. The developer is responsive and the price is reasonable. I’ve found SQLDeveloper to be too buggy for my needs though I do bounce over to it when I have a difficult query to troubleshoot. Unfortunately the SQLPro Studio apps don’t give precise error location. The error is always reported on “line 1” where SQLDeveloper pinpoints it for you. Other than that I much prefer working in SQLPro Studio and this “for Oracle” Apple Silicon version.
Show more

Not great

Yeah, this really isn’t great. A pro is the good UI design and nonclunky specification of connection parameters - and I also own the Postgres version of SQL Pro, which works fine.

The negative I ahve found so far is a huge one. It will not connect to my database. At all.

I have downloaded two free competitors to this - Oracle’s own SQL Developer, and the free-for-trial SQL Razor. Both connect just fine using exactly the same configuration parameters.

These are the days of the $0.99 download, so $6.99 sets expectations - and sadly this software does not live up to them.
Show more

Doesn’t support many Oracle functions….

You can’t use describe, you can’t prompt for variable entries… Good light-weight client for basic level SQL, but it’s missing many of the feature I take for granted in Toad, SQL Developer and even sqlplus.

works perfectly

I downloaded it, gave it my creds for my server and was able to start work immediately. great tool and well worth the few dollars they charge if you develop with an oracle database

Error reporting needs work

Clean interface and is functional for light-weight work; however, error messages seem to always map to the first line of the query which makes it difficult for debugging larger queries.