Here is the back story. A developer created an EXE program. The exe program has the ability to access a SQL Servre database. In order to do that we create an Active Directory group. Let's call this group
AppAdmin. The EXE program use windows integrated security to connect to the SQL Server database.
In order to use this EXE program, the user must belong to the
APPAdmin group. The
AppAdmin group then now set the membership as
DB_Owner for the database. This setup has been like this for a few years. and it is running fine. The user is only limited to what the EXE program can do.
Now here is the complication. One user one day decided to install SQL Server Management Studio Express. Let's call this guy JOE. and JOE is a member of
Now I am assigned to find away to protect the database from JOE breaking it using SQL Server Management Studio.
I am wondering if there is a way to restrict JOE when he is connecting using SQL Server Management Studio?
What are you suggestion ??
Changing this EXE program seems to be out of the question because it is big and I might break it if I start changing how the EXE program connect to the SQL Server database