New answers tagged logins
For me, the solution was that I was using an outdated version of SqlPackage.exe. Old version path: C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\SqlPackage.exe New version path: C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin\SqlPackage.exe It is installed by Microsoft SQL Server Data Tools (SSDT).
Try running this, when in the Database - it will give you the permission levels for SERVER, DATABASE, OBJECTs in 3 separate result windows - you can then consider the Group membership of the user vs the permissions levels (copy/paste results into Excel for easier filtering, etc. (PS. not my code, but very useful - I would reference the original ...
I would check if the users are part of the db_denydatareader role, check for deny permissions on the tables schema, and also for a deny permission on the public role. I would suspect these are the most likely culprits.
Top 50 recent answers are included