When your forced to pull data from a SharePoint List or long running SQL Queries

[james.davis]

Depending on how often the data gets updated, you will defiantly want to consider changing your Data cubes Storage Type to “Warehouse”.

I had 6 Data Cubes on one main Dashboard and all of the data retrieval was taking over 10 seconds. This was very annoying while testing to have to wait for the Dashboard to retrieve the data each time I went back and forth from EDIT to VIEW (or anything else that cause it to get the data again).

Now that I have switch them all over (all the SharePoint List and one SQL query) they all come back with data in 47 milliseconds.

That’s over 200 times faster.

For me I set up a schedule to re-build those Warehouses twice a day at 6am and 1pm.

I am curious to know if there is any known bottle neck in scheduling too many at the same time?

Hopefully if there is it is a very large number.

A lot of you might have known this already but I was completely amazed on just how much faster it went, and had to share.

[elia.scher.1 (Elia Scher)]

Thanks for the tip, James! Another bit I would like to add is that you have the option to Freeze your data while developing the dashboard.

This will prevent additional data retrieval until you unfreeze, which should help in scenarios like the one you described.

As for your question, there is no known bottle neck for simultaneously scheduled tasks, which means it's likely a very large number!