Database Migration From SQL Server
Move Off Your SQL Server Database Faster
SQL Server Migration Factory: Powered by Prolifics
Accelerated Migration
to Your Target Database
It’s unlikely you’re still running your SQL Server database on OS/2*, but it’s been popular since Microsoft ported the Sybase database in 1989.
There are many reasons organisations might consider moving away from SQL Server – cost, cloud migration, open source policy, performance… but regardless of the reason, transitioning from a working database can be daunting.
Databases exist to serve applications, which drive business value. Any database change must enhance the user experience. This is where Prolifics Database Migration planning begins.
However, there may be valid technical or commercial reasons why moving off the SQL Server database isn’t the right decision. For instance, your application may only be compatible with SQL Server. Prolifics will guide you on the technical and commercial considerations to help you understand if migrating from SQL Server is a good fit for your business. As you’ll discover, minimising risk is a key focus area throughout the project.
Minimising Database Migration Risk
Prolifics Database Migration Strategy Reduces Errors for Improved Performance
Technical and Commercial Viability Assessment
before any work takes place, we do this because we don't want your migration to fail.
Comprehensive Code Assessment
Prolifics covert your code optimally taking into account the nuances of SQL compatibility, to get the best version of your source. Incompatibilities are highlighted and changes tracked, to provide full auditability.
Automated Change Management
Minimise human-error. The target database is checked against the source environment to confirm successful conversion of the code. Then, using Prolifics' bespoke tooling of Python and NiFi we will migrate the data itself to the target EDB database.
Unmatched Consultation and Guidance
Guidance every step of the way. Without a robust testing methodology and knowledge of common SQL pitfalls, timelines can become compromised. Our specialist testing team create the right environment to make this final process seamless.
Detailed Strategy and Fixed-Cost Pricing
Know how much it will cost and why etc. etc.
Is Your SQL Server DB a good candidate?
Meet ADAM, Our Automated Database Agnostic Migrator
Automated – Prolifics went to market searching for a database migration tool to help with moving our customers between database vendors. We found many, but none that worked for us. They were either just a bunch of scripts that didn’t do the job, or a ‘black-box’ with no auditability that also didn’t suit our needs. What we needed was customisable automation. A system that tells us what it is going to do before it does it, takes the application into account, and then automates the creation of the best solution under the guidance of a database migration expert. It didn’t exist so we built it.
Database Agnostic – Most migration tools move code from A to B, or from C to D, but unless they specifically target A to D you need a different tool. ADAM works differently as it doesn’t convert directly, but rather works on a hub and spoke model. This means that it converts A, B, C and D into a central model, and then converts that into your target database A, B, C or D. Obviously it does not work with every single database ever made but it does work with all the major relational DBMS’s. So if you want to move to Postgres, Db2, Sybase, SQL Server, Aurora, etc etc – then ADAM will work for you.
Migrator – The tool is an assistant to our consulting services. We do not provide the ADAM software to our customers, we provide a migration service using ADAM. We do not just run your code through a tool and hope for the best. ADAM will analyse all of your SQL code upfront as a part of the planning process. From that analysis we will then identify every line of code as one of the below
• Needs a re-architecture as it is not supported on the target database, storing Oracle parquet files on postgresql for example (correct at the time of writing)
• Needs a sensible decision made by the consultant, distribution keys for example.
• Code that could be migrated a few ways, and so the specific conversion is application dependent, how to store numbers for example.
• Code that can only be migrated one way, and so can be automatically converted without further analysis.
Expert Insight
Why is SQL
so... incompatible?
Prolifics’ database expert and architect, Paul Vernon speaks candidly about why SQL databases are notoriously difficult to migrate.
Find out why this is stopping IT teams in their tracks when considering new, target databases.
Blog
SQL Data Migration:
What You Need to Know
Moving databases can be tricky, so we’ve put together a short article on everything you need to know before embarking on a migration.
Arrange a Call With Our Expert
Request a Database Assessment
Your next step may or may not be crystal clear, but a lack of tried and tested skills can be a daunting prospect when it comes to moving or migrating enterprise databases.
Spend 30 minutes with our database migration expert, for an assessment of the time and cost required to move you from SQL Server to your target database.