I am currently configuring and testing a new SQL server:
SQL 2000 Enterprise Edition SP3a
Windows 2003 Enterprise Edition
MDAC 2.8
I am experiencing some strange behaviour with linked SQL
servers from the new server.
This 1st SQL stmt below works OK from the new server
select contact_id from ls.lat_prod_ed.dbo.contact
This 2nd SQL stmt fails on the new server with general
network error after approx 25 seconds.
select * from ls.lat_prod_ed.dbo.contact
Server: Msg 11, Level 16, State 1, Line 5
General network error. Check your network documentation.
A SQL profiler trace shows the following error being
raised:
OLE/DB Provider 'Unknown' ::ReleaseSchemaLock returned
0x80040e96: OLE DB provider Unknown supported the Schema
Lock interface, but returned0x80040e96 for
ReleaseSchemaLock .
The target linked server (ls) is running SQL 2000 sp3a
Standard Edition on Windows 2000 sp3. It was on MDAC 2.7
and I've now upgraded it to MDAC 2.8 but get the same
error.
I've run component checker on both servers and it reports
everything OK.
The SQL statement that fails, works OK when run from
another SQL server (SQL 2000 Enterprise Edition sp3a,
Windows 2000 Advanced server sp3 and MDAC 2.7 sp1 refresh)
and pointing to the same target linked server (ls).
Thanks in advance
Greg DaviesDoes openquery work? Does this happen only for '*' or for other columns of
the table as well? How was this linked server created? Through enterprise
manager?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Showing posts with label configuring. Show all posts
Showing posts with label configuring. Show all posts
Wednesday, March 21, 2012
servers and MDAC 2.8
Labels:
configuring,
database,
edition,
editionmdac,
enterprise,
experiencing,
linked,
mdac,
microsoft,
mysql,
oracle,
server,
servers,
serversql,
sp3awindows,
sql
servers and MDAC 2.8
I am currently configuring and testing a new SQL server:
SQL 2000 Enterprise Edition SP3a
Windows 2003 Enterprise Edition
MDAC 2.8
I am experiencing some strange behaviour with linked SQL
servers from the new server.
This 1st SQL stmt below works OK from the new server
select contact_id from ls.lat_prod_ed.dbo.contact
This 2nd SQL stmt fails on the new server with general
network error after approx 25 seconds.
select * from ls.lat_prod_ed.dbo.contact
Server: Msg 11, Level 16, State 1, Line 5
General network error. Check your network documentation.
A SQL profiler trace shows the following error being
raised:
OLE/DB Provider 'Unknown' ::ReleaseSchemaLock returned
0x80040e96: OLE DB provider Unknown supported the Schema
Lock interface, but returned0x80040e96 for
ReleaseSchemaLock .
The target linked server (ls) is running SQL 2000 sp3a
Standard Edition on Windows 2000 sp3. It was on MDAC 2.7
and I've now upgraded it to MDAC 2.8 but get the same
error.
I've run component checker on both servers and it reports
everything OK.
The SQL statement that fails, works OK when run from
another SQL server (SQL 2000 Enterprise Edition sp3a,
Windows 2000 Advanced server sp3 and MDAC 2.7 sp1 refresh)
and pointing to the same target linked server (ls).
Thanks in advance
Greg Davies
Does openquery work? Does this happen only for '*' or for other columns of
the table as well? How was this linked server created? Through enterprise
manager?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
sql
SQL 2000 Enterprise Edition SP3a
Windows 2003 Enterprise Edition
MDAC 2.8
I am experiencing some strange behaviour with linked SQL
servers from the new server.
This 1st SQL stmt below works OK from the new server
select contact_id from ls.lat_prod_ed.dbo.contact
This 2nd SQL stmt fails on the new server with general
network error after approx 25 seconds.
select * from ls.lat_prod_ed.dbo.contact
Server: Msg 11, Level 16, State 1, Line 5
General network error. Check your network documentation.
A SQL profiler trace shows the following error being
raised:
OLE/DB Provider 'Unknown' ::ReleaseSchemaLock returned
0x80040e96: OLE DB provider Unknown supported the Schema
Lock interface, but returned0x80040e96 for
ReleaseSchemaLock .
The target linked server (ls) is running SQL 2000 sp3a
Standard Edition on Windows 2000 sp3. It was on MDAC 2.7
and I've now upgraded it to MDAC 2.8 but get the same
error.
I've run component checker on both servers and it reports
everything OK.
The SQL statement that fails, works OK when run from
another SQL server (SQL 2000 Enterprise Edition sp3a,
Windows 2000 Advanced server sp3 and MDAC 2.7 sp1 refresh)
and pointing to the same target linked server (ls).
Thanks in advance
Greg Davies
Does openquery work? Does this happen only for '*' or for other columns of
the table as well? How was this linked server created? Through enterprise
manager?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
sql
Labels:
configuring,
database,
edition,
editionmdac,
enterprise,
experiencing,
linked,
mdac,
microsoft,
mysql,
oracle,
server,
servers,
serversql,
sp3awindows,
sql
Monday, March 12, 2012
servers
Hello,
Is there any limit to the number of linked servers i can add via EM?. where can i find more info on adding/configuring linked servers in MSSQL2k and the limitations/drawbacks if any?
Thanks in advance..one limitation of linked servers I discovered recently is that loopback scenarios are not supported by MS, even though they often work. what I mean by loopback is a LS that points to itself.
One case I know that is broken in a loopback scenario is this:
INSERT INTO localtable EXEC LoopbackLinkedServer.dbo.RemoteSproc
as is detailed here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?postid=124137&siteid=1
Linked servers are very useful. why couldn't MS get the obvious use case of loopback to work? :(
I should note that the case above is broken on 2005. it may work on 2000, I haven't tried it.
Is there any limit to the number of linked servers i can add via EM?. where can i find more info on adding/configuring linked servers in MSSQL2k and the limitations/drawbacks if any?
Thanks in advance..one limitation of linked servers I discovered recently is that loopback scenarios are not supported by MS, even though they often work. what I mean by loopback is a LS that points to itself.
One case I know that is broken in a loopback scenario is this:
INSERT INTO localtable EXEC LoopbackLinkedServer.dbo.RemoteSproc
as is detailed here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?postid=124137&siteid=1
Linked servers are very useful. why couldn't MS get the obvious use case of loopback to work? :(
I should note that the case above is broken on 2005. it may work on 2000, I haven't tried it.
Subscribe to:
Posts (Atom)