One more connection problem-Security Issue

My company gave me their old Windows 2000 server. I installed my
database on it and the ODBC connection works perfectly on the server.
When I go to my client machine I go the the ODBC Connections in it and
it fails. It refuses connections and will not reply to pings. It is not
a network issue, as I can telnet to the server just fine. It's strictly
a security issue. I just have no clue where to look. Any suggestions
would be appreciated. ThanksCurt (myemail@.nowehere.com) writes:

Quote:

Originally Posted by

My company gave me their old Windows 2000 server. I installed my
database on it and the ODBC connection works perfectly on the server.
When I go to my client machine I go the the ODBC Connections in it and
it fails. It refuses connections and will not reply to pings. It is not
a network issue, as I can telnet to the server just fine. It's strictly
a security issue. I just have no clue where to look. Any suggestions
would be appreciated. Thanks

Which version of SQL Server?

If you are using SQL 2005, you need to enable remote connections, as by
default Express and Developer Editon only accepts local connections. You
can use the Surface Area Configuration tool for this.

Also, if you are using SQL Express, make sure that SQL Broswer is running,
so that the named instance can be found.

If you are using SQL 2000, I would look in the Server Network Utility
to see which protcols that are installed.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

OLEDB vs ODBC

I am new SQL Server 2005. The native client supports both OLEDB and ODBC
connections. Which one should I prefer and why? Thanks.
I would say it depends on the particular application. We use JD Edwards
which runs on SQL server and it has always been configured for ODBC
connections. Because of a couple of other apps we have in house which call
for an OLEDB connection and the performance was great we migrated from ODBC
to OLEDB on JD Edwards and the performance was severely degraded so we
switched back to ODBC on this particular app.
Hope this helps.
Robby
"mason" <masonliu@.msn.com> wrote in message
news:O81z$qzNGHA.208@.tk2msftngp13.phx.gbl...
>I am new SQL Server 2005. The native client supports both OLEDB and ODBC
>connections. Which one should I prefer and why? Thanks.

OLEDB vs ODBC

Maybe this group is more responsive for this particular question. TIA.
-- Original Message --
From: "mason"
Newsgroups: microsoft.public.sqlserver.clients
Sent: Tuesday, February 21, 2006 5:01 PM
Subject: OLEDB vs ODBC

>I am new to SQL Server 2005. The native client supports both OLEDB and ODBC
> connections. Which one should I prefer and why? Thanks.ODBC is the older technology and is harder to use. Always use OLEDB where
possible as it is easier to implement and provides faster connections.
Ian Logan
"mason" wrote:

> Maybe this group is more responsive for this particular question. TIA.
>
> -- Original Message --
> From: "mason"
> Newsgroups: microsoft.public.sqlserver.clients
> Sent: Tuesday, February 21, 2006 5:01 PM
> Subject: OLEDB vs ODBC
>
>
>|||"Ian Logan" <IanLogan@.discussions.microsoft.com> wrote in message
news:2C8FB0CD-88BF-4532-A98A-BE75A699AA42@.microsoft.com...
> ODBC is the older technology and is harder to use. Always use OLEDB where
> possible as it is easier to implement and provides faster connections.
> Ian Logan
>
While that is true, there are still quite a few legacy applications out
there that only support ODBC. As Ian said, in general use OLEDB when
possible, but you will probably still want to have the ODBC drivers loaded.
As an example, I believe (I could be wrong here) that Microsoft Visio (prior
to 2002) only used ODBC.
Rick Sawtell
MCT, MCSD, MCDBA|||Thank you very much. That's what I like hear. I am not sure about "easier"
part, but "faster connection" tells them apart.
"Ian Logan" <IanLogan@.discussions.microsoft.com> wrote in message
news:2C8FB0CD-88BF-4532-A98A-BE75A699AA42@.microsoft.com...
> ODBC is the older technology and is harder to use. Always use OLEDB where
> possible as it is easier to implement and provides faster connections.
> Ian Logan
> "mason" wrote:
>|||Thanks. Since the native client is a single DLL supporting both OLEDB and
ODBC connections, this shouldn't be a problem. We are still going to support
ODBC connection (DSNless), but to make OLEDB the default configuration for
MSSQL2005.
"Rick Sawtell" <Quickening@.msn.com> wrote in message
news:e3xajlIOGHA.668@.TK2MSFTNGP11.phx.gbl...
> "Ian Logan" <IanLogan@.discussions.microsoft.com> wrote in message
> news:2C8FB0CD-88BF-4532-A98A-BE75A699AA42@.microsoft.com...
> While that is true, there are still quite a few legacy applications out
> there that only support ODBC. As Ian said, in general use OLEDB when
> possible, but you will probably still want to have the ODBC drivers
> loaded. As an example, I believe (I could be wrong here) that Microsoft
> Visio (prior to 2002) only used ODBC.
>
> Rick Sawtell
> MCT, MCSD, MCDBAsql

