January 14, 2009 at 8:13 am
I almost hate to ask this but…..
Does anyone have any experience with linked servers using OLEDB to Sybase?
I have 2 Sybase servers, FAST1 and FAST2.
I defined 2 OLEDB connections on my SQL Server to go to the respective Sybase servers.
I created 2 linked servers on SQL Server, LS_FAST1 and LS_FAST2.
The problem is both linked servers go to FAST1.
It seems that regardless of what is on the Linked Server the connection always go to whichever name is first in the OLEDB config tool on the server.
January 14, 2009 at 8:29 am
What OLEDB Config tool are you using?
Most of the Sybase OLEDB problems I have run into (and it was a big list) were all because of poorly written OLEDB drivers for Sybase. I never used any that needed some OLEDB configuration tool, so I am not sure what you are using. The ones I used all just required an install of the drivers and then an appropriate OLEDB connection string in the linked server.
Can you post your linked server connection information (after removing passwrods, of course)?
January 14, 2009 at 8:42 am
I'm using the Sybase OLEDB config tool that was installed with the Sybase client on the server.
I get the same issue using SQL 2000 so I suspect its the OLEDB definitions on the server, but I'm not sure.
Here are the Linked server scripts;
/****** Object: LinkedServer [FASTDB1_OLEDB] Script Date: 01/14/2009 10:40:15 ******/
EXEC master.dbo.sp_addlinkedserver @server = N'FASTDB1_OLEDB', @srvproduct=N'Sybase', @provider=N'Sybase.ASEOLEDBProvider', @datasrc=N'B_FASTDB1_PROD'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'FASTDB1_OLEDB',@useself=N'False',@locallogin=NULL,@rmtuser=N'caars_prxy',@rmtpassword='########'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB1_OLEDB', @optname=N'use remote collation', @optvalue=N'true'
/****** Object: LinkedServer [FASTDB2_OLEDB] Script Date: 01/14/2009 10:40:34 ******/
EXEC master.dbo.sp_addlinkedserver @server = N'FASTDB2_OLEDB', @srvproduct=N'Sybase', @provider=N'Sybase.ASEOLEDBProvider', @datasrc=N'C_FASTDB2_PROD'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'FASTDB2_OLEDB',@useself=N'False',@locallogin=NULL,@rmtuser=N'caars_prxy',@rmtpassword='########'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'FASTDB2_OLEDB', @optname=N'use remote collation', @optvalue=N'true'
January 14, 2009 at 8:53 am
Not a Sybase OLEDB provider I have used, but it looks like something wrong with the provider. You should contact the company that sold it to you.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply