"dba" <bryanmur...@gmail.com> wrote in message

>I have a pretty big database, 4 terabytes. It's an Inman style data
> warehouse, I tried both on the tables directly, then tried to create
> some views of just the dimensions I needed a fact table. I set
> sp_configure on the server:

> exec sp_configure @configname='remote query timeout (s)' ,@configvalue
> ='2147483647'

> exec sp_configure @configname='remote login timeout (s)' ,@configvalue
> ='2147483647'

> RECONFIGURE WITH OVERRIDE;

> In SQL Server Configuration Manager I set for TCP/IP Keep Alive 0,
> Keep Alive Interval 0 for the native client configuration => Client
> Protocols.

> When I process with SQL Native Client I get this error:

> Errors in the high-level relational engine. The following exception
> occurred while the managed IDbConnection interface was being used:
> Timeout expired.  The timeout period elapsed prior to obtaining a
> connection from the pool.  This may have occurred because all pooled
> connections were in use and max pool size was reached..

> When I use OLE DB I get this error:

> OLE DB error: OLE DB or ODBC error: Timeout expired; HYT00.

> I put in a call to support but haven't gotten a response back yet.
> Wondering if anyone else has had a similiar issue.

> Analysis Services 2005 is on the same box as the SQL Server 2005 DB.
> Just changed the Processing Order: Sequential and the Transaction
> mode: Objects in serpate transactions. Have been able to build cubes
> with smaller tables but larger ones always time out.

> Please help or post for other's benefit.
> Regards
> Bryan

Info.com> wrote:
> Bryan,

> It seems to me that problem is with your relational database refusing
> connections, as it is busy enough. I would do following things to test:
> 1. In BIDS double click on your data source(s) and change parameter "Maximum
> Number of connections" to something smaller, lets say 4-6. I believe by
> default will be 10.
> 2. When submitting processing, specify Maximum Parallel tasks option to
> something reasonable, like 4, 6.
> Then test, and change values as required.

> All this will increase your processing time, buy you might avoid timeout.
> You have to figure out what is causing it and what is happening when you get
> timeout? Like, server CPU is 100% busy.
> . Do you have partitions? How much memory, 64 bit, how many cpu's ?

> HTH,

> Vidas Matelis

> http://www.ssas-info.com

> "dba" <bryanmur...@gmail.com> wrote in message

> news:1180553215.194245.296630@h2g2000hsg.googlegroups.com...

> >I have a pretty big database, 4 terabytes. It's an Inman style data
> > warehouse, I tried both on the tables directly, then tried to create
> > some views of just the dimensions I needed a fact table. I set
> > sp_configure on the server:

> > exec sp_configure @configname='remote query timeout (s)' ,@configvalue
> > ='2147483647'

> > exec sp_configure @configname='remote login timeout (s)' ,@configvalue
> > ='2147483647'

> > RECONFIGURE WITH OVERRIDE;

> > In SQL Server Configuration Manager I set for TCP/IP Keep Alive 0,
> > Keep Alive Interval 0 for the native client configuration => Client
> > Protocols.

> > When I process with SQL Native Client I get this error:

> > Errors in the high-level relational engine. The following exception
> > occurred while the managed IDbConnection interface was being used:
> > Timeout expired.  The timeout period elapsed prior to obtaining a
> > connection from the pool.  This may have occurred because all pooled
> > connections were in use and max pool size was reached..

> > When I use OLE DB I get this error:

> > OLE DB error: OLE DB or ODBC error: Timeout expired; HYT00.

> > I put in a call to support but haven't gotten a response back yet.
> > Wondering if anyone else has had a similiar issue.

> > Analysis Services 2005 is on the same box as the SQL Server 2005 DB.
> > Just changed the Processing Order: Sequential and the Transaction
> > mode: Objects in serpate transactions. Have been able to build cubes
> > with smaller tables but larger ones always time out.

> > Please help or post for other's benefit.
> > Regards
> > Bryan- Hide quoted text -

> - Show quoted text -

"dba" <bryanmur...@gmail.com> wrote in message

> On May 30, 5:04 pm, "Vidas Matelis" <Vidas.Mate...@RemoveNoSpam.SSAS-
> Info.com> wrote:
>> Bryan,

>> It seems to me that problem is with your relational database refusing
>> connections, as it is busy enough. I would do following things to test:
>> 1. In BIDS double click on your data source(s) and change parameter
>> "Maximum
>> Number of connections" to something smaller, lets say 4-6. I believe by
>> default will be 10.
>> 2. When submitting processing, specify Maximum Parallel tasks option to
>> something reasonable, like 4, 6.
>> Then test, and change values as required.

>> All this will increase your processing time, buy you might avoid timeout.
>> You have to figure out what is causing it and what is happening when you
>> get
>> timeout? Like, server CPU is 100% busy.
>> . Do you have partitions? How much memory, 64 bit, how many cpu's ?

>> HTH,

>> Vidas Matelis

>> http://www.ssas-info.com

>> "dba" <bryanmur...@gmail.com> wrote in message

>> news:1180553215.194245.296630@h2g2000hsg.googlegroups.com...

>> >I have a pretty big database, 4 terabytes. It's an Inman style data
>> > warehouse, I tried both on the tables directly, then tried to create
>> > some views of just the dimensions I needed a fact table. I set
>> > sp_configure on the server:

>> > exec sp_configure @configname='remote query timeout (s)' ,@configvalue
>> > ='2147483647'

>> > exec sp_configure @configname='remote login timeout (s)' ,@configvalue
>> > ='2147483647'

>> > RECONFIGURE WITH OVERRIDE;

>> > In SQL Server Configuration Manager I set for TCP/IP Keep Alive 0,
>> > Keep Alive Interval 0 for the native client configuration => Client
>> > Protocols.

>> > When I process with SQL Native Client I get this error:

>> > Errors in the high-level relational engine. The following exception
>> > occurred while the managed IDbConnection interface was being used:
>> > Timeout expired.  The timeout period elapsed prior to obtaining a
>> > connection from the pool.  This may have occurred because all pooled
>> > connections were in use and max pool size was reached..

>> > When I use OLE DB I get this error:

>> > OLE DB error: OLE DB or ODBC error: Timeout expired; HYT00.

>> > I put in a call to support but haven't gotten a response back yet.
>> > Wondering if anyone else has had a similiar issue.

>> > Analysis Services 2005 is on the same box as the SQL Server 2005 DB.
>> > Just changed the Processing Order: Sequential and the Transaction
>> > mode: Objects in serpate transactions. Have been able to build cubes
>> > with smaller tables but larger ones always time out.

>> > Please help or post for other's benefit.
>> > Regards
>> > Bryan- Hide quoted text -

>> - Show quoted text -

> Thanks for responding Vidas.

> The support representative gave me the following instructions:

> Right click on Analysis Services in Management Studio
> => Properties.
> => Show Advanced (all) Properties
> => ExternalCommandTimeout 0
> => ExternalConnectionTimeout 0

> Restart Analysis Services.

Info.com> wrote:
> Bryan,

> Thanks for sharing this.

> Vidas Matelis

> "dba" <bryanmur...@gmail.com> wrote in message

> news:1180627571.001299.75640@g4g2000hsf.googlegroups.com...

> > On May 30, 5:04 pm, "Vidas Matelis" <Vidas.Mate...@RemoveNoSpam.SSAS-
> > Info.com> wrote:
> >> Bryan,

> >> It seems to me that problem is with your relational database refusing
> >> connections, as it is busy enough. I would do following things to test:
> >> 1. In BIDS double click on your data source(s) and change parameter
> >> "Maximum
> >> Number of connections" to something smaller, lets say 4-6. I believe by
> >> default will be 10.
> >> 2. When submitting processing, specify Maximum Parallel tasks option to
> >> something reasonable, like 4, 6.
> >> Then test, and change values as required.

> >> All this will increase your processing time, buy you might avoid timeout.
> >> You have to figure out what is causing it and what is happening when you
> >> get
> >> timeout? Like, server CPU is 100% busy.
> >> . Do you have partitions? How much memory, 64 bit, how many cpu's ?

> >> HTH,

> >> Vidas Matelis

> >>http://www.ssas-info.com

> >> "dba" <bryanmur...@gmail.com> wrote in message

> >>news:1180553215.194245.296630@h2g2000hsg.googlegroups.com...

> >> >I have a pretty big database, 4 terabytes. It's an Inman style data
> >> > warehouse, I tried both on the tables directly, then tried to create
> >> > some views of just the dimensions I needed a fact table. I set
> >> > sp_configure on the server:

> >> > exec sp_configure @configname='remote query timeout (s)' ,@configvalue
> >> > ='2147483647'

> >> > exec sp_configure @configname='remote login timeout (s)' ,@configvalue
> >> > ='2147483647'

> >> > RECONFIGURE WITH OVERRIDE;

> >> > In SQL Server Configuration Manager I set for TCP/IP Keep Alive 0,
> >> > Keep Alive Interval 0 for the native client configuration => Client
> >> > Protocols.

> >> > When I process with SQL Native Client I get this error:

> >> > Errors in the high-level relational engine. The following exception
> >> > occurred while the managed IDbConnection interface was being used:
> >> > Timeout expired.  The timeout period elapsed prior to obtaining a
> >> > connection from the pool.  This may have occurred because all pooled
> >> > connections were in use and max pool size was reached..

> >> > When I use OLE DB I get this error:

> >> > OLE DB error: OLE DB or ODBC error: Timeout expired; HYT00.

> >> > I put in a call to support but haven't gotten a response back yet.
> >> > Wondering if anyone else has had a similiar issue.

> >> > Analysis Services 2005 is on the same box as the SQL Server 2005 DB.
> >> > Just changed the Processing Order: Sequential and the Transaction
> >> > mode: Objects in serpate transactions. Have been able to build cubes
> >> > with smaller tables but larger ones always time out.

> >> > Please help or post for other's benefit.
> >> > Regards
> >> > Bryan- Hide quoted text -

> >> - Show quoted text -

> > Thanks for responding Vidas.

> > The support representative gave me the following instructions:

> > Right click on Analysis Services in Management Studio
> > => Properties.
> > => Show Advanced (all) Properties
> > => ExternalCommandTimeout 0
> > => ExternalConnectionTimeout 0

> > Restart Analysis Services.- Hide quoted text -

> - Show quoted text -