call us toll-free +1 855 855 3600
 
DB Best Chronicles
 
Talks on Big Data, Mobile Apps, Web and Software Development

Is In-Memory OLTP a Useless Feature?

Posted by | On June 22nd, 2017 | In In-memory OLTP, Kalen's Continuum, SQL Server
 

useless

What makes a feature useless? I might agree that if absolutely NO ONE uses it, or has ever used it, then it is useless, by obvious definition.  But if some people use it, but not everyone, is that useless? What if only 1% of product users employ a feature in production? Is that useless? What if those 1% base their entire production system around the feature? Is that more or less useless than another feature used by 80% of the installed customer base in only one or two queries, and for which there is another way to accomplish the same desk with equal efficiency?

I suggest that there isn’t a clear way to measure uselessness, once the usage rate is non-zero. I can even imagine some features that might have seemed exciting when first introduced, inspiring a developer to spend weeks or even month building a proof of concept or prototype. And then what if the prototype failed to behave as anticipated? I can imagine the developer would be left with feelings that were quite a bit less than warm and fuzzy, and might single-handedly, out of frustration, declare the feature ‘useless’. That, of course, does not mean that no one else was able to use the feature to their decided advantage.

Adam Machanic, a long-time colleague of mine, recently posted a list of ‘most useless features of SQL Server’, gathered from suggestions made by his Twitter followers. http://sqlblog.com/blogs/adam_machanic/archive/2017/06/14/the-sql-hall-of-shame.aspx  I was quite surprised to see that one of the features listed was In-Memory OLTP.  Admittedly, he did not claim the feature was completely useless, but was echoing someone else’s tweet. Adam seemed to imply there might be some (very limited) use cases for this feature.  I’ll admit that after having written two books on the topic, I am not completely unbiased about this technology. But I am actually baffled about this feature could be called ‘useless’ when many SQL Server production applications are getting great use out of it.

Read the rest of this entry »

How the detailed modernization roadmap helped reduce the number of servers in the data center by 96%

Posted by | On June 22nd, 2017 | In Azure, Customer Story, Database Upgrades, SQL Server, Uncategorized | Tags: , , , , , , ,
 

 

A major American provider of global eCommerce solutions was looking for a way to upgrade their extensive data processing system. We provided them with visibility into their system and built cost-effective and highly optimized modernization roadmap using our DBMSys tool. Using our detailed instructions they can substantially cut the upgrade expenses and take advantage of their workloads migration to Azure along with benefits from virtualization and consolidation options.

Read the rest of this entry »

Delivering expert support in resolving database conversion errors

Posted by | On June 21st, 2017 | In Customer Story, Database Migration, SQL Server | Tags: , , , ,
 

One of the major United States universities has been migrating their complex data managing system from Sybase to SQL Server. They used SQL Server Migration Assistant for Sybase to automate the migration process. However, SSMA tool could not deal with 100% of their source code, and their development team required some assistance with a manual conversion. So they asked us to provide technical support in resolving these conversion errors. With our guidance and extensive support, our customer was able to complete the migration within the short period of time.

Read the rest of this entry »

Helping our customer to convert Oracle schemas with hierarchical queries to SQL Server

Posted by | On June 20th, 2017 | In Customer Story, Database Migration, SQL Server | Tags: , , , , ,
 

One of the world’s largest information technology companies decided to migrate their Oracle database to SQL Server. They leveraged SQL Server Migration Assistant (SSMA) for Oracle to automate the major part of their migration effort. However, their source database code included over 400 hierarchical queries that SSMA could not convert. Neither could the customer’s technical staff. So, they turned to DB Best asking for assistance in converting a number of Oracle database schemas.

We helped our customer to solve this complicated task by converting the required database schemas within the short period of time. Watch the following video to learn more about the approach  we’ve used to convert the hierarchical queries from Oracle to SQL Server.

 

Read the rest of this entry »

Oracle to PostgreSQL migration with AWS SCT: How to convert INSERT ALL statement

Posted by | On June 19th, 2017 | In AWS, Data Management, Database Migration | Tags: , , , , , ,
 

In Oracle you may use the conditional insert clauses, for example, an INSERT ALL statement to add multiple rows with a single command. You can insert rows into one table or even multiple tables using just one SQL statement in Oracle. However, PostgreSQL doesn’t support such statements that attempt to inserting multiple rows.

