Lowell (8/27/2013)
I suspect the core issue is that everyone logged in has sysadmin or dbo priviledges and instead of fixing that as gail implied with proper security, you are looking for a bandaid approach to limit by ip address.If you fix your security model by creating roles with the expected permissions, you gain twofold : a better security model and directly addressi g the overpriviledges problem while still fixing the problem itself
Actually 10 users are using a common User name & password to access the Application.. means all ten 10 users do DML operations on one application & we came across a scenario where some records were deleted from tables but god know who did that.. obviously that was the common Login ID used..
Its a client need..
Client wants 10 users to use same Login ID but wants to know who did what incase of issue, like who deletes who makes updates & also wants that their should be no impact on server if we go ahaead & do some additional implementation on restrictions :w00t: :w00t::w00t:
I am puzzled, my boss is puzzled :w00t: & team members are also puzzled :w00t:
************************************
Every Dog has a Tail !!!!! :-D