Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

Thanks for supporting me on this issue.

I checked the timeout value in the Editor of my SSAS OLE DB Connection and
it is set to 0. My connectionstring looks like this:

Data Source=localhost;Initial Catalog=SSAS_DB;Provider=MSOLAP.3;Integrated
Security=SSPI;Impersonation Level=Impersonate;

When I process the cube it lasts about 30 minutes for a full process.

In BIDS I did not try but I will do now and post the result.

Kind regards,

Marc

Hello Charles

out from BIDS the processing with a SSIS package takes about 30 minutes and
was successful. I just moved this data warehouse to virtualized 64bit box -
before I did not have this problem. I realized that the last step of
processing takes a long time and nearly no processing power (seen in
taskmanager) is used.

Could this be a reason for the timeout?

Kind regards,

Marc

Hello Charles

out from BIDS the processing with a SSIS package takes about 30 minutes and
was successful. I just moved this data warehouse to virtualized 64bit box -
before I did not have this problem. I realized that the last step of
processing takes a long time and nearly no processing power (seen in
taskmanager) is used.

Could this be a reason for the timeout?

Kind regards,

Marc

Hello Charles

out from BIDS the processing with a SSIS package takes about 30 minutes and
was successful. I just moved this data warehouse to virtualized 64bit box -
before I did not have this problem. I realized that the last step of
processing takes a long time and nearly no processing power (seen in
taskmanager) is used.

Could this be a reason for the timeout?

Kind regards,

Marc