OLEDB versus ODBC

HI,

I'm using a reporting tool for retrieving information from a sqlsrv 2005 env. using OLE DB for my connection.
When i've created a metric and whilst refreshing it i get the message 'object was open'. Changing the connection into ODBC everything went well.

By looking at the log file it's trying to write the metric record in the DB but it simply cannot (OLEDB) but using ODBC is all went fine...

Is something not properly installed on the server side?

anyone?

E10

Are you using a 3rd-party reporting tools? It looks like they do not use OleDb in a proper way. Better check with the reporting tools' vendor.

oledb / odbc connection timeout

Hi - does anyone know of a sql server - server side resource limit that will
timeout an oledb connection running a simple select statement ? I am only
aware of the client side timeout options are there any server side limits
that will do this ? A user of mine is experiencing a timeout and I cant
reproduce the error and I just want to make sure I am not missing something.
Many thanks.
Ian
Timeouts are handled through the connection (client-side). What's the exact
error message (there are a couple different kinds of timeouts) and do you
have more specific circumstances? For instance, many queries time out in
EM, but run perfectly fine in QA.
"Ian G" <Ian G@.discussions.microsoft.com> wrote in message
news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> Hi - does anyone know of a sql server - server side resource limit that
> will
> timeout an oledb connection running a simple select statement ? I am only
> aware of the client side timeout options are there any server side limits
> that will do this ? A user of mine is experiencing a timeout and I cant
> reproduce the error and I just want to make sure I am not missing
> something.
> Many thanks.
> Ian
|||Remote query timeout is the only server-side setting which controls the
timeouts, but it only affects remote queries (i.e. server to server).
The following articles will help you get started troubleshooting query
timeouts.
http://support.microsoft.com/default...b;en-us;224453
http://support.microsoft.com/default...b;en-us;319892
http://support.microsoft.com/default...b;en-us;137983
http://support.microsoft.com/default...b;en-us;827422
Adrian
"Ian G" <Ian G@.discussions.microsoft.com> wrote in message
news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> Hi - does anyone know of a sql server - server side resource limit that
> will
> timeout an oledb connection running a simple select statement ? I am only
> aware of the client side timeout options are there any server side limits
> that will do this ? A user of mine is experiencing a timeout and I cant
> reproduce the error and I just want to make sure I am not missing
> something.
> Many thanks.
> Ian
|||Hi Michael
Thanks for the reply - the error message is below - but I have a growing
suspicion that my user may have connected to our server via his own sql
server (poss as a linked server). The error may then be coming from his own
server - I think I need to investigate exactly what the user is doing - I am
fairly confident now that I havent missed any obscure server side timeout.
Many thanks. If the error does give you any other idea's though - please let
me know. Best Wishes - Ian
Server: Msg 7399, Level 16, State 1, Line 12
OLE DB provider 'MSDASQL' reported an error. Execution terminated by the
provider because a resource limit was reached.
[OLE/DB provider returned message: [Microsoft][ODBC SQL Server
Driver]Timeout expired]
OLE DB error trace [OLE/DB Provider 'MSDASQL' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because a resource limit
was reached.].
"Michael C#" wrote:

> Timeouts are handled through the connection (client-side). What's the exact
> error message (there are a couple different kinds of timeouts) and do you
> have more specific circumstances? For instance, many queries time out in
> EM, but run perfectly fine in QA.
> "Ian G" <Ian G@.discussions.microsoft.com> wrote in message
> news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
>
>
|||Hi Adrian
Many thanks for your reply - I will read the KB articles but your info
confirmed my understanding and I am now fairly confident I havent missed any
obscure server side timeout limits. I replied to Michael C# with the error
message and what I think may be happening (pls let me know if this gives you
any other ideas). Thanks again for your help - much appreciated.
Best Wishes - Ian
"Adrian Zajkeskovic" wrote:

> Remote query timeout is the only server-side setting which controls the
> timeouts, but it only affects remote queries (i.e. server to server).
> The following articles will help you get started troubleshooting query
> timeouts.
> http://support.microsoft.com/default...b;en-us;224453
> http://support.microsoft.com/default...b;en-us;319892
> http://support.microsoft.com/default...b;en-us;137983
> http://support.microsoft.com/default...b;en-us;827422
> Adrian
>
> "Ian G" <Ian G@.discussions.microsoft.com> wrote in message
> news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
>
>

oledb / odbc connection timeout

Hi - does anyone know of a sql server - server side resource limit that will
timeout an oledb connection running a simple select statement ? I am only
aware of the client side timeout options are there any server side limits
that will do this ? A user of mine is experiencing a timeout and I cant
reproduce the error and I just want to make sure I am not missing something.
Many thanks.
IanTimeouts are handled through the connection (client-side). What's the exact
error message (there are a couple different kinds of timeouts) and do you
have more specific circumstances? For instance, many queries time out in
EM, but run perfectly fine in QA.
"Ian G" <Ian G@.discussions.microsoft.com> wrote in message
news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> Hi - does anyone know of a sql server - server side resource limit that
> will
> timeout an oledb connection running a simple select statement ? I am only
> aware of the client side timeout options are there any server side limits
> that will do this ? A user of mine is experiencing a timeout and I cant
> reproduce the error and I just want to make sure I am not missing
> something.
> Many thanks.
> Ian|||Remote query timeout is the only server-side setting which controls the
timeouts, but it only affects remote queries (i.e. server to server).
The following articles will help you get started troubleshooting query
timeouts.
http://support.microsoft.com/defaul...kb;en-us;224453
http://support.microsoft.com/defaul...kb;en-us;319892
http://support.microsoft.com/defaul...kb;en-us;137983
http://support.microsoft.com/defaul...kb;en-us;827422
Adrian
"Ian G" <Ian G@.discussions.microsoft.com> wrote in message
news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> Hi - does anyone know of a sql server - server side resource limit that
> will
> timeout an oledb connection running a simple select statement ? I am only
> aware of the client side timeout options are there any server side limits
> that will do this ? A user of mine is experiencing a timeout and I cant
> reproduce the error and I just want to make sure I am not missing
> something.
> Many thanks.
> Ian|||Hi Michael
Thanks for the reply - the error message is below - but I have a growing
suspicion that my user may have connected to our server via his own sql
server (poss as a linked server). The error may then be coming from his own
server - I think I need to investigate exactly what the user is doing - I am
fairly confident now that I havent missed any obscure server side timeout.
Many thanks. If the error does give you any other idea's though - please let
me know. Best Wishes - Ian
Server: Msg 7399, Level 16, State 1, Line 12
OLE DB provider 'MSDASQL' reported an error. Execution terminated by the
provider because a resource limit was reached.
[OLE/DB provider returned message: [Microsoft][ODBC SQL Server
Driver]Timeout expired]
OLE DB error trace [OLE/DB Provider 'MSDASQL' ICommandText::Execute retu
rned
0x80040e31: Execution terminated by the provider because a resource limit
was reached.].
"Michael C#" wrote:

> Timeouts are handled through the connection (client-side). What's the exa
ct
> error message (there are a couple different kinds of timeouts) and do you
> have more specific circumstances? For instance, many queries time out in
> EM, but run perfectly fine in QA.
> "Ian G" <Ian G@.discussions.microsoft.com> wrote in message
> news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
>
>|||Hi Adrian
Many thanks for your reply - I will read the KB articles but your info
confirmed my understanding and I am now fairly confident I havent missed any
obscure server side timeout limits. I replied to Michael C# with the error
message and what I think may be happening (pls let me know if this gives you
any other ideas). Thanks again for your help - much appreciated.
Best Wishes - Ian
"Adrian Zajkeskovic" wrote:

> Remote query timeout is the only server-side setting which controls the
> timeouts, but it only affects remote queries (i.e. server to server).
> The following articles will help you get started troubleshooting query
> timeouts.
> http://support.microsoft.com/defaul...kb;en-us;224453
> http://support.microsoft.com/defaul...kb;en-us;319892
> http://support.microsoft.com/defaul...kb;en-us;137983
> http://support.microsoft.com/defaul...kb;en-us;827422
> Adrian
>
> "Ian G" <Ian G@.discussions.microsoft.com> wrote in message
> news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
>
>

oledb / odbc connection timeout

Hi - does anyone know of a sql server - server side resource limit that will
timeout an oledb connection running a simple select statement ? I am only
aware of the client side timeout options are there any server side limits
that will do this ? A user of mine is experiencing a timeout and I cant
reproduce the error and I just want to make sure I am not missing something.
Many thanks.
IanTimeouts are handled through the connection (client-side). What's the exact
error message (there are a couple different kinds of timeouts) and do you
have more specific circumstances? For instance, many queries time out in
EM, but run perfectly fine in QA.
"Ian G" <Ian G@.discussions.microsoft.com> wrote in message
news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> Hi - does anyone know of a sql server - server side resource limit that
> will
> timeout an oledb connection running a simple select statement ? I am only
> aware of the client side timeout options are there any server side limits
> that will do this ? A user of mine is experiencing a timeout and I cant
> reproduce the error and I just want to make sure I am not missing
> something.
> Many thanks.
> Ian|||Remote query timeout is the only server-side setting which controls the
timeouts, but it only affects remote queries (i.e. server to server).
The following articles will help you get started troubleshooting query
timeouts.
http://support.microsoft.com/default.aspx?scid=kb;en-us;224453
http://support.microsoft.com/default.aspx?scid=kb;en-us;319892
http://support.microsoft.com/default.aspx?scid=kb;en-us;137983
http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
Adrian
"Ian G" <Ian G@.discussions.microsoft.com> wrote in message
news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> Hi - does anyone know of a sql server - server side resource limit that
> will
> timeout an oledb connection running a simple select statement ? I am only
> aware of the client side timeout options are there any server side limits
> that will do this ? A user of mine is experiencing a timeout and I cant
> reproduce the error and I just want to make sure I am not missing
> something.
> Many thanks.
> Ian|||Hi Michael
Thanks for the reply - the error message is below - but I have a growing
suspicion that my user may have connected to our server via his own sql
server (poss as a linked server). The error may then be coming from his own
server - I think I need to investigate exactly what the user is doing - I am
fairly confident now that I havent missed any obscure server side timeout.
Many thanks. If the error does give you any other idea's though - please let
me know. Best Wishes - Ian
Server: Msg 7399, Level 16, State 1, Line 12
OLE DB provider 'MSDASQL' reported an error. Execution terminated by the
provider because a resource limit was reached.
[OLE/DB provider returned message: [Microsoft][ODBC SQL Server
Driver]Timeout expired]
OLE DB error trace [OLE/DB Provider 'MSDASQL' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because a resource limit
was reached.].
"Michael C#" wrote:
> Timeouts are handled through the connection (client-side). What's the exact
> error message (there are a couple different kinds of timeouts) and do you
> have more specific circumstances? For instance, many queries time out in
> EM, but run perfectly fine in QA.
> "Ian G" <Ian G@.discussions.microsoft.com> wrote in message
> news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> > Hi - does anyone know of a sql server - server side resource limit that
> > will
> > timeout an oledb connection running a simple select statement ? I am only
> > aware of the client side timeout options are there any server side limits
> > that will do this ? A user of mine is experiencing a timeout and I cant
> > reproduce the error and I just want to make sure I am not missing
> > something.
> > Many thanks.
> >
> > Ian
>
>|||Hi Adrian
Many thanks for your reply - I will read the KB articles but your info
confirmed my understanding and I am now fairly confident I havent missed any
obscure server side timeout limits. I replied to Michael C# with the error
message and what I think may be happening (pls let me know if this gives you
any other ideas). Thanks again for your help - much appreciated.
Best Wishes - Ian
"Adrian Zajkeskovic" wrote:
> Remote query timeout is the only server-side setting which controls the
> timeouts, but it only affects remote queries (i.e. server to server).
> The following articles will help you get started troubleshooting query
> timeouts.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;224453
> http://support.microsoft.com/default.aspx?scid=kb;en-us;319892
> http://support.microsoft.com/default.aspx?scid=kb;en-us;137983
> http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
> Adrian
>
> "Ian G" <Ian G@.discussions.microsoft.com> wrote in message
> news:CBC74343-06BC-4AC1-B68A-04E701CDB3CC@.microsoft.com...
> > Hi - does anyone know of a sql server - server side resource limit that
> > will
> > timeout an oledb connection running a simple select statement ? I am only
> > aware of the client side timeout options are there any server side limits
> > that will do this ? A user of mine is experiencing a timeout and I cant
> > reproduce the error and I just want to make sure I am not missing
> > something.
> > Many thanks.
> >
> > Ian
>
>