So, when you try to convert the source Oracle code that includes the INSERT ALL statement to PostgreSQL in the AWS Schema Conversion Tool, it will generate the following action item: «9996 — Severity critical — Transformer error occurred».

9996_2

Let’s discover how you can address this issue.

Read the rest of this entry »

Oracle to Azure SQL Database shift may save up to $1 million

Posted by | On June 16th, 2017 | In Azure, Customer Story, Database Migration, SQL Server | Tags: , , , , , , , , ,
 

‘Low-performing and costly’ – these were major characteristics of the Oracle system of one of our customers, a leading US automotive corporations. In this regard, it was quite natural for them to consider migration to another database platform. We suggested changing their Oracle Database to Azure SQL Database and moving their applications to Azure services. According to the calculations made by our experts, the customer may well anticipate this solution to save over 1 million dollars only on licenses in the coming 5 years!

The video below depicts the migration process in details:

Read the rest of this entry »

Using PostgreSQL in cloud alongside with Oracle to enhance the database system performance

Posted by | On June 15th, 2017 | In AWS, Customer Story, Data Management, Database Migration | Tags: , , , , , , ,
 

One of the leading independent software vendors in educational domain needed to expand their original Oracle database system. They wanted to add a new PostgreSQL database running at AWS RDS to their original system and upgrade the connected Java application to support both database platforms. We came up with a proof of concept and converted one of the largest customer’s database schemas to PostgreSQL, demonstrating how the upgraded system may work. To do so, we updated the application by adding the unified SQL code and changing its architecture to support 2 database platforms. As a result, the newly created system could meet the customer’s performance requirements.

Watch the following video to learn more about the technical approach that we’ve used for code unification.

Read the rest of this entry »

Oracle to SQL Server migration with SSMA: How to convert virtual columns

Posted by | On June 14th, 2017 | In Data Management, Database Migration, SQL Server | Tags: , , , , , , ,
 

Oracle allows you to specify virtual columns in the table definition. Oracle doesn’t store the data in virtual columns on the disk. On the contrary, the database derives the values in a virtual column on demand by computing a set of expressions or functions. The computed columns in SQL Server are considered as a direct analog of Oracle’s virtual columns. The problem is that the SQL Server Migration Assistant (SSMA) for Oracle converts the virtual columns as a DEFAULT expression. Thus the logic that stands behind the virtual column doesn’t converts to the target database. This will result in an error when you will try to apply the converted code to a SQL Server target database.

convert virtual columns in SSMA

Read the rest of this entry »

Database Compare Suite update 4.9 brings Azure SQL Data Warehouse support

Posted by | On June 14th, 2017 | In Database Migration, Database Upgrades | Tags: , , , , , , , , , , ,
 

We’re excited to bring you the latest release of Database Compare Suite. The new version 4.9 features support for Microsoft Azure SQL Data Warehouse along with some other improvements.

Database Compare Suite 4.9 with Azure SQL Data Warehouse support

Covering 12 Major Database Platforms

With the support of Microsoft Azure SQL Data Warehouse, the total count of available database platforms in the Database Compare Suite reached the total of 12. This dozen includes 5 specific data warehouse platforms. So, you can keep humongous data under control with Database Compare Suite. The full list of supported database dialects includes Amazon Redshift, Azure SQL Data Warehouse, Azure SQL Database, Greenplum, IBM DB2, IBM Netezza, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, Sybase ASE and Teradata.

Read the rest of this entry »

Oracle to SQL Server migration with SSMA: How to convert unsupported SQL clause

Posted by | On June 13th, 2017 | In Data Management, Database Migration, SQL Server | Tags: , , , , , , ,
 

Oracle allows you to assign a non-scalar condition in WHERE clause. The problem is that SQL Server doesn’t support conditions of this type. Thus, the SQL Server Migration Assistant (SSMA) for Oracle doesn’t convert queries with a a non-scalar condition in WHERE clause. So, when you try to convert the source code that includes a non-scalar condition in a WHERE clause, SSMA will generate an error O2SS0001.

O2SS0001 convert unsupported SQL clause

Read the rest of this entry »