March 4, 2010 at 10:09 am
I am migrating a Sybase app to SQL Server 2005 or 2008. There are a large number of BCP (in and out) scripts running on UNIX that point to the Sybase server. These scripts are complex because in addition to BCP, they include PERL and PYTHON scripts which format the output files.
The logical solution would be to redevelop everything in SSIS.
Alternatively, is it possible to point the Sybase BCP program running on the UNIX server to my new SQL Server instance?
March 4, 2010 at 1:06 pm
I am migrating a Sybase app to SQL Server 2005 or 2008. There are a large number of BCP (in and out) scripts running on UNIX that point to the Sybase server. These scripts are complex because in addition to BCP, they include PERL and PYTHON scripts which format the output files.
Regarding PERL and PYTHON, there are windows versions available such as http://www.python.org.
For Sybase BCP, SQL Server also has a BCP and you will find that the parameters are similar but there are some differences, such as, especially with the case sensitivity of the parms.
Sybase:
-a display_charset
-A packet_size
MS:
-a packet_size
-A does not exist.
SQL = Scarcely Qualifies as a Language
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply