Having views in DB vs Data manipulation in Expression rules - What approach is best in terms of Performance?

Certified Lead Developer
Consider simple scenario: I have joining date of an employee in DB, want to find out experience. We can achieve in two ways : 1. Writing a view with DB specific functions to find the date difference 2. Manipulating in Expression rules using Appian functions.
Which approach is best practice/improves performance? and strictly speaking When to go for DB views?
Any suggestions?..

OriginalPostID-241280

  Discussion posts and replies are publicly visible

Parents
  • @Ramanjaneyulu ..
    Hi

    As said above .. for the simple scenario which you have mentioned a view might not be required

    Afaik , in my opinion

    Using a view would be helpful when you don't want all columns but instead want only some columns data from many tables and need to show them in as single entity.

    In that case i feel that instead of using expression language using a view would be better as it reduces load on the system and can acheived quite easily and effectively in the back-end itself.

    Please correct me if im wrong
Reply
  • @Ramanjaneyulu ..
    Hi

    As said above .. for the simple scenario which you have mentioned a view might not be required

    Afaik , in my opinion

    Using a view would be helpful when you don't want all columns but instead want only some columns data from many tables and need to show them in as single entity.

    In that case i feel that instead of using expression language using a view would be better as it reduces load on the system and can acheived quite easily and effectively in the back-end itself.

    Please correct me if im wrong
Children
No Data