Skip to main content

Why Oracel or SQL DBA like Postgres than mysql


  • We can create database server architecture similar to Oracle/SQL as well as mysql and also feature of mongodb.
  • Postgres Supports all sorts of performance optimization that we used in Oracle or SQL Server. I think in that's case where MySQL is lacking.
  • Supports materialized views and temporary tables. Supports temporary tables but does not support materialized views.
  • It implements the SQL standard very well. It includes support for "advanced" SQL stuff like window functions or common table expressions (now supported in MySQL 8.0) .
  • Postgres is very innovative in the matter of how plpgsql interacts with SQL. It supports lots of advanced data types, such as (multi-dimensional) arrays, user-defined types, etc.
  • MySQL is partially compliant on some of the versions (e.g does not support CHECK constraints).
  • PostgreSQL is widely used in large systems where read and write speeds are crucial and data needs to validated. In addition, it supports a variety of performance optimizations that are available only in commercial solutions such as Geospatial data support, concurrency without read locks, and so on (e.g. Oracle, SQL Server). 
  • MySQL is a widely chosen for web based projects that need a database simply for straightforward data transactions. It is common, though, for MySQL to underperform when strained by a heavy loads or when attempting to complete complex queries.
  • Overall, PostgreSQL performance is utilized best in systems requiring execution of complex queries. PostgreSQL performs well in OLTP/OLAP systems when read/write speeds are required and extensive data analysis is needed.  PostgreSQL also works well with Business Intelligence applications but is better suited for Data Warehousing and data analysis applications that require fast read/write speeds.
  • MySQL performs well in OLAP/OLTP systems when only read speeds are required. MySQL + InnoDB provides very good read/write speeds for OLTP scenarios. Overall, MySQL performs well with high concurrency scenarios. MySQL is reliable and works well with Business Intelligence applications, as business intelligence applications are typically read-heavy.


Comments

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.)    Creation of Application/Proxy user where Application is hosted. 2.)    Give appropriate access to the user. 3.)    Create Database Login user on database. 4.)    Authenticate User and provide credential on IIS. 5.)    Then Configure web.config on Application.

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription