Hi,
Right now I am working for migration from Sybase to SQL Server. Currently there are batch jobs, Access 2007 databases(.accdb) pointing to Sybase(having tables and stored procedure there). We are in plan to migrate all thease sybase stuff to SQL server. Can you please guide me what should be first step for me to initiate this process? 
I look forward for your joyful reply.
Thanks,

Chirag,

I am sure you must be aware about SSMA, (Sql Server Migration Assitant) , if not then please go through these following URLs.

Microsoft SQL Server Migration Assistant (SSMA) for Sybase is a tool to automate migration from Sybase ASE database to SQL Server or SQL Azure.

Download SSMA http://www.microsoft.com/en-us/download/details.aspx?id=28765

Blogs

1. http://blogs.msdn.com/b/ssma/p/sybase.aspx
2. http://blogs.msdn.com/b/ssma/archive/2011/06/09/migrating-from-sybase-ase-to-sql-server-how-to-use-ssma-for-sybase.aspx

 FAQ - http://download.microsoft.com/download/9/8/5/98561e8d-540f-429d-b93a-66ae05ab8368/SQL%20Server%202005%20Solutions%20-%20Migration%20-%20Sybase%20-%20FAQ.pdf");

Hi Manish,

Thanks for your valuable reply.

But I am not sure this is well enough for existing batch jobs and Access databases(97/2007) which currently pointing to Sybase. I also have to take for them as well tables and stored procedures in Sybase. Can we do this using SSIS?

Do you have any approach for batch jobs and access databases? 

Thanks,

Hi Chirag,

Couple of months before I did a migration from Sybase ASE database (Adaptive Server Enterprise/15.0.2) to my favorite MS SQL Server 2012 , and I was having some around 1500  tables, 750 Indexes, 2000 Sps and 200 Functions and successfully migrated all of them, but like in your  case I was not having batch job and ACCESS dependency, Hence I am not able to comment on this, but I believe the other forum members might suggest you better approach and alternatives.

Hello Manish,

Can you tell me what was the total effort to do this migration.  We currently planning to migrate a Sybase DB to SQL and we seems have some problem to determine the right effort.

Hello Chirag,

Manish suggested right about for SSMA, even I have used that tool and it works fine.

Next thing is Batch Jobs, well we had batch jobs in our application and those were in written in shell programming and configured through Autosys. For conversion of batch jobs we have created a tool to extract queries from the batch jobs and then reviewed it, those required changes were put into SSMS and converted code back to the batch program.

As you are in starting phase, I will strongly suggest you to work on "Data migration" approach because that takes a serious amount of time. For data migration you can use Bulk Copy(BCP), freeBcp, DataCopy. Every tool has an advantage and a disadvantage too, so please go through the offer document carefully before investing(time)! :)

HTH

Regards,

Agrawal

Hello Chirag,

SSMA is a really powerful tool, but unfortunately the list of supported databases could be larger. Even though we got used to work with it,  for Teradata to SQL Server migration we had to find another tool. It's called SQLWays. The tool turned out to be very flexible and good at migrating our stored procedures, triggers, functions, etc. What was good about it as well, is that the whole process of migration was highly automated. We are constantly working on some migration projects, and now we are using it again for Sybase to SQL Server migration. So as an option you can try this tool as well: www.ispirer.com/products/sybase-to-sql-server-migration