ole db, odbc, mdac what does enterprise manager register server use?

I hear a lot about different ways of pulling data off of sql servers.
When you go to register a server in enterprise manager what method of
data access is it using? ole db, odbc, ?
"tbone" <tony.despain@.gmail.com> wrote in message
news:1139251537.917459.100430@.g44g2000cwa.googlegr oups.com...
>I hear a lot about different ways of pulling data off of sql servers.
> When you go to register a server in enterprise manager what method of
> data access is it using? ole db, odbc, ?
>
My best guess is that it is using the SQL-DMO API. How the API is
connecting, who knows. I would guess that it is either using SQL OLE-DB, or
it may be using DBLib.
Rick Sawtell
MCT, MCSD, MCDBA

ole db, odbc, mdac what does enterprise manager register server use?

I hear a lot about different ways of pulling data off of sql servers.
When you go to register a server in enterprise manager what method of
data access is it using? ole db, odbc, ?"tbone" <tony.despain@.gmail.com> wrote in message
news:1139251537.917459.100430@.g44g2000cwa.googlegroups.com...
>I hear a lot about different ways of pulling data off of sql servers.
> When you go to register a server in enterprise manager what method of
> data access is it using? ole db, odbc, ?
>
My best guess is that it is using the SQL-DMO API. How the API is
connecting, who knows. I would guess that it is either using SQL OLE-DB, or
it may be using DBLib.
Rick Sawtell
MCT, MCSD, MCDBA

ole db, odbc, mdac what does enterprise manager register server use?

I hear a lot about different ways of pulling data off of sql servers.
When you go to register a server in enterprise manager what method of
data access is it using? ole db, odbc, ?"tbone" <tony.despain@.gmail.com> wrote in message
news:1139251537.917459.100430@.g44g2000cwa.googlegroups.com...
>I hear a lot about different ways of pulling data off of sql servers.
> When you go to register a server in enterprise manager what method of
> data access is it using? ole db, odbc, ?
>
My best guess is that it is using the SQL-DMO API. How the API is
connecting, who knows. I would guess that it is either using SQL OLE-DB, or
it may be using DBLib.
Rick Sawtell
MCT, MCSD, MCDBA

ole db vs odbc

where can i find differences between these 2 data access components?See my reply to your previous post.
Andrew J. Kelly SQL MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23SbXRCWEFHA.464@.TK2MSFTNGP15.phx.gbl...
> where can i find differences between these 2 data access components?
>|||Check out this link - I answered a similar question here:
http://www.vb-forum.com/showthread.php?t=322281
"Hassan" wrote:

> where can i find differences between these 2 data access components?
>
>

ole db vs odbc

where can i find differences between these 2 data access components?
See my reply to your previous post.
Andrew J. Kelly SQL MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23SbXRCWEFHA.464@.TK2MSFTNGP15.phx.gbl...
> where can i find differences between these 2 data access components?
>
|||Check out this link - I answered a similar question here:
http://www.vb-forum.com/showthread.php?t=322281
"Hassan" wrote:

> where can i find differences between these 2 data access components?
>
>

ole db vs odbc

where can i find differences between these 2 data access components?See my reply to your previous post.
--
Andrew J. Kelly SQL MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23SbXRCWEFHA.464@.TK2MSFTNGP15.phx.gbl...
> where can i find differences between these 2 data access components?
>|||Check out this link - I answered a similar question here:
http://www.vb-forum.com/showthread.php?t=322281
"Hassan" wrote:
> where can i find differences between these 2 data access components?
>
>

OLE DB timeout processing AS Cube

When doing a full process of the Analysis Services Cube with several partitioned measure groups. We receive: "OLE DB error: OLE DB or ODBC error: Query timeout expired HYT00" or "OLE DB error: OLE DB or ODBC error: Query timeout expired HY008". There are 410 million rows in one base table and 80 million rows in another base table. The other measure groups process fine. It has abended at 61 minutes the last 3 times. I can individually process each measure group successfully.

Any help is greatly appreciated, Edwina Derrick

Simular problem for me. Have a huge database to be queried and can't pass the 60 minutes query time despite having made sure that ALL!! timeout values are suposed to be eternal (zero in most cases). This seems like a bug to me. I used the developer release version of the SQL2005. Would appriciate the Microsoft development team to test this problem and to suply information of when and how to bypass this 1 hour timeout limitation.

|||Try increasing ExternalCommandTimeout Analysis Server advanced property.

Being in situation when Analysis Server needs to wait for an hour for some data to come from SQL Server is very unusual. Such situation ususally means that SQL server needs to perform some heavy operation before it can start sending data out. Try optimizing your SQL Server database.
Edward Melomed (MSFT)

---

This posting is provided "AS IS" with no warranties, and confers no rights.|||

WTF....

isn't there a way to set the timeout?

If I was able to "Optimize my SQL Server database".....

I have five fact tables (All of them are required) and each table has it's own Dimensions.

since I am unable to create a cube on a left join relationship I need to work with views ("SQL server needs to perform some heavy operation before it can start sending data out").

OLE DB timeout processing AS Cube

When doing a full process of the Analysis Services Cube with several partitioned measure groups. We receive: "OLE DB error: OLE DB or ODBC error: Query timeout expired HYT00" or "OLE DB error: OLE DB or ODBC error: Query timeout expired HY008". There are 410 million rows in one base table and 80 million rows in another base table. The other measure groups process fine. It has abended at 61 minutes the last 3 times. I can individually process each measure group successfully.

Any help is greatly appreciated, Edwina Derrick

Simular problem for me. Have a huge database to be queried and can't pass the 60 minutes query time despite having made sure that ALL!! timeout values are suposed to be eternal (zero in most cases). This seems like a bug to me. I used the developer release version of the SQL2005. Would appriciate the Microsoft development team to test this problem and to suply information of when and how to bypass this 1 hour timeout limitation.

|||Try increasing ExternalCommandTimeout Analysis Server advanced property.

Being in situation when Analysis Server needs to wait for an hour for some data to come from SQL Server is very unusual. Such situation ususally means that SQL server needs to perform some heavy operation before it can start sending data out. Try optimizing your SQL Server database.
Edward Melomed (MSFT)

---

This posting is provided "AS IS" with no warranties, and confers no rights.|||

WTF....

isn't there a way to set the timeout?

If I was able to "Optimize my SQL Server database".....

I have five fact tables (All of them are required) and each table has it's own Dimensions.

since I am unable to create a cube on a left join relationship I need to work with views ("SQL server needs to perform some heavy operation before it can start sending data out").

OLE DB timeout processing AS Cube

When doing a full process of the Analysis Services Cube with several partitioned measure groups. We receive: "OLE DB error: OLE DB or ODBC error: Query timeout expired HYT00" or "OLE DB error: OLE DB or ODBC error: Query timeout expired HY008". There are 410 million rows in one base table and 80 million rows in another base table. The other measure groups process fine. It has abended at 61 minutes the last 3 times. I can individually process each measure group successfully.

Any help is greatly appreciated, Edwina Derrick

Simular problem for me. Have a huge database to be queried and can't pass the 60 minutes query time despite having made sure that ALL!! timeout values are suposed to be eternal (zero in most cases). This seems like a bug to me. I used the developer release version of the SQL2005. Would appriciate the Microsoft development team to test this problem and to suply information of when and how to bypass this 1 hour timeout limitation.

|||Try increasing ExternalCommandTimeout Analysis Server advanced property.

