As someone that uses PostgreSQL, would you care to elaborate on the topic? I haven't used MS SQL Server so maybe if you can actually provide some useful information we can start a discussion and learn something new.
I think many IT departments choose MSSQL for the same reason they choose Windows - it's an easy to setup system with good tools and lots of commercial support. MSSQL also integrates very tightly with Windows and you can use single-sign-on via Windows authentication with no setup.
The administration GUI included with SQL Server (called SQL Server Management Studio/SSMS) is very robust and whenever I look, I always see other people asking around for something as good as SSMS for other RDBMS. If you use Unix you might prefer your command line tools, but a lot folks would rather obviously use a GUI.
For developers, I haven't found anything better than SQL Server Data Tools (SSDT) which is a set of extensions for Visual Studio that let you design and develop a SQL Server database. It creates version migration scripts, diffs database schemas and data, integrates with git and other source control providers and generates DML scripts among other things.
The administration GUI included with SQL Server (called SQL Server Management Studio/SSMS) is very robust and whenever I look, I always see other people asking around for something as good as SSMS for other RDBMS. If you use Unix you might prefer your command line tools, but a lot folks would rather obviously use a GUI.
For developers, I haven't found anything better than SQL Server Data Tools (SSDT) which is a set of extensions for Visual Studio that let you design and develop a SQL Server database. It creates version migration scripts, diffs database schemas and data, integrates with git and other source control providers and generates DML scripts among other things.