Huge data movement from Sybase IQ to SQL server approach

How to do large set of data movement from SAP ASE/ ASE IQ server to other RDBMS say SQL server.??
The data is need to move is around 2-3 TB , could you please provide a complete step to step approach.
My Sybase IQ tables are too big. A detailed explanation will be highly appreciated.

Thanks
LVL 2
learning_sybaseAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
From the description is not clear if this is a one time data migration or one sync from Sybase to MS SQL database or whavere else it may be so depending on the case scenario you could use the Sybase migration too from Microsoft SQL as per https://docs.microsoft.com/en-us/sql/ssma/sybase/sql-server-migration-assistant-for-sybase-sybasetosql?view=sql-server-2017&viewFallbackFrom=sql-server-2014 OR use SQL Server SSIS Integration Packages to Import your Sybase data into SQL OR you could use Sybase ddlgen utilitly to extract the database structure then use the Sybase bcp utility to extract the data from the Sybase database and bcp into SQL.
learning_sybaseAuthor Commented:
Thanks Icohon. Joe and Alpmoon, waiting for your inputs too. Please advise.
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> The data is need to move is around 2-3 TB

Few pointers to be noted..
1. What is the number of tables in your database.
2. Are all those tables huge in size, if so what would be the size of the individual tables..
3. Calculate only the data size without the space occupied by indexes..

Once you have the above values identified, you can handle the Data Movement or Migration better by following the below guidelines:
1. Drop the Indexes on the Destination table to transfer data faster.
2. Disable any Foreign key constraints so that Data Movement would be faster.
3. Depending upon the individual record size, identify the optimal batch size for the tables.
4. Make sure the Destination SQL Server database is set to Bulk Recovery Mode or Simple Mode to reduce the Log file size increase..
5. Use SSIS or BCP to perform bulk load on the destination tables which would be faster.

As mentioned by lcohan, you can also use Database Migration Assistant for SQL Server which can help validate the data type and few other prerequisites for Migration..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
learning_sybaseAuthor Commented:
Thanks to all
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL

From novice to tech pro — start learning today.