The way we are fixing this bug is as follows:
We are trying to keep our authentication mechanism very simple. When a user tries to login and if the user belongs to BUILTIN\Administrator group and the same group exist in SQL Server we will skip to take into account the privileges of this group.
In fact we skip to take into account the privileges of any user or group that belongs to BUILTIN domain.
However if the SQL Server and the user who is logging into the SQL Server exist on the same machine then AdminStudio will consider the roles of users and groups belonging to BUILTIN domain.
What do you think about this?
You can provide me with your feedback at
ambera@installshield.com