Being in situation when Analysis Server needs to wait for an hour for some data to come from SQL Server is very unusual. Such situation ususally means that SQL server needs to perform some heavy operation before it can start sending data out. Try optimizing your SQL Server database.
Edward Melomed (MSFT)

---

This posting is provided "AS IS" with no warranties, and confers no rights.|||

WTF....

isn't there a way to set the timeout?

If I was able to "Optimize my SQL Server database".....

I have five fact tables (All of them are required) and each table has it's own Dimensions.

since I am unable to create a cube on a left join relationship I need to work with views ("SQL server needs to perform some heavy operation before it can start sending data out").

OLE DB Provider for ODBC/Win XP

I have SQL Server Developer Edition which runs on Windows XP and it has been
running fine thus far. I am now trying to run Analysis Services on it and it
needs OLE DB Provider for ODBC. I downloaded MDAC 2.8 and installed it on my
Windows XP platform. The installation went without a hitch but when I go to
Data Sources (ODBC), I cannot see OLE DB Provider for ODBC listed. Does OLE
DB Provider for ODBC only run on Windows 2000 or Windows NT?
Thanks,
AlistairOops, that should be OLE DB Provider for OLAP.
Alistair
"lestersal" <lestersal@.cox.net> wrote in message
news:yLs3c.40660$1k.22567@.okepread01...
> I have SQL Server Developer Edition which runs on Windows XP and it has
been
> running fine thus far. I am now trying to run Analysis Services on it and
it
> needs OLE DB Provider for ODBC. I downloaded MDAC 2.8 and installed it on
my
> Windows XP platform. The installation went without a hitch but when I go
to
> Data Sources (ODBC), I cannot see OLE DB Provider for ODBC listed. Does
OLE
> DB Provider for ODBC only run on Windows 2000 or Windows NT?
> Thanks,
> Alistair
>|||The Data Sources (ODBC) control panel applet only deals with ODBC data
sources and drivers. You are referring to an OLE DB provider.
OLE DB has a similar data sources interface. Try creating a empty text
file, and save it with a .udl file extension. Then double-click that file
and you should get the OLE DB interface.
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.
"lestersal" <lestersal@.cox.net> wrote in message
news:5oA3c.40902$1k.38183@.okepread01...
> Oops, that should be OLE DB Provider for OLAP.
> Alistair
> "lestersal" <lestersal@.cox.net> wrote in message
> news:yLs3c.40660$1k.22567@.okepread01...
> been
and
> it
on
> my
> to
> OLE
>

OLE DB Provider for ODBC and Oracle

Hi,

I created a linked server for MS SQL Server 2005 Express to an Oracle
database using the OLE DB Provider for ODBC. My ODBC Source uses the
Microsoft ODBC for Oracle driver.
I'm using the OLE DB Provider for ODBC instead of the Oracle OLE DB
providers because those don't handle Oracle's Numeric Data Type well.
When I set this up yesterday it worked fine. However I log in today and
attempt to run sp_tables_exec against my linked server and get the
following

OLE DB provider "MSDASQL" for linked server "WHATEVER" returned message
"[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "WHATEVER" returned message
"[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "WHATEVER" returned message
"[Microsoft][ODBC driver for Oracle][Oracle]".
Msg 7303, Level 16, State 1, Procedure sp_tables_ex, Line 41
Cannot initialize the data source object of OLE DB provider "MSDASQL"
for linked server "WHATEVER".

I can tnsping the server, and I have no trouble connecting with the
Oracle OLE DB provider

I try to set up ODBC logging but the log file is blank -- same with
attempting to set up logging for Oracle's network client. I've been
dealing with crap like this the last 4 days, something works one day,
then the next nothing (I've done nothing to change the configuration
between these outages).

Can anyone help me?

Thanks
FrustratedReplied to duplicate post of 22/12 !

