March 11, 2011 at 9:53 am
Using SSIS package
From Sybase Server
To SQL Server 2005
Created a Dataflow
Data Reader Source to Ole db Destination
Table gets created, but if the table on the sybase server had fields that are not nulls they are not being converted as such, all fields in SQL Server are set to allow nulls and Primary keys or FK are not being migrated as well.
Sincerely,
Sonal.
March 11, 2011 at 11:48 am
Mapping a Data Reader Source to an OLE DB Destination will give you the option to create the table in the destination...however other than column names and data types nothing else is "brought over". All it is helping you do is create a place to copy your data to.
If you are migrating a set of tables and their data from Sybase to SQL Server I would suggest you script out all you DDL from Sybase and build those tables in SQL Server before going to SSIS to setup a package to copy your data.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 14, 2011 at 7:01 am
Thank you.
March 14, 2011 at 7:21 am
I am still waiting for the sybase drivers to be loaded, so cannot use the import wizard on SQL Server yet.
If I used the import wizard on SQL Server, will this also not bring the not nulls and PK's?
http://msdn.microsoft.com/en-us/library/ms141209.aspx
"The SQL Server Import and Export Wizard provides minimal transformation capabilities. Except for setting the name, the data type, and the data type properties of columns in new destination tables and files, the SQL Server Import and Export Wizard supports no column-level transformations. "
This is what I got from the above link.
Sincerely,
Sonal.
March 14, 2011 at 9:34 am
The Import Export Wizard will help you do a simple 'source to destination' data copy, hence the lack of transformation support. It's a shortcut to create a package very similar to what have already created manually in BIDS.
My previous recommendation still stands, you'll want to script the schema out of Sybase, build that schema in SQL Server and then tackle the data movement using SSIS.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 15, 2011 at 7:05 am
FYI, moving (non-trivial) data from ASE to SQL Server in an automated fashion isn't particularly easy, at least without fairly expensive 3rd party tools. In general, you'll need to do a lot of scripting.
You're aware that NULLs "evaluate" differently by default on those platforms?
However, there is one free tool from Microsoft that will do a pretty good job of copying schema and either changing it appropriately, or pointing out the exact place you need to do handwork.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=C7933D3E-B7B9-43A6-ADE3-F8E37C8CB046
Roger Reid
Roger L Reid
March 15, 2011 at 8:36 am
Roger tried to access the two microsoft links you referred to and access is denied per "Corporate Policy"
Sincerely,
Sonal
March 15, 2011 at 9:20 am
Attached are the SSMA for Sybase to 2005 from Roger's first link and the two white papers from Roger's second link.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply