dbTalk Databases Forums  

Import from Sybase SQL Anywhere 9

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Import from Sybase SQL Anywhere 9 in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mark Huisinga
 
Posts: n/a

Default Import from Sybase SQL Anywhere 9 - 06-19-2006 , 02:53 AM






Hi,

I'm trying to import data into sql 2005 from sybase sql anywhere 9
(9.0.2.3320) using DTS (using the asademo db). I can select the tables I
want to import but during the actual import on Setting Source Connection I
always get an OLE DB Error :

Could not connect source component.

Error 0xc0202009: Source - contact[1]: An OLE DB error has occured. Error
code : 0x80040E21

Error 0xc020204a: Source - contact[1]: Unabtle to retrieve column
information from the data source.
Make sure your target table in the database is available.

The thing is DTS should create the target table for me. Does anybody have an
idea of what is going wrong here ?




Reply With Quote
  #2  
Old   
AT
 
Posts: n/a

Default RE: Import from Sybase SQL Anywhere 9 - 06-19-2006 , 04:43 AM






Hello Mark,

I found similar issue reported and it seems to be caused by olddb driver
from sybase.

I've been reading the .NET connectivity papers on ianywhere.com and
searching the Sybase newsgroups for information on configuring the Sybase
OLEDB driver. I noticed almost all of the newsgroups support for
configuring the SQL Anywhere OLEDB providers was provided by the
ianywhere.com support staff.

Most of these technical papers and discussion contain the user name and
password in the Provider String parameter.

Migrating a Microsoft Access Application into a .NET Solution that Uses SQL
Anywhere
<http://www.ianywhere.com/developer/s...ner/migrate_ac
cess.html>

Provider=ASAProv.90;User ID=uid Password=pwd

http://www.ianywhere.com/developer

About the .NET Data Provider for SQL Anywhere Studio
-------------------------------------------------------
SQL Anywhere's strong tradition of the .NET Framework support in its data
management and data synchronization technologies is further enhanced with
its newly
announced support for ADO.NET 2.0 and integration with Visual Studio 2005.
The new ADO.NET 2.0 provider allows native access to SQL Anywhere data
management
technology. Integration features with Visual Studio 2005 will make it easy
for developers to build data-driven .NET application for frontline
environments.

You may want to contact their support to see if there is any updated driver
to work around this issue.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===



This posting is provided "AS IS" with no warranties, and confers no rights.



Reply With Quote
  #3  
Old   
Mark Huisinga
 
Posts: n/a

Default Re: Import from Sybase SQL Anywhere 9 - 06-19-2006 , 07:11 AM



Hi Peter,

I just tried it with the new (beta) version of sql anywhere, version 10.
This still gives me exactly the same error.
It seems unlikely that the same problem also exists in the newest version of
their oledb drivers.

I also read similar post regarding this issue but on none of these posts
there is a workable answer.
Since this oledb provider does work when using sql 2000 how can we be sure
that the problem is not in ssis ?

Kind regards,

Mark Huisinga

""privatenews"" <petery (AT) online (DOT) microsoft.com> schreef in bericht
newsl7LRT4kGHA.5700 (AT) TK2MSFTNGXA01 (DOT) phx.gbl...
Quote:
Hello Mark,

I found similar issue reported and it seems to be caused by olddb driver
from sybase.

I've been reading the .NET connectivity papers on ianywhere.com and
searching the Sybase newsgroups for information on configuring the Sybase
OLEDB driver. I noticed almost all of the newsgroups support for
configuring the SQL Anywhere OLEDB providers was provided by the
ianywhere.com support staff.

Most of these technical papers and discussion contain the user name and
password in the Provider String parameter.

Migrating a Microsoft Access Application into a .NET Solution that Uses
SQL
Anywhere
http://www.ianywhere.com/developer/s...ner/migrate_ac
cess.html

Provider=ASAProv.90;User ID=uid Password=pwd

http://www.ianywhere.com/developer

About the .NET Data Provider for SQL Anywhere Studio
-------------------------------------------------------
SQL Anywhere's strong tradition of the .NET Framework support in its data
management and data synchronization technologies is further enhanced with
its newly
announced support for ADO.NET 2.0 and integration with Visual Studio 2005.
The new ADO.NET 2.0 provider allows native access to SQL Anywhere data
management
technology. Integration features with Visual Studio 2005 will make it easy
for developers to build data-driven .NET application for frontline
environments.

You may want to contact their support to see if there is any updated
driver
to work around this issue.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===



This posting is provided "AS IS" with no warranties, and confers no
rights.





Reply With Quote
  #4  
Old   
Mark Huisinga
 
Posts: n/a

Default Re: Import from Sybase SQL Anywhere 9 - 06-19-2006 , 10:54 AM



I have tried accessing the data using oledb from code (C#) and that goes
without any problem. So I think the problem has to be somewhere in SSIS.


"Mark Huisinga" <mhuisinga (AT) newsgroups (DOT) nospam> schreef in bericht
news:Ovwlg.59145$Ue7.38878 (AT) aphrodite (DOT) ..
Quote:
Hi Peter,

I just tried it with the new (beta) version of sql anywhere, version 10.
This still gives me exactly the same error.
It seems unlikely that the same problem also exists in the newest version
of their oledb drivers.

I also read similar post regarding this issue but on none of these posts
there is a workable answer.
Since this oledb provider does work when using sql 2000 how can we be sure
that the problem is not in ssis ?

Kind regards,

Mark Huisinga

""privatenews"" <petery (AT) online (DOT) microsoft.com> schreef in bericht
newsl7LRT4kGHA.5700 (AT) TK2MSFTNGXA01 (DOT) phx.gbl...
Hello Mark,

I found similar issue reported and it seems to be caused by olddb driver
from sybase.

I've been reading the .NET connectivity papers on ianywhere.com and
searching the Sybase newsgroups for information on configuring the Sybase
OLEDB driver. I noticed almost all of the newsgroups support for
configuring the SQL Anywhere OLEDB providers was provided by the
ianywhere.com support staff.

Most of these technical papers and discussion contain the user name and
password in the Provider String parameter.

Migrating a Microsoft Access Application into a .NET Solution that Uses
SQL
Anywhere
http://www.ianywhere.com/developer/s...ner/migrate_ac
cess.html

Provider=ASAProv.90;User ID=uid Password=pwd

http://www.ianywhere.com/developer

About the .NET Data Provider for SQL Anywhere Studio
-------------------------------------------------------
SQL Anywhere's strong tradition of the .NET Framework support in its data
management and data synchronization technologies is further enhanced with
its newly
announced support for ADO.NET 2.0 and integration with Visual Studio
2005.
The new ADO.NET 2.0 provider allows native access to SQL Anywhere data
management
technology. Integration features with Visual Studio 2005 will make it
easy
for developers to build data-driven .NET application for frontline
environments.

You may want to contact their support to see if there is any updated
driver
to work around this issue.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===



This posting is provided "AS IS" with no warranties, and confers no
rights.







Reply With Quote
  #5  
Old   
AT
 
Posts: n/a

Default Re: Import from Sybase SQL Anywhere 9 - 06-20-2006 , 03:09 AM



Hello,

It seems compatiblity issue between SSIS and the oledb provider. To find
out the root cause of this issue we may need to live debug/analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. I recommend that you open a Support incident with
Microsoft Product Support Services so that a dedicated Support Professional
can assist with this case. If you need any help in this regard, please let
me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp

Also, it is suggested that we also include support for the oledb provider
since they know more details.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.