We have linked database servers using linked server feature. Is it a
resource intensive setting? Any one has any comments and their experiences
on this setup?
SQL 2K.
JoeHere's a WebCast that focuses on Linked Server configuration, usage, and
troubleshooting
(http://support.microsoft.com/default.aspx?scid=kb;en-us;326839). It should
give you a good overview. The link itself isn't resource intensive however
at run time, depending how data is used across the link, it will have some
impact on the individual query involved as some JOINS may need to be staged
in TempDB before being resolved against local tables. You also need to
carefully consider the security implications of your Linked Server
definition. Not that there's any pure security issues per-se however like
any other tool, when not properly configured and then exposed for public
consumption it could leave you data wide open.
--
--Brian
(Please reply to the newsgroups only.)
"JoeMathew" <Joe_Mathew@.hotmail.com> wrote in message
news:ueGbMGZtFHA.2076@.TK2MSFTNGP14.phx.gbl...
> We have linked database servers using linked server feature. Is it a
> resource intensive setting? Any one has any comments and their experiences
> on this setup?
> SQL 2K.
> Joe
>
Showing posts with label setting. Show all posts
Showing posts with label setting. Show all posts
Friday, March 23, 2012
servers..
We have linked database servers using linked server feature. Is it a
resource intensive setting? Any one has any comments and their experiences
on this setup?
SQL 2K.
Joe
Here's a WebCast that focuses on Linked Server configuration, usage, and
troubleshooting
(http://support.microsoft.com/default...b;en-us;326839). It should
give you a good overview. The link itself isn't resource intensive however
at run time, depending how data is used across the link, it will have some
impact on the individual query involved as some JOINS may need to be staged
in TempDB before being resolved against local tables. You also need to
carefully consider the security implications of your Linked Server
definition. Not that there's any pure security issues per-se however like
any other tool, when not properly configured and then exposed for public
consumption it could leave you data wide open.
--Brian
(Please reply to the newsgroups only.)
"JoeMathew" <Joe_Mathew@.hotmail.com> wrote in message
news:ueGbMGZtFHA.2076@.TK2MSFTNGP14.phx.gbl...
> We have linked database servers using linked server feature. Is it a
> resource intensive setting? Any one has any comments and their experiences
> on this setup?
> SQL 2K.
> Joe
>
sql
resource intensive setting? Any one has any comments and their experiences
on this setup?
SQL 2K.
Joe
Here's a WebCast that focuses on Linked Server configuration, usage, and
troubleshooting
(http://support.microsoft.com/default...b;en-us;326839). It should
give you a good overview. The link itself isn't resource intensive however
at run time, depending how data is used across the link, it will have some
impact on the individual query involved as some JOINS may need to be staged
in TempDB before being resolved against local tables. You also need to
carefully consider the security implications of your Linked Server
definition. Not that there's any pure security issues per-se however like
any other tool, when not properly configured and then exposed for public
consumption it could leave you data wide open.
--Brian
(Please reply to the newsgroups only.)
"JoeMathew" <Joe_Mathew@.hotmail.com> wrote in message
news:ueGbMGZtFHA.2076@.TK2MSFTNGP14.phx.gbl...
> We have linked database servers using linked server feature. Is it a
> resource intensive setting? Any one has any comments and their experiences
> on this setup?
> SQL 2K.
> Joe
>
sql
servers..
We have linked database servers using linked server feature. Is it a
resource intensive setting? Any one has any comments and their experiences
on this setup?
SQL 2K.
JoeHere's a WebCast that focuses on Linked Server configuration, usage, and
troubleshooting
(http://support.microsoft.com/defaul...kb;en-us;326839). It should
give you a good overview. The link itself isn't resource intensive however
at run time, depending how data is used across the link, it will have some
impact on the individual query involved as some JOINS may need to be staged
in TempDB before being resolved against local tables. You also need to
carefully consider the security implications of your Linked Server
definition. Not that there's any pure security issues per-se however like
any other tool, when not properly configured and then exposed for public
consumption it could leave you data wide open.
--Brian
(Please reply to the newsgroups only.)
"JoeMathew" <Joe_Mathew@.hotmail.com> wrote in message
news:ueGbMGZtFHA.2076@.TK2MSFTNGP14.phx.gbl...
> We have linked database servers using linked server feature. Is it a
> resource intensive setting? Any one has any comments and their experiences
> on this setup?
> SQL 2K.
> Joe
>
resource intensive setting? Any one has any comments and their experiences
on this setup?
SQL 2K.
JoeHere's a WebCast that focuses on Linked Server configuration, usage, and
troubleshooting
(http://support.microsoft.com/defaul...kb;en-us;326839). It should
give you a good overview. The link itself isn't resource intensive however
at run time, depending how data is used across the link, it will have some
impact on the individual query involved as some JOINS may need to be staged
in TempDB before being resolved against local tables. You also need to
carefully consider the security implications of your Linked Server
definition. Not that there's any pure security issues per-se however like
any other tool, when not properly configured and then exposed for public
consumption it could leave you data wide open.
--Brian
(Please reply to the newsgroups only.)
"JoeMathew" <Joe_Mathew@.hotmail.com> wrote in message
news:ueGbMGZtFHA.2076@.TK2MSFTNGP14.phx.gbl...
> We have linked database servers using linked server feature. Is it a
> resource intensive setting? Any one has any comments and their experiences
> on this setup?
> SQL 2K.
> Joe
>
Friday, March 9, 2012
server with Oracle
I installed the Oracle client on my computer, and I can connect to oracle databases using SqlPlus, however when I try setting up the linked server I get the following error after I try executing a query.
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: ORA-12560: TNS:protocol adapter error
]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: ORA-12560: TNS:protocol adapter error
]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
me to getting the same problem so u got the solution please tell to me
my Address:
A. Shiva Prasad
GIS Developer
MIDWEST INFO TECH Pvt Limited
70, kanakapura main road ,J.P. nagar 6th phase
opposite Family mart
Bangalore - INDIA
mail id : shiva.prasad@.midwestinfotech.com alternate mail : asp.347@.gmail.com
mobile : +919886451711
|||This looks more like a protocol adapter error. This indicates that Oracle client does not know what instance to connect to or what TNS alias to use. Try fixing the tnsname.ora file so that it points to the correct instance
server with Oracle
I installed the Oracle client on my computer, and I can connect to oracle databases using SqlPlus, however when I try setting up the linked server I get the following error after I try executing a query.
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: ORA-12560: TNS:protocol adapter error
]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].me to getting the same problem so u got the solution please tell to me
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: ORA-12560: TNS:protocol adapter error
]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].me to getting the same problem so u got the solution please tell to me
my Address:
A. Shiva Prasad
GIS Developer
MIDWEST INFO TECH Pvt Limited
70, kanakapura main road ,J.P. nagar 6th phase
opposite Family mart
Bangalore - INDIA
mail id : shiva.prasad@.midwestinfotech.com alternate mail : asp.347@.gmail.com
mobile : +919886451711
|||This looks more like a protocol adapter error. This indicates that Oracle client does not know what instance to connect to or what TNS alias to use. Try fixing the tnsname.ora file so that it points to the correct instance
server VS SQL server registration
Hi ,
Is there any difference between setting up a linked server and to register
a SQL server ?
I want to set up replication ,shld i be using a linked server or a
registered server or either one is ok
kindly advise
tks & rdgs
Hi,
There is a big diffrence between linked server and Registering a
server.
In linked server u can not see the graphical phase.Every thing u have
to do by code.
I registering a server u can do everything u do on th local server.
If u are going to do replication between diffrent server then u have to
use linked server.
else no use to create a linked server.
read bol for more information
hope this help
from
killer
|||Hi ,
I am currently doing a replication across different server using a
registered sever. it used to be successfuly but i got the general network
error so i am finding an alternative ways such as DTS , or using query
analyzer to copy the data over.
i'll try to do replication using a linked server then
tks & rdgs
"doller" wrote:
> Hi,
> There is a big diffrence between linked server and Registering a
> server.
> In linked server u can not see the graphical phase.Every thing u have
> to do by code.
> I registering a server u can do everything u do on th local server.
> If u are going to do replication between diffrent server then u have to
> use linked server.
> else no use to create a linked server.
>
> read bol for more information
> hope this help
> from
> killer
>
|||Hi ,
It seems that replication requires a registered SQL Server
rdgs
"maxzsim" wrote:
[vbcol=seagreen]
> Hi ,
> I am currently doing a replication across different server using a
> registered sever. it used to be successfuly but i got the general network
> error so i am finding an alternative ways such as DTS , or using query
> analyzer to copy the data over.
> i'll try to do replication using a linked server then
> tks & rdgs
> "doller" wrote:
|||Hi,
No replication doesnt require any registered server.
What type of replication u are using.
Tell me for what purpose u use replication.Becasue replication use too
much of resources.
If u do data transfer for few records or tables then better use DTS .
Hope this helps.
FRom
Killer
Is there any difference between setting up a linked server and to register
a SQL server ?
I want to set up replication ,shld i be using a linked server or a
registered server or either one is ok
kindly advise
tks & rdgs
Hi,
There is a big diffrence between linked server and Registering a
server.
In linked server u can not see the graphical phase.Every thing u have
to do by code.
I registering a server u can do everything u do on th local server.
If u are going to do replication between diffrent server then u have to
use linked server.
else no use to create a linked server.
read bol for more information
hope this help
from
killer
|||Hi ,
I am currently doing a replication across different server using a
registered sever. it used to be successfuly but i got the general network
error so i am finding an alternative ways such as DTS , or using query
analyzer to copy the data over.
i'll try to do replication using a linked server then
tks & rdgs
"doller" wrote:
> Hi,
> There is a big diffrence between linked server and Registering a
> server.
> In linked server u can not see the graphical phase.Every thing u have
> to do by code.
> I registering a server u can do everything u do on th local server.
> If u are going to do replication between diffrent server then u have to
> use linked server.
> else no use to create a linked server.
>
> read bol for more information
> hope this help
> from
> killer
>
|||Hi ,
It seems that replication requires a registered SQL Server
rdgs
"maxzsim" wrote:
[vbcol=seagreen]
> Hi ,
> I am currently doing a replication across different server using a
> registered sever. it used to be successfuly but i got the general network
> error so i am finding an alternative ways such as DTS , or using query
> analyzer to copy the data over.
> i'll try to do replication using a linked server then
> tks & rdgs
> "doller" wrote:
|||Hi,
No replication doesnt require any registered server.
What type of replication u are using.
Tell me for what purpose u use replication.Becasue replication use too
much of resources.
If u do data transfer for few records or tables then better use DTS .
Hope this helps.
FRom
Killer
server VS SQL server registration
Hi ,
Is there any difference between setting up a linked server and to register
a SQL server ?
I want to set up replication ,shld i be using a linked server or a
registered server or either one is ok
kindly advise
tks & rdgsHi,
There is a big diffrence between linked server and Registering a
server.
In linked server u can not see the graphical phase.Every thing u have
to do by code.
I registering a server u can do everything u do on th local server.
If u are going to do replication between diffrent server then u have to
use linked server.
else no use to create a linked server.
read bol for more information
hope this help
from
killer|||Hi ,
I am currently doing a replication across different server using a
registered sever. it used to be successfuly but i got the general network
error so i am finding an alternative ways such as DTS , or using query
analyzer to copy the data over.
i'll try to do replication using a linked server then
tks & rdgs
"doller" wrote:
> Hi,
> There is a big diffrence between linked server and Registering a
> server.
> In linked server u can not see the graphical phase.Every thing u have
> to do by code.
> I registering a server u can do everything u do on th local server.
> If u are going to do replication between diffrent server then u have to
> use linked server.
> else no use to create a linked server.
>
> read bol for more information
> hope this help
> from
> killer
>|||Hi ,
It seems that replication requires a registered SQL Server
rdgs
"maxzsim" wrote:
[vbcol=seagreen]
> Hi ,
> I am currently doing a replication across different server using a
> registered sever. it used to be successfuly but i got the general network
> error so i am finding an alternative ways such as DTS , or using query
> analyzer to copy the data over.
> i'll try to do replication using a linked server then
> tks & rdgs
> "doller" wrote:
>|||Hi,
No replication doesnt require any registered server.
What type of replication u are using.
Tell me for what purpose u use replication.Becasue replication use too
much of resources.
If u do data transfer for few records or tables then better use DTS .
Hope this helps.
FRom
Killer
Is there any difference between setting up a linked server and to register
a SQL server ?
I want to set up replication ,shld i be using a linked server or a
registered server or either one is ok
kindly advise
tks & rdgsHi,
There is a big diffrence between linked server and Registering a
server.
In linked server u can not see the graphical phase.Every thing u have
to do by code.
I registering a server u can do everything u do on th local server.
If u are going to do replication between diffrent server then u have to
use linked server.
else no use to create a linked server.
read bol for more information
hope this help
from
killer|||Hi ,
I am currently doing a replication across different server using a
registered sever. it used to be successfuly but i got the general network
error so i am finding an alternative ways such as DTS , or using query
analyzer to copy the data over.
i'll try to do replication using a linked server then
tks & rdgs
"doller" wrote:
> Hi,
> There is a big diffrence between linked server and Registering a
> server.
> In linked server u can not see the graphical phase.Every thing u have
> to do by code.
> I registering a server u can do everything u do on th local server.
> If u are going to do replication between diffrent server then u have to
> use linked server.
> else no use to create a linked server.
>
> read bol for more information
> hope this help
> from
> killer
>|||Hi ,
It seems that replication requires a registered SQL Server
rdgs
"maxzsim" wrote:
[vbcol=seagreen]
> Hi ,
> I am currently doing a replication across different server using a
> registered sever. it used to be successfuly but i got the general network
> error so i am finding an alternative ways such as DTS , or using query
> analyzer to copy the data over.
> i'll try to do replication using a linked server then
> tks & rdgs
> "doller" wrote:
>|||Hi,
No replication doesnt require any registered server.
What type of replication u are using.
Tell me for what purpose u use replication.Becasue replication use too
much of resources.
If u do data transfer for few records or tables then better use DTS .
Hope this helps.
FRom
Killer
server VS SQL server registration
Hi ,
Is there any difference between setting up a linked server and to register
a SQL server ?
I want to set up replication ,shld i be using a linked server or a
registered server or either one is ok
kindly advise
tks & rdgsHi,
There is a big diffrence between linked server and Registering a
server.
In linked server u can not see the graphical phase.Every thing u have
to do by code.
I registering a server u can do everything u do on th local server.
If u are going to do replication between diffrent server then u have to
use linked server.
else no use to create a linked server.
read bol for more information
hope this help
from
killer|||Hi ,
I am currently doing a replication across different server using a
registered sever. it used to be successfuly but i got the general network
error so i am finding an alternative ways such as DTS , or using query
analyzer to copy the data over.
i'll try to do replication using a linked server then
tks & rdgs
"doller" wrote:
> Hi,
> There is a big diffrence between linked server and Registering a
> server.
> In linked server u can not see the graphical phase.Every thing u have
> to do by code.
> I registering a server u can do everything u do on th local server.
> If u are going to do replication between diffrent server then u have to
> use linked server.
> else no use to create a linked server.
>
> read bol for more information
> hope this help
> from
> killer
>|||Hi ,
It seems that replication requires a registered SQL Server
rdgs
"maxzsim" wrote:
> Hi ,
> I am currently doing a replication across different server using a
> registered sever. it used to be successfuly but i got the general network
> error so i am finding an alternative ways such as DTS , or using query
> analyzer to copy the data over.
> i'll try to do replication using a linked server then
> tks & rdgs
> "doller" wrote:
> > Hi,
> >
> > There is a big diffrence between linked server and Registering a
> > server.
> > In linked server u can not see the graphical phase.Every thing u have
> > to do by code.
> > I registering a server u can do everything u do on th local server.
> > If u are going to do replication between diffrent server then u have to
> > use linked server.
> > else no use to create a linked server.
> >
> >
> > read bol for more information
> >
> > hope this help
> >
> > from
> > killer
> >
> >|||Hi,
No replication doesnt require any registered server.
What type of replication u are using.
Tell me for what purpose u use replication.Becasue replication use too
much of resources.
If u do data transfer for few records or tables then better use DTS .
Hope this helps.
FRom
Killer
Is there any difference between setting up a linked server and to register
a SQL server ?
I want to set up replication ,shld i be using a linked server or a
registered server or either one is ok
kindly advise
tks & rdgsHi,
There is a big diffrence between linked server and Registering a
server.
In linked server u can not see the graphical phase.Every thing u have
to do by code.
I registering a server u can do everything u do on th local server.
If u are going to do replication between diffrent server then u have to
use linked server.
else no use to create a linked server.
read bol for more information
hope this help
from
killer|||Hi ,
I am currently doing a replication across different server using a
registered sever. it used to be successfuly but i got the general network
error so i am finding an alternative ways such as DTS , or using query
analyzer to copy the data over.
i'll try to do replication using a linked server then
tks & rdgs
"doller" wrote:
> Hi,
> There is a big diffrence between linked server and Registering a
> server.
> In linked server u can not see the graphical phase.Every thing u have
> to do by code.
> I registering a server u can do everything u do on th local server.
> If u are going to do replication between diffrent server then u have to
> use linked server.
> else no use to create a linked server.
>
> read bol for more information
> hope this help
> from
> killer
>|||Hi ,
It seems that replication requires a registered SQL Server
rdgs
"maxzsim" wrote:
> Hi ,
> I am currently doing a replication across different server using a
> registered sever. it used to be successfuly but i got the general network
> error so i am finding an alternative ways such as DTS , or using query
> analyzer to copy the data over.
> i'll try to do replication using a linked server then
> tks & rdgs
> "doller" wrote:
> > Hi,
> >
> > There is a big diffrence between linked server and Registering a
> > server.
> > In linked server u can not see the graphical phase.Every thing u have
> > to do by code.
> > I registering a server u can do everything u do on th local server.
> > If u are going to do replication between diffrent server then u have to
> > use linked server.
> > else no use to create a linked server.
> >
> >
> > read bol for more information
> >
> > hope this help
> >
> > from
> > killer
> >
> >|||Hi,
No replication doesnt require any registered server.
What type of replication u are using.
Tell me for what purpose u use replication.Becasue replication use too
much of resources.
If u do data transfer for few records or tables then better use DTS .
Hope this helps.
FRom
Killer
Wednesday, March 7, 2012
server via ODBC - help!
Hi All
I have set up several linked SQL servers which work ok - but I'm having
trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
The ODBC points to an 'Alchemy' database and uses an Alchemy driver
ironically i can set up linked tables in an Access DB, via ODBC - and I can
pull the same data into Excel via ODBC - so there is no problem connecting t
o
Alchemy using other MS apps.
When I add the linked server in SQL, it appears to be added but no tables
are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
returns an error "Cannot initialize the data source object of OLE DB provide
r
'MSDASQL' "
Its driving me crazy...Anyone have any ideas'
Thanks in advanceMake sure the driver is compatible with the MDAC version on
the SQL Server box. Make sure you are using the latest
driver. Make sure the driver is correctly installed on the
SQL Server box.
Sometimes those issues can be related to issues specific to
the driver and interactions with service accounts. Try
logging onto the server using the service account for SQL
Server and install the driver while logged in under the
service account SQL Server is running under.
-Sue
On Thu, 28 Sep 2006 15:29:02 -0700, grasshopper
<nospam@.nospam.com> wrote:
>Hi All
>I have set up several linked SQL servers which work ok - but I'm having
>trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
>The ODBC points to an 'Alchemy' database and uses an Alchemy driver
>ironically i can set up linked tables in an Access DB, via ODBC - and I can
>pull the same data into Excel via ODBC - so there is no problem connecting
to
>Alchemy using other MS apps.
>When I add the linked server in SQL, it appears to be added but no tables
>are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
>returns an error "Cannot initialize the data source object of OLE DB provid
er
>'MSDASQL' "
>Its driving me crazy...Anyone have any ideas'
>Thanks in advance
I have set up several linked SQL servers which work ok - but I'm having
trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
The ODBC points to an 'Alchemy' database and uses an Alchemy driver
ironically i can set up linked tables in an Access DB, via ODBC - and I can
pull the same data into Excel via ODBC - so there is no problem connecting t
o
Alchemy using other MS apps.
When I add the linked server in SQL, it appears to be added but no tables
are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
returns an error "Cannot initialize the data source object of OLE DB provide
r
'MSDASQL' "
Its driving me crazy...Anyone have any ideas'
Thanks in advanceMake sure the driver is compatible with the MDAC version on
the SQL Server box. Make sure you are using the latest
driver. Make sure the driver is correctly installed on the
SQL Server box.
Sometimes those issues can be related to issues specific to
the driver and interactions with service accounts. Try
logging onto the server using the service account for SQL
Server and install the driver while logged in under the
service account SQL Server is running under.
-Sue
On Thu, 28 Sep 2006 15:29:02 -0700, grasshopper
<nospam@.nospam.com> wrote:
>Hi All
>I have set up several linked SQL servers which work ok - but I'm having
>trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
>The ODBC points to an 'Alchemy' database and uses an Alchemy driver
>ironically i can set up linked tables in an Access DB, via ODBC - and I can
>pull the same data into Excel via ODBC - so there is no problem connecting
to
>Alchemy using other MS apps.
>When I add the linked server in SQL, it appears to be added but no tables
>are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
>returns an error "Cannot initialize the data source object of OLE DB provid
er
>'MSDASQL' "
>Its driving me crazy...Anyone have any ideas'
>Thanks in advance
server via ODBC - help!
Hi All
I have set up several linked SQL servers which work ok - but I'm having
trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
The ODBC points to an 'Alchemy' database and uses an Alchemy driver
ironically i can set up linked tables in an Access DB, via ODBC - and I can
pull the same data into Excel via ODBC - so there is no problem connecting to
Alchemy using other MS apps.
When I add the linked server in SQL, it appears to be added but no tables
are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
returns an error "Cannot initialize the data source object of OLE DB provider
'MSDASQL' "
Its driving me crazy...Anyone have any ideas?
Thanks in advance
Make sure the driver is compatible with the MDAC version on
the SQL Server box. Make sure you are using the latest
driver. Make sure the driver is correctly installed on the
SQL Server box.
Sometimes those issues can be related to issues specific to
the driver and interactions with service accounts. Try
logging onto the server using the service account for SQL
Server and install the driver while logged in under the
service account SQL Server is running under.
-Sue
On Thu, 28 Sep 2006 15:29:02 -0700, grasshopper
<nospam@.nospam.com> wrote:
>Hi All
>I have set up several linked SQL servers which work ok - but I'm having
>trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
>The ODBC points to an 'Alchemy' database and uses an Alchemy driver
>ironically i can set up linked tables in an Access DB, via ODBC - and I can
>pull the same data into Excel via ODBC - so there is no problem connecting to
>Alchemy using other MS apps.
>When I add the linked server in SQL, it appears to be added but no tables
>are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
>returns an error "Cannot initialize the data source object of OLE DB provider
>'MSDASQL' "
>Its driving me crazy...Anyone have any ideas?
>Thanks in advance
I have set up several linked SQL servers which work ok - but I'm having
trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
The ODBC points to an 'Alchemy' database and uses an Alchemy driver
ironically i can set up linked tables in an Access DB, via ODBC - and I can
pull the same data into Excel via ODBC - so there is no problem connecting to
Alchemy using other MS apps.
When I add the linked server in SQL, it appears to be added but no tables
are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
returns an error "Cannot initialize the data source object of OLE DB provider
'MSDASQL' "
Its driving me crazy...Anyone have any ideas?
Thanks in advance
Make sure the driver is compatible with the MDAC version on
the SQL Server box. Make sure you are using the latest
driver. Make sure the driver is correctly installed on the
SQL Server box.
Sometimes those issues can be related to issues specific to
the driver and interactions with service accounts. Try
logging onto the server using the service account for SQL
Server and install the driver while logged in under the
service account SQL Server is running under.
-Sue
On Thu, 28 Sep 2006 15:29:02 -0700, grasshopper
<nospam@.nospam.com> wrote:
>Hi All
>I have set up several linked SQL servers which work ok - but I'm having
>trouble setting up a linked server via ODBC (in either SQL 2000, or 2005).
>The ODBC points to an 'Alchemy' database and uses an Alchemy driver
>ironically i can set up linked tables in an Access DB, via ODBC - and I can
>pull the same data into Excel via ODBC - so there is no problem connecting to
>Alchemy using other MS apps.
>When I add the linked server in SQL, it appears to be added but no tables
>are displayed (enterprise mgr) and OPENQUERY in SQL2005 management studio
>returns an error "Cannot initialize the data source object of OLE DB provider
>'MSDASQL' "
>Its driving me crazy...Anyone have any ideas?
>Thanks in advance
server to Postgres
Hi
Can anyone help me with this.. driving me nuts.
when setting up a linked server to Postgres 7.3.1 (specifics*) I can see the tables in Enterprise Manager but in Query Analyzer i get this error when doing the below queries
SELECT * FROM OPENQUERY(POSTGRES_1,'select * from dbo.TestTable')
OR
SELECT * FROM OPENQUERY(POSTGRES_1,'select * from TestTable')
Error:
Server: Msg 7357, Level 16, State 2, Line 1
Could not process object 'select id,value_char from dbo.Test_Default_1'. The OLE DB provider 'MSDASQL' indicates that the object has no columns.
OLE DB error trace [Non-interface error: OLE DB provider unable to process object, since the object has no columnsProviderName='MSDASQL', Query=select id,value_char from dbo.Test_Default_1'].http://support.microsoft.com/default.aspx?scid=kb;EN-US;270119 to followup the issue and resolve.|||Hi Satya,
I have seen this article before and it does not help with this issue as I cannot select data even using the pass through query syntax shown. Is there anyone you know that has any light on this problem. Getting data through the ODBC connection is fine it's just that the OPENQUERY() returns the error.
Regards...|||The only option to suspect is about compatible/proper driver from Postgres, have you tried on Postgres website for any information.|||I have and I downloaded the version of the ODBC which should be compatible with the current version of Postgres which is 7.3.1. It just keeps bugging me that this is possible an issue with OLEDB for ODBC rather than the ODBC Driver itself but I can't pin point it.|||Try with latest version of MDAC and OLEDB provider.|||Will try...
Can anyone help me with this.. driving me nuts.
when setting up a linked server to Postgres 7.3.1 (specifics*) I can see the tables in Enterprise Manager but in Query Analyzer i get this error when doing the below queries
SELECT * FROM OPENQUERY(POSTGRES_1,'select * from dbo.TestTable')
OR
SELECT * FROM OPENQUERY(POSTGRES_1,'select * from TestTable')
Error:
Server: Msg 7357, Level 16, State 2, Line 1
Could not process object 'select id,value_char from dbo.Test_Default_1'. The OLE DB provider 'MSDASQL' indicates that the object has no columns.
OLE DB error trace [Non-interface error: OLE DB provider unable to process object, since the object has no columnsProviderName='MSDASQL', Query=select id,value_char from dbo.Test_Default_1'].http://support.microsoft.com/default.aspx?scid=kb;EN-US;270119 to followup the issue and resolve.|||Hi Satya,
I have seen this article before and it does not help with this issue as I cannot select data even using the pass through query syntax shown. Is there anyone you know that has any light on this problem. Getting data through the ODBC connection is fine it's just that the OPENQUERY() returns the error.
Regards...|||The only option to suspect is about compatible/proper driver from Postgres, have you tried on Postgres website for any information.|||I have and I downloaded the version of the ODBC which should be compatible with the current version of Postgres which is 7.3.1. It just keeps bugging me that this is possible an issue with OLEDB for ODBC rather than the ODBC Driver itself but I can't pin point it.|||Try with latest version of MDAC and OLEDB provider.|||Will try...
Subscribe to:
Posts (Atom)