Prevent Unauthorized Index Modifications – SQL in Sixty Seconds #183

Prevent Unauthorized Index Modifications - SQL in Sixty Seconds #183 183-DatabaseTrigger-yt-800x450 Earlier I have two blog posts on the database trigger and I have received lots of questions and comments on them. Here are the blog posts: SQL SERVER – Prevent Users from Changing Index and SQL SERVER – Trigger on Database to Prevent Table Creation. Many people asked me to create a video on the same topic, so we have Prevent Unauthorized Index Modifications.

Here is the video from SQL in Sixty Seconds series.

If you are going to say that I should have created a user role or application role (to prevent unauthorized index modification) with the right amount of permissions, I totally agree with you. However, this solution was chosen by my client and they find it very easy to implement. If you have ever worked with me before on Comprehensive Database Performance Health Check, you would know that I do not like triggers.

Here are my few recent videos and I would like to know what is your feedback about them.

Reference: Pinal Dave (http://blog.SQLAuthority.com)

SQL in Sixty Seconds, SQL Scripts, SQL Server, SQL Trigger
Previous Post
MAX Columns Ever Existed in Table – SQL in Sixty Seconds #182
Next Post
Generate Script of SQL Server Objects – SQL in Sixty Seconds #184

Related Posts

2 Comments. Leave new

  • I hope, this will restrict all user to create index, so how can we create an index if really required. do we need to delete this trigger?

    Reply
    • Yes, you will need to disable or delete the trigger.

      As I mentioned, It would be best to create a security role.

      Reply

Leave a Reply

Menu
Exit mobile version