I'm connecting to sysbase via odbc and oledb - mostly oledb.
"Kayda" wrote:
> Hi:
>
> I'm finding with SSIS 2005 that the most basic functionality--being
> able to connect to datasources--is very difficult. I've tried to
> connect to Sybase via ODBC and OLEDB and had different problems each
> way. As a test I tried an ODBC connection to Access and it also had
> problems. I've seen other posts but nothing that really helps.
>
> Here is what I've tried:
> 1. I understand that now if you want to use an ODBC source, you create
> an ODBC connection manager and then use a "DataReader Source" that
> uses that connection manager. I tried this via ODBC to my Sybase
> database, but got this error:
>
> "Error at pump MyPump [DataReader Source xxxx]: Cannot acquire a
> managed connection from the run-time connection manager"
>
> This connection manager tested fine, and I have no problem querying
> via an ODBC testing tool.
>
> 2. I tried an ODBC connection to MS Access, and got the same problem,
> I think this must be a problem with SSIS. I found this link:
>
>
http://blogs.sqlxml.org/bryantlikes/archive/2004/07/28/876.aspx >
> but I'm not sure what he means by "Change Qualifier". Where exactly do
> I put that extra text?
>
> 3. I tried an OLEDB connection with Sybase. I had setup a Sybase OLEDB
> source in the Sybase OLEDB tool, and then I setup a connection manager
> in SSIS, which tested fine. I created an OLEDB source in SSIS, and
> used this connection manager.
>
> When I am setting up my OLEDB source, when I click on the "Name of the
> table or view" drop down list, it thinks and then gives me my list of
> Sybase tables. Then when I click on anything else, like Preview or try
> to go to the "columns" tab, I get an error:
>
> Error at pump mytable[OLE DB Source[xxxx]]: Opening a rowset for
> ""dbo."."mytable"" failed. Check that the object exists in the
> database.
>
> Strange, since it gave me that table in the dropdown-of course it
> exists!
>
> I am happy to connect either via OLEDB or ODBC. Any advice on either
> would be appreciated-this is frustrating because connecting to
> datasources is the most basic thing in an ETL tool--it shouldn't be
> this difficult.
>
> Thanks,
> Kayda
>