In this case, and many others, Babelfish ensures the semantics of SQL Server data types and T-SQL functionality are preserved: we created a MONEY datatype that behaves as SQL Server apps would expect. Such a subtle difference might lead to rounding errors and have a significant impact on downstream processes, such as financial reporting. For example, the MONEY datatype has different characteristics in SQL Server (with four decimals precision) and PostgreSQL (with two decimals precision).
Instead, we focused on the most common T-SQL commands and returning the correct response or an error message. SQL Server has evolved over more than 30 years, and we do not expect to support all functionalities right away. Amazon Aurora provides the security, availability, and reliability of commercial databases at 1/10th the cost. When adopting Babelfish, you save on licensing costs of using SQL Server. Babelfish reduces the risk associated with database migration projects by significantly reducing the number of changes required to the application. Support for T-SQL includes elements such as the SQL dialect, static cursors, data types, triggers, stored procedures, and functions. Babelfish adds the capability to Amazon Aurora PostgreSQL to understand the SQL Server wire protocol Tabular Data Stream (TDS), as well as extending PostgreSQL to understand commonly used T-SQL commands used by SQL Server. Just point the application to an Amazon Aurora PostgreSQL database with Babelfish activated. You continue to use the existing queries and drivers your application uses today. You can migrate your application in a fraction of the time that a traditional migration would require. It allows you to migrate your SQL Server applications to PostgreSQL cheaper, faster, and with less risks involved with such change.
Babelfish allows Amazon Aurora PostgreSQL-Compatible Edition to understand the SQL Server wire protocol. Today, we are making Babelfish for Aurora PostgreSQL available. Motivation is there, but costs and risks are often limiting factors. But there is always more work to do to migrate the application itself, including rewriting application code that interacts with the database. When migrating your databases, you can automate the migration of your database schema and data using the AWS Schema Conversion Tool and AWS Database Migration Service. But migrating away from commercial and legacy databases can be time-consuming and resource-intensive. Many of our customers are telling us they want to move away from proprietary database vendors to avoid expensive costs and burdensome licensing terms.
0 kommentar(er)
