Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Being a solution consultant for the world leader in data connectivity, I have had the opportunity to consult on several database migration projects. I have seen almost every combination of migration to/from SQL Server, Sybase, DB2 and Oracle across Unix/Linux/Windows. Much like Progress DataDirect who is "Switzerland" when it comes to databases, I too love them all from Operational to DWs, on-premise to clouds, SQL to NOSQL ... and we're ready for your next migration.
Why choose Progress DataDirect connectivity for your migration project?
Data connectivity and compatibility with existing applications across different platforms varies greatly between database vendors. DataDirect has been developing interoperable connectivity for decades, and we have the largest standards based data connectivity test suite in the universe across a full range of databases and platforms. We've seen everything including issues where one of several result sets get returned, stored procedures fail to return expected data, internationalization and translation issues for character data, etc. Your data migration project cannot afford these kind of setbacks.
And Progress DataDirect bulk load has introduced a brand new set of solutions for database migration.
Here are the 3 most recent projects I have worked:
1. Migrating existing BCP and SQL scripts and custom applications
Problem: An enterprise financial services environment is entertaining a DBMS migration from Sybase to SQL Server 2008, but had thousands of BCP bulk load and ISQL scripts running across Solaris SPARC, Linux and HP-UX. Each of those scripts would have to be migrated one by one to keep the environment running against SQL Server.
Solution: Our exclusive standards based drivers and code samples were used to create database agnostic utilities that can run anywhere against anything. The architect overseeing that project is a popular guy today, and will be a bigger hero when the next database migration project comes along. Learn more by reading an article on BCP and ISQL on Unix/Linux to SQL Server, Sybase, DB2, Oracle.
To complete the transition, it is also important to port existing PowerBuilder for Unix applications from Sybase to SQL Server using the DataDirect Connect for ODBC SQL Server driver.
2. Data Validation
Problem: A consulting group migrated a large amount of data from Sybase to SQL Server 2008 R2 for a prospect. To check for accuracy between source and target, they typically dump data to flat files for comparison on smaller systems. However for larger systems, the size of data becomes unmanageable for such an approach.
Solution: Use data federation to leverage the database server's processing power and memory to perform a byte by byte comparison to ensure accuracy. Our DataDirect Connect64 for ODBC Sybase driver was the only scalable solution to fetch large amounts of data quickly and accurately for validation from SQL Server Linked Server.
3. Application migration across the enterprise
Problem: Another organization has over 600 systems running various database applications accessing Sybase. They are planning to migrate to DB2 LUW over a 12-18 month period where data may exist in both the old and new systems, and it's important to ensure the SQL syntax is compatible with DB2. They need an intermediate solution to avoid having to rewrite 60 applications running on 600 systems to support the new DBMS.
Solution: Use the DataDirect OpenAccess SDK to add data access logic at the driver level to achieve data federation between the two systems and modify queries for compatibility with the new DBMS. This makes the migration seamless to users, and no application or script changes are required.
And as I'm wrapping up this post, an Oracle to DB2 LUW 9.7 migration is underway with the help of our DataDirect Connect for ADO.NET providers in an SSRS reporting environment.
Get started today on your project!
1. Download free trial for any DataDirect Database Migration Solution.
2. Or call 1-800-876-3101 to speak with a live Solutions Consultant to learn how other organizations are making progress with DataDirect Connect products for database migrations.
Sumit Sarkar is a Chief Data Evangelist at Progress, with over 10 years experience working in the data connectivity field. The world's leading consultant on open data standards connectivity with cloud data, Sumit's interests include performance tuning of the data access layer for which he has developed a patent pending technology for its analysis; business intelligence and data warehousing for SaaS platforms; and data connectivity for aPaaS environments, with a focus on standards such as ODBC, JDBC, ADO.NET and ODATA. He is an IBM Certified Consultant for IBM Cognos Business Intelligence and TDWI member. He has presented sessions on data connectivity at various conferences including Dreamforce, Oracle OpenWorld, Strata Hadoop, MongoDB World and SAP Analytics and Business Objects Conference, among many others.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.