April 1, 2010 at 10:52 am
I have migrated database from Sybase 15 to SQL Server 2008 using SSMA 2008, due to user defined dataypes, we migrated shcema manually and used SSMA for converting stored procedires only.
Now the problem is we have our own user defined data types which are used for tables and Stored Proecedurs, we want to continue using this.
While migrating Stored Procedures to SQL Server 2008 using SSMA 2008, it replaces Sybase user defined data types to SQL server 2008 native data types, inspite of the fact these user defined datatypes already existed on both servers, SSMA ignored thesse and created SPs with paramters with native data types.
Did anyone face similar problem, any suggestions on how to handle this situation.
Yogesh Puri
Database LEAD/ Database Architect (Sybase, SQL Server, Database Designing, Database Migration, PowerBuilder, ASP, PHP, mySQL, postGreSQL)
"Eat your fruits and vegetables." Healthy diets rich in fruits and vegetables may reduce the risk of cancer and other chronic diseases.
April 6, 2010 at 11:49 am
Just curious as to what you have done to resolve this issue.
April 6, 2010 at 12:11 pm
Well SSMA replaces Sybase user-defined types by the underlying types, and they also become part of the table definitions.
We will have to convert these procedures manually on SQL Server since during conversion SSMA will ignore RULE when applied to user data types
April 6, 2010 at 12:22 pm
Thank you for a fast response.
Did you use SQL Server Migration Assistant 2008 for Sybase ASE V4.0?
April 6, 2010 at 12:33 pm
Yes, we have used SSMA 2008 v4.0.1366
August 2, 2014 at 3:45 pm
Hi,
I realized this thread is 4 years old, but still apply to me.
I want to migrate sybase to sql server 2012. I successfully used SSMA to migrate schema and data over on a test servers. It took me 10 hrs to complete. Our prod is an 24/7 OLTP databases and I can't afford to have them down for 10 hrs. I can beg my mgr for 2 hrs downtime the most. I have thought of using t-sql MERGE or SSIS, but we have over 30 databases and each db has couple hundreds of tables. It's a real pain to write t-sql MERGE codes for each table.
Now is my challenge: When it comes to real migration, how do I keep the data sync-up between sybase and sql server til the moment I'm ready to cut over? Is there Microsoft tools out there to accomplish this? Sybase Replication Server is not an option for me.
Any opinion would be greatly appreciated.
Thanh
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply