It look like source connection issue ... check data source property if you are able to make connection with appropriate impersonation information.

It can be processed by Proactive caching. In Proactive caching, you need not to schedule it by SSMS. Analysis Services will take care.

http://www.msbiconcepts.com/2010/10/implementation-of-proactive-caching-in.html

This question gave me idea to write about Proactive caching feature to help my developer friends...

http://learnmicrosoftbi.blogspot.com/2010/10/implementation-of-proactive-caching-in.html

Hi,

It depends on your cube processing strategy. There are two types of processing strategy:

1) Process full

2) Process incremental

If it is Process full then no issues, AS DB will be created...

Hi,

You can change following properties in caching settings(same storage option window):

1) Silence Interval

2) Silence Override interval

if Silence interval = 10 second then analysis server will remain silent till 10 seconds...

Cube does not detect changes automatically ... By default, cube gets created in MOLAP storage mode and you need to reprocess(process all, process incremental) it based on your frequency (hourly,...

Hi,

Can you please elaborate your problem? It is not clear from your problem statement ...

Spare me if i have not understood your problem correctly...

In Data Source view , If you add new named calculation in time/date dimension and make it key column then you...

Hi,

I will strongly suggest to move ahead with SSAS cubes and MDX if you have signification data into DM/DW(~> 1000MB). Performance will be key factor in deciding OLAP layer. There...

You can refer to Vidas Matelis site:

www.ssas-info.com

Few good articles can be found in below site:

http://www.msbiconcepts.com