SQL Server Access Restriction

  • Comments posted to this topic are about the item SQL Server Access Restriction

    /* ----------------------------- */
    Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!

  • Thanks for this. I really learnt something new here.

    BTW, I love the URLs in the comments (do the same thing myself) as it is a great way to document something which is really documented elsewhere.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • How well does this scale? If I have thousands of users hitting the server...

    If I'm right, the scale issue will very often not be picked up during testing but only appear when it is released to the production environment.

  • As for scaling, I am not sure how well it would handle thousands of logins per second. My best advice would be to add at the begining of the trigger a exit clause that covers 90% of the cases, i.e.

    1) the sql server service account logging from the local server

    2) the application service service account where HostName in (list of app servers)

    3) and/or ApplicationName = '<Application Name>'

    4) any member of the sa role (perhaps hardcoding the members of your dba team)

    /* ----------------------------- */
    Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!

  • Really, really, really good!

    Thanks Greg.

    Tom Garth
    Vertical Solutions[/url]

    "There are three kinds of men. The one that learns by reading. The few who learn by observation. The rest of them have to pee on the electric fence for themselves." -- Will Rogers
  • Thanks a lot Greg. This script is really helpful.

    Correct me If I am wrong.

    My situation is I want to restrict group of accounts which can login from some applications but not from SSMS / Excel / DBArtisan / .....

    As suggested by you the sql service account can be added to the [BlackList] with [RestrictionEnabled] to zero to avoid rollback right ?

    Please Advise.

    Thanks & Regards,

    Srini

  • srinivasreddy4uhyd (3/11/2010)


    Thanks a lot Greg. This script is really helpful.

    Correct me If I am wrong.

    My situation is I want to restrict group of accounts which can login from some applications but not from SSMS / Excel / DBArtisan / .....

    As suggested by you the sql service account can be added to the [BlackList] with [RestrictionEnabled] to zero to avoid rollback right ?

    Please Advise.

    Thanks & Regards,

    Srini

    Section #6 of the Trigger covers this scenario:

    ????--#6

    ????--If a particular application connects to SQL Server, with a given UserName (i.e. service account cannot connect with SSMS)

    ????If(Exists(Select * from SQL_Audit.dbo.BlackList where AppName = @AppName and LoginName = @User and RestrictionEnabled = 1))

    To set it up, insert to the blacklist table

    User and application

    Each user and application requires a seperate entry, i.e.

    user1, Excel

    user1, Access

    user1, Toad

    user2, Excel

    user2, Access

    user2, Toad

    So update the table with each developer login and the application that cannot be used.

    Alternatively, you could add a condition at the begining of the trigger:

    If ((@User in ('User1', User2', 'User3')) and (@AppName in ('Excel', Access', 'TOAD')))

    Begin

    Rollback

    ??insert into SQL_Audit..Violations

    ????????????????(PostDate, LoginName, IPAddress, HostName, ServerName, AppName, ViolationType)

    ????????????????values (@PostTime, @User, @IPAddress, @HostName, @SrvName, @AppName, 'ApplicationName')

    Return;

    End

    The advantage of the second method is that the hardcoded values require less disk IO to process; however, the disadvantage is that the SP would have to be recreated to every change in Users and apps.

    /* ----------------------------- */
    Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!

  • Hi,

    while using this script I had created sql_audit database but not able to create trigger getting following error while running provided scrip

    Msg 156, Level 15, State 1, Procedure trg_LoginBlackList, Line 5

    Incorrect syntax near the keyword 'as'.

    Msg 1088, Level 16, State 119, Line 2

    Cannot find the object "trg_LoginBlackList" because it does not exist or you do not have permissions.

    Please revert ..........

  • any one plz help on this

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply