Not trying to be a wet blanket, but isn't one of the tenants of the relational database to eliminate redundancy?

Who (what) reloads the application variable when the employees table is altered?

What about when there are multiple websites that draw data from a single source?

Does the database really need to know anything about the interfaces that connect to it?

In the cases of storing result sets in session variables things become even harder to manage, as there are likely to be many users that can access data from a shared table, ie a list of preferred locations. Any number of session variables may need to be updated when the base data is modified.

Just my 2 cents...