Error message when connecting to Sybase from SSIS on 64bit server
(Sorry, this is supposed to be in the SSIS forum, not XSL/XML)
I am quite new to SSIS so please bear with me if I use incorrect terminology.
I developed a SSIS package on MY PC and it works fine. But I'm having trouble when it runs on the server.
On our SSIS server (which is a 64 bit server where we installed SQL Server 2008) we have a series of ODBC connections configured using the Adaptive Server Enterprise. I have configured 32-bit ODBC connections and these do seem to be available to SSIS via ADO.net.
I created a data flow task and linked my sybase database to the ADO.net source connection. The query I used as my data source was a stored procedure call, i.e.:
When I click on Preview, generally first time in I get an error message like this:
Error at Data Flow Task ADO NET Source: System.AccessViolationException: Attempted to read or write protected memory.
Next time it seems to work OK and I get rows back. Clicking on the 'columns' are doesn't show me any output. If I then connect the source to a data flow transformation such as a 'Row Sampling' task it claims there are no input columns.
If I then click on the ADO.NET Source again I get a message saying, 'The component is not in a valid state. Do you want the component to fix itself automatically?'. If I say yes I get the error message again.
Can anyone suggest what I'm doing wrong? I'm sure it is something to do with these ODBC drivers.
Microsoft SQL ServerSybase DatabaseMicrosoft SQL Server 2008
You cannot execute any Stored Proc directly from Data Flow task unless you use FMTONLY ON command before the EXEC statement.. This sure works against SQL Database never tried against an ADO source..but you give it a try to see if it works
SET FMTONLY ON
SET NOCOUNT ON
EXEC sfa_sp_REP182
SET FMTONLY OFF
Vass1
ASKER
Hi - just tried the FMTONLY idea but still get the same problem. In fact, clicking Preview now returns NO rows rather than returning data... Thanks anyway.
Reza Rad
why you don't use ODBC connection in SSIS?!! try it.
The advice to use SET FMTONLY ON is bad advice - it is the equivalent to running SET NOEXEC ON. The stored procedure will not actually ever execute - hence the zero rows returned.
None of your error messages are Sybase errors, or ODBC errors. Suspect your problem lies elsewhere.
vdr1620
My bad.. it should be OFF instead of ON
it should actually be SET FMTONLY OFF, without which you will not be able to see any Columns at-least in sql.. There are many ways around,this being one of them
>>>>>>>>>I don't have ODBC connections listed in my Data Flow Sources. So, even though I've configured ODBC connections on the server, I can't access them <<<<<<<<<<
You will need to use a ADO.NET source to connect to a Database using ODBC connection
SET FMTONLY ON
SET NOCOUNT ON
EXEC sfa_sp_REP182
SET FMTONLY OFF