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.
Talks on Managing Data and Applications Anywhere
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.
I recently ran into this issue with SQL Server 2019 CTP 2.5 where I was getting the error – Msg 3628, Level 16, State 1, Line 4 The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator. It turned out that this would happen whenever I ran a query that joined In-Memory tables with disk based tables and the result ended up with no rows returned. Here is how trace flag 1254 fixes SQL Server Msg 3628 floating point exceptions.
When converting Oracle database code to Microsoft SQL Server, I often face the problem of correctly mapping Oracle data types to SQL Server data types. I regularly use SQL Server Migration Assistant (SSMA) to automate Oracle database code conversion to SQL Server. However, SSMA’s default data type mapping for Oracle procedure and function parameters uses the maximum possible size for each specific data type to prevent data loss. This approach causes unintended consequences with application code.
Managing customer’s SQL Server applications, we discovered a significant performance decrease related to query execution time. We figured out that the reason for that was the execution of a script, which checks the existence of database objects before updating them. Initially, the developers created this script to emulate the behavior of the CREATE OR REPLACE statement from many other database platforms.
We solved the performance issue by replacing the original script with a new code snippet.
As moats create obstacles in the way of an invader, so do proprietary database features for developers. One of Oracle’s proprietary features is the Oracle Call Interface (OCI) which provides efficient communication between application code and the database. There are other ways to connect to Oracle, but once you have committed to OCI, you are “protected” from switching to another database. In this blog post, we break down an application modernization from Oracle to SQL Server for an advanced engineering-oriented […]
One of our customers, a global digital media company, came to us with an interesting problem. As part of their General Data Protection Regulation (GDPR) compliance program, our client identified two tables that contained hundreds of millions of rows of historical user login data. GDPR states that you can process personal data while there is a contractual obligation with your client. However, once you terminate the contractual obligation and you have no legitimate interest with the data, deleting historical data […]
One of the leading US agricultural suppliers wanted to upgrade their SQL Server system in order to reduce their overall SQL Server licensing expenses. We performed a thorough financial and technical analysis of their existing OLTP and BI/OLAP database system, and provided a number of optimization suggestions. In addition, we delivered a modernization roadmap to give the customer an idea of potential future plans. Discover how we approached this project from the following video. Complex customer’s system Before our customer […]