Hi,

On one side, I have a Sybase 12.5 32 bits Server running on AIX 5.1
(maintenance level 3). On the other, I've got W2000 5.00.2195 (SP2)
with SQL Server Standard Edition, Product Version 8.00.534 (SP2),
having installed MDAC 2.6.

I connect to the Sybase 12.5 database using Merant ASE ODBC driver for
Sybase 12.5, and using the Microsoft OLE DB Provider for SQL Server
that comes with this SQLServer version.

I try to pump over data from Sybase to SQLServer to one table at a
SQLServer user database, using a package containing a select statement
on a View on the Sybase Server side, using an ODBC 12.5 System DSN
pointing to the Sybase server. All privileges are set correctly on
either side and the ODBC datasource test gives an 'OK' on trying to
reach the Sybase Server.

When I do PREVIEW, I get a resultset alright, however, when I actually
run the package as a scheduled job, its keeps on running infinitely
until manually killed. No data at all is inserted in the the SQLServer
table.

Strange thing is, the same processes is running without any
complications on a W2000 5.00.2195 (SP3), MDAC 2.7 system, with the
same SQLServer connecting to the same Sybase Server but using Merant
ASE ODBC 12.0 instead of ODBC 12.5.

How come?

Any help will be greatly appreciated.

Martijn Rutte

Same permissions for the SQL Server Agent account ?

http://support.microsoft.com/?kbid=269074


--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Martijn Rutte" <opales (AT) zonnet (DOT) nl> wrote

Martin,

If I were you, I wouldn't attempt to connect from MS
products to Sybase via anything which requires Open Client.

In the mid 90's, Sybase were opposing MS-Visual Basic by
promoting Powerbuilder and native drivers. They were not
at all interested in MS-style connectivity such as ODBC.
They succeeded quite well, and there are a large number of
VB/VBA applications misbehaving against a Sybase backend.

Recently, Sybase has seen the light, and have purchased an
OleDB driver from a third party. Try to get your hands on
version 2.7 of AseOleDbProvider. It self-standing, i.e.
requires no Open Client. It works perfectly on 12.0, with
DTS and VBA programs. For DTS, you will need to
preconfigure a data source, just like you would do with
ODBC. ( VBA programs connect can directly to server:ort,
I really like this )

Sybase distribute this driver as part of their client setup
CD. Ask your DBA, or contact the original vendor,
http://www.datadirect-technologies.com If you still
cannot get it, just send me an email (remove portion in
capitals).

Andrew

Hi Allan,

Exactly the same permissions.

Martijn

"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Hi Andrew,

Sounds reasonable, the thing is, however, that I haven't got much to
choose. If had had a choice, I wouldn't have used SQLServer DTS at
all, or SQLServer for that matter.

Anyway, we now installed ASE ODBC 12.0 on the system and DTS is
running, i.e., data can be copied from sybase to sqlserver.

Strange world, ICT.

Martijn

"Andrew Schonberger" <andrewsc (AT) internode (DOT) NO.SPAM.on.net> wrote