Our fully automated Migration Platform confidently guides you through an upgrade project. Read the blog post and watch the related video to discover how you can use the DB Best Migration Platform to test breaking changes and new features during the SQL Server upgrade.
Talks on Managing Data and Applications Anywhere
In Oracle, you can specify virtual columns in a table definition. However, when migrating your Oracle database to Microsoft SQL Server, you need to utilize computed columns. You may want to use SSMA to automate the conversion. The problem is that SSMA does not correctly convert source Oracle virtual columns to SQL Server. So, you will need to update the converted code manually.
Read this blog post to discover our proven solution to Oracle virtual columns conversion to Microsoft SQL Server.
Our customer’s data science team needed to perform read-only data warehouse queries against a mission-critical online transaction and batch processing database. They were performing read-only queries over 4 terabytes of historical data. These queries are ad-hoc and look at multiple months of historical data for analysis. The queries would consume all available I/O on the production databases environment and impede the performance of the primary workload. This blog talks about how we helped them solve this problem.
One of the customers contacted DB Best to help address performance issues with their SQL Server application. They started experiencing problems after upgrading from SQL Server 2008 R2 up to SQL Server 2016. However, after we analyzed their database system, we discovered a complex issue with updating SQL Server statistics.
We utilized industry best practices and internal expertise to correct issues. Read our blog post to learn how we approached this complex task.
In Oracle, you can use a combination of a trigger and sequence to generate unique values for the key columns. However, when migrating your Oracle database to Microsoft SQL Server, you need to find the right path to convert this construction. This is an architecture-level decision, so you need to approach it at the very beginning of your migration project. Otherwise, you will need to recreate tables, reload data and recreate backups, and even rewrite code that relates to these tables.
Read this blog post to discover our proven solution to Oracle sequences conversion.
For quite a period of time, our customer was using a SQL Server database that at the long last became disorganized and fairly difficult to arrange. The difficulties with finding and retrieving the right data negatively influenced their performance. In addition, their server was storing duplicating views and tables that utilized space. The problem Our customer considered hiring several data analysts to reinforce their team. However, extra people in the team couldn’t address the challenge for they weren’t aware of […]
When migrating Oracle databases to Microsoft SQL Server, you need to define a naming convention for the conversion of packaged procedures and functions. This step is as important as setting the schema mapping and data type mapping. This is an architecture-level decision that you should make at the very beginning of your migration project. Read this blog post to discover the importance of this decision and the possible issues it may cause.
I recently had a client using SQL Server 2012 Standard Edition on three of their development servers. However, SQL Server 2012 has a developer edition that is specifically designed for development servers. More importantly, our client has free SQL Server 2012 Developer edition licenses as part of the paid SQL Server Standard Editon purchase.
Our customer decided to convert their Standard Edition to the Developer Edition so they could save big bucks. However, the conversion process can be a bit tricky. In this blog post, we will show how you can easily convert SQL Server Standard Edition to the Developer Edition.
One of our customers had their Management Data Warehouse (MDW) running on their production SQL Server 2012 and didn’t know what to do with it. Microsoft had introduced the MDW with SQL Server in 2008. However, there was a bug in SQL Server 2012 that prevented the Query Statistics data collector from working. Rather than trying to fix it, we made the decision to remove it instead.
Removing the MDW from SQL Server running in production is straight forward and requires that you follow the steps described in this blog post.
When migrating a customer’s Oracle databases to Microsoft SQL Server I often face the problem of updating relevant applications. A broad range of our customers use the Oracle Call Interface (OCI) to develop their database applications.
This interface is specific to Oracle and you can’t use it to connect to any other database platform. Read the blog post to discover the right path to effectively remediate Oracle’s С or C++ applications to the Microsoft SQL Server.