I am building a SQL Server 2005 Integration Services package to migrate data from a Sybase Adaptive Server Enterprise 12.5.4 database to a SQL Server 2005 Database. The Sybase Database is the backend for a vendor product which our team does not have the authority to change or manage.
In my initial stages of development, to access the Sybase database, I created a SQL Server Linked Server utilizing the Microsoft OLE DB Provider for ODBC Drivers on my destination database server. With this linked server created, I created my SSIS package with a single Data Source - connecting to the MS SQL Server "Destination" Database. Next, in my SSIS package data flow tasks, I configured the OLE DB Source to access single Data Source defined in the package, using SQL commands to access the source linked server (simply using SELECT col1, col2, col3 FROM [SybaseLinkedServer].[Database].dbo.[Table]). The OLE DB Destination within the data flow task utilizes the same connection manager as the OLE DB Source, but makes use of the Table or view - fast load Data access mode.
Later, in the project, I obtained the Sybase ASE OLE DB Provider (The v12.5.4 OLE DB Provider was no longer available, we had to purchase the v15.7 ASE SDK). Thinking that removing the Linked Server from the solution would improve performance, I modified the SSIS package to include a new OLE DB Data Source utilizing the Sybase ASE OLE DB Provider to access the Sybase Database directly, and modified the OLE DB Source to use the new ASE OLE DB Data Source with the Table or View Data access mode.
To my surprise, switching the solution from the Linked Server using the OLEDB Provider for ODBC Drivers to the direct OLEDB connection using the Sybase ASE OLEDB Provider produced significantly poorer results, far from my expectations. The results from test runs using each method are available at this hyperlink.
Has anyone experienced this type of issue and/or is this behavior to be expected? Is there a better way to configure this to extract data from Sybase ASE to MS SQL Server 2005?
i had the exact same issue and i ended up using linked server to connect to sybase because it was the fastest way and most reliable, i had great difficulty trying to connect to sybase using SSIS sql 2008 directly.
even though i was able to connect to sybase using Sql 2000 DTSs.
but there is a very interesting driver provided by datadirect
http://www.datadirect.com/products/other/ssis/index.html
i downloaded it and tried it for 30 days, and it was amazing fast and very easy
its very light when comparing it with sybase drivers, i mean not much to install and it works very good with SSIS.
Related
Im using SSIS package which created SQL Sever data tools 2017 to load data from Oracle to SQL Server. I have setup the Oracle Client 32bit in SQL Sever and configure tnsnames.ora correctly. In OLE DB data source at Data Flow Task successfully connected to Orcal Database in SSIS. I have try simple query out some columns using SQL Command in OLE DB Source.
But Im getting following error when previewing the data,provider cannot derive parameter information and setparameterinfo has not been called. (Microsoft OLE DB Provider for Oracle).
I have tested packages which created in SQL data tools 2010,2012,2014 and those are worked fine and not generated any errors. But for 2015 and 2017 SQL Data tool packages above mentioned error is generating. So could you guide me how to fix this in SQL Data Tools 2017 version.
I need to import some data from Ms Access to SQL Server 2008 R2 and SQL Server 2012. One of the requirements is to use SSIS so we can generate and schedule a package to run at a later stage.
When I create a Data Flow task, the Source Assistant Wizard is not able to locate the Ms Access database file (accdb). There is no option on the list to select Ms Access or OLE provider. I was able to create a connection to the Access db in Connection Managers but again I cant work out how to use that connection as a data source. Any assistant would be greatly appreciated
I want to export the entire schema and daily data from a SQL Server Compact database (3.x) into a SQL Server LocalDB or Express database. Evem better yet would be to pipe it daily into a Sybase/SAP SQL Anywhere database.
I would like to grab the Compact schema and port it to the other database, then set up a daily pipe to copy the data completely into the second database.
Any experts out there who know how to do this? Are there data migration tools in SQL Server LocalDB / Express that can be automated to do this?
Even better yet, would be to have the database painter in Powerbuilder 12.5 (SAP/Sybase) be able to access the SQL Compact database....but I'm not going to hold my breath. Powerbuilder could then do the data pipe.
Any ideas?
Thank you in advance.
You can use my SQL Server Compact Tools on Codeplex to do this, either from GUI, coomad line or via a .NET API
My SQL Server 2012 server with several linked servers hangs when i try to add a linked server to an Access database using the ACE 12 provider. Once it hangs, SQL management studio stops displaying linked server catalog objects. I have enabled InProcess on the ACE provider.
How do I fix this/add the Access DB as a linked server without this problem?
For context, I have a MS Access database (about 1GB in size) with about a dozen tables that I want to load into corresponding tables in a SQL server 2012 database. The data is loaded on demand when a user process a button in an Excel worksheet. (worksheet calls stored procedure, stored procedure calls DTS package)
I want to change this process to remove the DTS package because users will no longer have permission to run DTS packages or xp_cmdshell.
I think the DTS package could easily be replaced using a linked server or even OPENDATASOURCE query, but I'm having trouble using the linked server (constantly hangs when i try to add it)
I want to migrate a Btrieve Database to Microsoft SQL Server 2008 R2. I already have done the step of migration to Pervasive PSQL 10 Workstation (x86), which offers an ODBC / OLE DB driver. (It seems Microsof doesn't offer any solution to import Btrieve.)
Ok, so far so good, but how can I transfer the whole database (schema and data) into Microsoft SQL Server? The Import Wizard of SQL Server crashes every time and is useless, because it doesn't map Date- and Memo-Datatypes correctly. I also tried to map these datatypes manually, but the wizard always crashes, caused by ODBC-Errors.
So, I'm looking for a tool which offers a native driver to Btrieve or PSQL 10. It would be nice if it is free, because I only need it for this single migration.
TIA! ^^
There is a tool with a Btrieve driver but you still need the DDFs (just like in ODBC) available from Pervasive called Data Integrator. It is not free but you can find more information at http://integration.pervasive.com/.
Another more manual option would be to export the data from PSQL to CSV, then import the CSV to the MS SQL server. You would have to manually create the tables in the MS SQL database but it could be done with the tools you have.
Also, you say it's crashing with ODBC errors. Are the ODBC errors from PSQL or MS SQL? What are they?