>Generally speaking, a data mart is a denormalized set of tables that are usually synthesized in a way to optimize queries.

Yeah, ok, the problem with that is that we have about 400 lists with an average of 28 fields in each, all searchable, and this is customized per user. So, the possibility are limitless.

>Of course, that means a lag, between when data is posted to txaction tables, and when they appear in the data mart. For some, that lag is OK. Others find it unacceptable.

Seems like major sites such as Facebook where there are so many implementation like these that sometimes, whatever is posted takes a few seconds to be broadcasted. It used to be worst a while ago but went better in the last two years.

>SQL 2012 and 2014 enterprise have introduced some new data warehousing type features that help with the lag.

This is good to know.

>This is just an extremely brief overview. But it does sound like you might have some overloading in the process, and a data mart can sometimes help. More details would need to be covered to see if this would really help, but I do think it's something to at least consider.

For that, we will need to hire a specialized person in that, first because I don't have the time, secondly to gain on expertise and make sure we do it the right way.