Hello clockwatcher, Can you give me the version of Cache and Intersystems ODBC driver are you using? I wonder why it is not running for me when it is for you.
I've run it against two server versions (both worked w/o problems):
Cache for UNIX (IBM PowerPC) 4.1.16 (Build 233_3 + Adhoc 1341) Sat Apr 3 2004 08:16:46 EST
Cache for Windows NT (Intel/P4) 5.0.13 (Build 5607) Thu Dec 30 2004 13:20:23 EST
The ODBC driver on my SQL server: Intersystems ODBC 5.00.5607.00
I have Cache 2007 running at home. I'll see if I have any different results with it. My guess would be the newer ODBC driver. If I get a few minutes later tonight, I'll play around with it and see if I can duplicate the problem.
I use ODBC for LInked server. Is there any way to use intersystem's managed dotnet provider for connecting linked server in Sql Server? intersystem's managed dotnet provider does not come as a provider in the list of providers for Linked Servers. It will be great if there is one.
I am working in a project transferring data from Cache Database to Sql Server everyday. Some tables fail with link server or ODBC connection, but could get the data using intersystems's managed dotnet provider.
I wonder if there is a way to connect the Sql Server 2005 Link server using intersystems managed dotnet provider.
I don't believe it's possible to set up a linked server using a dotnet managed provider.
Transferring sounds like you're actually putting data into or out of one database into the other. If that's what you're after, why don't you do your link the other way around. Link the SQL Server to Cache. And do the the transfer from the Cache side of things. You'll probably have better luck with that.
I do not have enough permissions at the Cache server and also I do not have good knowledge on Cache. I asked them for permission for Remote administration of the database. I do not know it will help.