• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 95 subscribers
  • Views 2448 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How To: Dynamic Business Role Efficiency

ds_walters
over 7 years ago

I've got a question around efficiency of business roles and whether nesting roles might be more efficient from a purely performance perspective.

For example, I have many roles that have similar criteria

Role 1 - Department in (1,2,3,4,5) and Profit Center = 1

Role 2 - Department in (1,2,3,4,5) and Profit Center = 3

Role 3 - Department in (1,2,3,4,5) and Profit Center = 8

 

Would it be better to have each of the roles as above or to create one business role of 'Department in (1,2,3,4,5)' called Department Group and then have

Role 1 - User in 'Department Group' and Profit Center = 1

Role 2 - User in 'Department Group' and Profit Center = 3

Role 3 - User in 'Department Group' and Profit Center = 8

  • 0 over 7 years ago
    Efficiency in regards to performance depends on the number of departments in your in clause, your SQL Server instance, and your data.

    But from an operational perspective, the nesting approach is easier to maintain if you need to change the department condition at some point in time.