It's got cell level TDE if you want which also makes it transparent to the application which makes it pretty easy to implement as you don't need to handle the encryption within your app.

All the key management, split knowledge, key rotation and most importantly access management and a full audit trail are also a "few clicks" away.

Having a turn key solution for one of the most annoying things to implement in a correct manner should not be under-estimated.

Anyone who done any compliance work knows just how many weirdly stitched solutions you can have.

Something along the lines of "we manage split knowledge to our keys by splitting the key and keepass file into 2 files and storing them on USB keys in separate vaults"....

Now technically this can pass a compliance check but this is a pretty darn silly situation simply because there isn't any better solution that works out of the box, this also quite often means that anytime you restart your DB you have an entire process of getting the keys, decrypting the tables copying their content into temporary views, re-encrypting the files and remove the keys from the server..

For MSSQL it wasn't that long ago that you have to do it "by hand" also, usually have a stored procedure that would handle the encryption and have a key which is then encrypted by several KEK's whilst it did afford some split knowledge it wasn't a true m of n which also meant that if you had more than 2 DBA's you had to make sure that the DBA's are know all of the KEK's and not be in a situation where all 3 DBA's that are not off during that week know the exact same password for the KEK...