"Crazy Cat" <danbredy@.hotmail.com> wrote in message
news:1135178623.892320.137120@.o13g2000cwo.googlegr oups.com...
> Hi,
> I created a linked server for MS SQL Server 2005 Express to an Oracle
> database using the OLE DB Provider for ODBC. My ODBC Source uses the
> Microsoft ODBC for Oracle driver.
> I'm using the OLE DB Provider for ODBC instead of the Oracle OLE DB
> providers because those don't handle Oracle's Numeric Data Type well.
> When I set this up yesterday it worked fine. However I log in today and
> attempt to run sp_tables_exec against my linked server and get the
> following
> OLE DB provider "MSDASQL" for linked server "WHATEVER" returned message
> "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
> OLE DB provider "MSDASQL" for linked server "WHATEVER" returned message
> "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
> OLE DB provider "MSDASQL" for linked server "WHATEVER" returned message
> "[Microsoft][ODBC driver for Oracle][Oracle]".
> Msg 7303, Level 16, State 1, Procedure sp_tables_ex, Line 41
> Cannot initialize the data source object of OLE DB provider "MSDASQL"
> for linked server "WHATEVER".
> I can tnsping the server, and I have no trouble connecting with the
> Oracle OLE DB provider
> I try to set up ODBC logging but the log file is blank -- same with
> attempting to set up logging for Oracle's network client. I've been
> dealing with crap like this the last 4 days, something works one day,
> then the next nothing (I've done nothing to change the configuration
> between these outages).
> Can anyone help me?
> Thanks
> Frustrated

OLE DB Provider

How do you set up an OLE DB Provider on a client machine.
Is there a similar setup procedure as ODBC?
Thanks,
StephIf you have MDAC installed on your client PC, you will have all major OLE DB
providers. MDAC gets installed along with some applications. You can also
get it from Microsoft site at: http://www.microsoft.com/data
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"steph" <stephaniebeling@.hotmail.com> wrote in message
news:393a01c3559d$91c59f60$a001280a@.phx.gbl...
How do you set up an OLE DB Provider on a client machine.
Is there a similar setup procedure as ODBC?
Thanks,
Steph

OLE DB or ODBC collation information

Good morning.
We are building a SQL Server client in C++ and out client needs to be
able to dynamically discover collation information about result set
columns and existing table columns. We'd like to be able to map that
collation back to an LCID in Win32. Does anyone know the proper
properties or interfaces to use to obtain this information?
ThanksYou can use a system store procedure:
exec [<database>]..sp_tablecollations '[<schema>].[<tablename>]'
Michael
"Chris Stolte" <cstolte@.graphics.stanford.edu> wrote in message
news:98086226.0410220714.20ad4ed2@.posting.google.com...
> Good morning.
> We are building a SQL Server client in C++ and out client needs to be
> able to dynamically discover collation information about result set
> columns and existing table columns. We'd like to be able to map that
> collation back to an LCID in Win32. Does anyone know the proper
> properties or interfaces to use to obtain this information?
> Thanks|||And to map a collation to an LCID:
SELECT COLLATIONPROPERTY ('<collation_name>', 'LCID')
To do this in one query instead of submitting the above for each of the
columns returned by sp_tablecollations:
USE pubs
GO
SELECT COLUMN_NAME, DATA_TYPE, COLLATION_NAME,
COLLATIONPROPERTY (COLLATION_NAME, 'LCID') AS LCID
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_CATALOG = 'pubs' AND TABLE_SCHEMA = 'dbo' AND TABLE_NAME =
'authors'
Bart
--
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "Michael Thomas \(Microsoft\)" <mithomas@.online.microsoft.com>
| References: <98086226.0410220714.20ad4ed2@.posting.google.com>
| Subject: Re: OLE DB or ODBC collation information
| Date: Fri, 22 Oct 2004 09:21:33 -0700
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.181
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
| Message-ID: <eMH94MFuEHA.1372@.TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.odbc
| NNTP-Posting-Host: tide138.microsoft.com 131.107.71.95
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.odbc:42809
| X-Tomcat-NG: microsoft.public.sqlserver.odbc
|
| You can use a system store procedure:
|
| exec [<database>]..sp_tablecollations '[<schema>].[<tablename>
]'
|
|
|
| Michael
|
|
| "Chris Stolte" <cstolte@.graphics.stanford.edu> wrote in message
| news:98086226.0410220714.20ad4ed2@.posting.google.com...
| > Good morning.
| >
| > We are building a SQL Server client in C++ and out client needs to be
| > able to dynamically discover collation information about result set
| > columns and existing table columns. We'd like to be able to map that
| > collation back to an LCID in Win32. Does anyone know the proper
| > properties or interfaces to use to obtain this information?
| >
| > Thanks
|
|
|