Read our blogs, tips and tutorials
Try our exercises or test your skills
Watch our tutorial videos or shorts
Take a self-paced course
Read our recent newsletters
License our courseware
Book expert consultancy
Buy our publications
Get help in using our site
435 attributed reviews in the last 3 years
Refreshingly small course sizes
Outstandingly good courseware
Whizzy online classrooms
Wise Owl trainers only (no freelancers)
Almost no cancellations
We have genuine integrity
We invoice after training
Review 30+ years of Wise Owl
View our top 100 clients
Search our website
We also send out useful tips in a monthly email newsletter ...
|
A detailed comparison of PostgreSQL and Microsoft's T-SQL for SSMS Part two of a four-part series of blogs |
|---|
|
Even though Microsoft's SQL Server Management Studio and PostgreSQL use the same underying language (SQL), the user interface and dialects are quite different at times, as this blog explains.
|
In this blog
These are the areas where I've found SQL Server Management Studio to be a better programming environment than PG Admin:
I haven't included in this page any areas in which I think T-SQL outperforms PostgreSQL because ... I haven't found any! In general I prefer the Postgres implementation of SQL, as you'll see if you read on in this series of blogs.
Although there's not that much in it, I do find SSMS easier to use than PG Admin - here are 3 concrete examples of this.
Firstly, Intellisense in SSMS is better than autocompletion in PG Admin:

The list of fields appears much more quickly (and more reliably) in SSMS, and is easier to read (in PG Admin on the right you often have to wait a half-second while the autocompletion loads).
SSMS also allows you to type in parts of a column name to hone in on it in a list (for example you could type dollars to get the two financial fields in the above example). You will miss this if you convert to Postgres!
As a second example, in SSMS you can double-click on an error to take you to the offending line - in PG Admin you can't do this:

As always the error is comma-related here!
And as a third example, SSMS allows you to send output to either a grid, text or a file:

You can do this to some extent in PG Admin, but not in such an obvious way.
Notwithstanding all of the above, the experiences of programming SQL in SSMS and PG Admin are remarkably similar.
There's no equivalent of the SSMS Query Designer in PG Admin:

The Query Designer allows you to see a visual representation of your tables.
Purists will probably say "And a good thing too!", but I'm not a purist! Many delegates on our courses struggle with the syntax of creating joins, so the Query Designer gives them a way to begin their SQL queries easily.
Here's an ERD (Entity Relationship Diagram) in PG Admin:

The diagram can be made to look nice like this, and pleasingly all of the lines join the correct fields!
A database diagram in SSMS, by contrast, initially doesn't look as good as an ERD diagram in PG Admin:

Most irritatingly, the lines don't always seem to link to the correct fields.
However, database diagrams have one huge advantage - they're live:

If you add, edit or delete a line, you're adding, editing or deleting the underlying relationship.
This makes them much more useful!
| Parts of this blog |
|---|
|
Kingsmoor House
Railway Street
GLOSSOP
SK13 2AA
Landmark Offices
99 Bishopsgate
LONDON
EC2M 3XD
Holiday Inn
25 Aytoun Street
MANCHESTER
M1 3AE
© Wise Owl Business Solutions Ltd 2026. All Rights Reserved.