Here is the issue that I am having problems with. I am trying to export the data from a table in Interbase to a flat file (csv) using SSIS through the Embarcadero ODBC driver. I can connect to Interbase with SSIS and I can even see the data on the Interbase connection side but when I execute the package very little of the data actually comes across from Interbase to the flat file. What I get is a file filled with just commas and either the numeric or timestamp columns. I am assuming that I have some sort 
of data type conversion issue or a character set issue. I have tried using SQL and the CONVERT function to convert the string data and have played around with the Char Set (its Win1253 in Interbase). I am running Interbase XE on a Windows Server 2008 R2 with service pack 1 installed and I am running SQL Server 2008 R2 (64 Bit) on a different Windows Server 2008 R2 also with service pack 1 installed. Can someone please help me figure this out.

Thank you

Paul Heinsohn wrote:
> It is very weird behavior that tells me something is wrong on a more foundational level.

It you want to go to a core foundation level, run ODBC Test. It's part 
of the MDAC SDK which can be downloaded from here: 
http://www.microsoft.com/en-us/download/details.aspx?id=21995 If ODBC 
Test returns the wrong data, then you are on to something and it is 
something we can investigate. If ODBC Test and SSIS return something 
different, then you should contact Microsoft.

Another thing you might do here is generate an ODBC Trace log. Then, 
look to see what SQL Statements are generated. Run those SQL statements 
through IBConsole or isql and see if you get the same results as SSIS. 
If IBConsole or isql return the same results as SSIS, then I suggest 
your data is not what you think it is.

Note that if want someone from Embarcadero (most likely me), to 
investigate the ODBC Test output of your database, I would entertain the 
idea for a $300 support incident. What we don't do is investigate what 
SSIS does. You can learn more about a single incident here: 
http://support.embarcadero.com/incident. We would need some sort of 
database from you to do this work. Possibly a meta data only backup and 
a few insert statements.

SSIS is really a development platform. It integrates with Visual Studio. The problem that I am having is that when I attempt to work with the data in that environment none of the string values come across. It is very weird behavior that tells me something is wrong on a more foundational level. Thanks for the feedback. I will read that document.

Do you have access to any sort of development tool? This would be pretty 
easy to do with RAD Studio and I imagine Visual Studio as well. That is 
how I would create something that was scheduled.

Otherwise, I suggest you look at 
http://support.embarcadero.com/article/44061. It gives you a variety of 
options for data migration.

Paul Heinsohn wrote:
> Can anyone recommend a data pump tool that will allow us to output a csv file from a ta
> ble on a scheduled basis?

SSIS stands for SQL Server Integration Services. It is the ETL tool that comes with SQL Server. My bad on the CONVERT function, I'm new to Interbase and I didn't realize that it was not a standard function. I am working on a data warehouse project that must pull data on a scheduled basis from Interbase so unfortunately doing the work manually through IB Console won't work for us. Our process needs to run automatically. Can anyone recommend a data pump tool that will allow us to output a csv file from a ta
ble on a scheduled basis? That aside can anyone explain why I can save a SQL query to a csv file from inside IBconsole but when I try to connect to the database through the ODBC driver and run the same SQL query, none of the string values come through?

InterBase nor it's ODBC driver knowns anything about exporting to a CSV 
file. I have never heard of SSIS, but if you are going to use it, then 
whatever needs to change has to change with it and not with InterBase.

Note that InterBase has no function called convert. So, anything called 
convert would be a SSIS thing.

There are many ways to export to a CSV file and my suggestion would be 
to find another way. One way would be to use IBConsole. There also many 
data pump utilities out there, many free, and I would guess that most 
can connect to anything ODBC and export to CSV.

Paul Heinsohn wrote:
> Here is the issue that I am having problems with. I am trying to export the data from a table in Interbase to a flat file (csv) using SSIS through the Embarcadero ODBC driver. I can connect to Interbase with SSIS and I can even see the data on the Interbase connection side but when I execute the package very little of the data actually comes across from Interbase to the flat file. What I get is a file filled with just commas and either the numeric or timestamp columns. I am assuming that I have some sor
t
> of data type conversion issue or a character set issue. I have tried using SQL and the CONVERT function to convert the string data and have played around with the Char Set (its Win1253 in Interbase). I am running Interbase XE on a Windows Server 2008 R2 with service pack 1 installed and I am running SQL Server 2008 R2 (64 Bit) on a different Windows Server 2008 R2 also with service pack 1 installed. Can someone please help me figure this out.
>
> Thank you
>