Why did the QV consultant make the dashboard loading the same data twice?

[#1]

Hi,

I think it might be the norm, but my companies most used dashboard uses transactional data loaded twice.  Once as TY for this year and once for LY or last year.  It does this for the last 10 years of record keeping.  Is this more efficinet or just easeir for a consultant to implement?

[luciancotea]

Comparisons works faster.

[#3]

I actually made a copy of the same document with slightly different set anaylsis that only loads the data once.  I did that in hopes that the lesser menory would make the document faster.  It appears though that they are exactly the same speed. 

[luciancotea]

Now do a chart where you compare each months sales vs same month of previous year sales by Product and check the speed.

[#5]

Brandon,
If they are the same speed (I persume you mean "referesh rate" on the front-end) and if they give the same result (in your case sales) - I guess the only question left is: what is the reload time(s).

Another thing to be mindful of if you choose to leave it loading TY and LY is that if any changes are to be made in your Transactions table - the load script will have to be changed in 2 places.

[#6]

The file size is for both the data model layer and application layer decreased in size by about a third and needed to be changed.  Also, I just didn't load LY in either of those two so I didn't have to change the extraction layer(which makes the .qvds that the next layer loads from.) 

Even though reload times on the front-end seem to be about the same, all the values on the front end were the same when both were in production on the server so I went with the new smaller one.