64-bit linkder server to Sybase



Hi,

From my research, it appears that it is not possible to have a linked server
created in Microsoft SQL Server 2005 x64 use a 32-bit DSN (i.e. created with
a 32 bit driver). The answer is that I need to create a 64-bit DSN in order
to create a linked server in Microsoft SQL Server 2005 x64 that connects to
an ASE 12.5.x database. The problem is that many vendors (i.e. Sybase) do
not have a 64-bit driver.

Any one using Data Direct to connect to Sybase from SQL Server 2005 x64?

Thanks,

Rocco M.

(posted in microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.clients and microsoft.public.sqlserver.connect)


.



Relevant Pages

  • RE: [dbi] Re: MsSQL DBD::ODBC IsNull and undef
    ... I'd guess this is because the SQL Server ODBC driver is looking at your ... Martin J. Evans ... can you run your test script again but creating an OOB log file ...
    (perl.dbi.users)
  • Re: Scheduling DTS job
    ... If you try to transfer the same rowsfrom SQL Server to SQL Server ... > How do i see if there is any difference in the driver ... >>> The SQL server agent is running as Local System Account. ... >>> Nothing has been changed in sybase box. ...
    (microsoft.public.sqlserver.dts)
  • Re: Padding using Type 4 Drivers
    ... |> value than what you have set in SQL Server 2000. ... |> settings that you require. ... |> Are you using the Microsoft JDBC driver or a third-party driver?. ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: MsSQL DBD::ODBC IsNull and undef
    ... Martin J. Evans ... On 26-Jul-2005 Brian Becker wrote: ... > ensure you tell your driver the type of the column in bind_col. ... > I'd guess this is because the SQL Server ODBC driver is looking at your ...
    (perl.dbi.users)
  • Re: XA and 2000 backwards compatibility
    ... We haven't deployed the SQL2K XA driver either, so this should work for us. ... I am going through the documentation for the SQL Server driver. ... and enable XA transactions in MSDTC on the SQL Server ... Goto MSDTC tab on properties, click "Security Configuration" button, ...
    (microsoft.public.sqlserver.jdbcdriver)