One thing you have to watch out for is the fairly severe differences in the way MSSQL and MySQL implement the SQL syntax.
MS SQL works only in Windows and is expensive; MySQL works on Windows and Unix and is free; Oracle works on Windows and Unix and is expensive. All three can be used to develop high-performance applications."
Moreover, advantages and disadvangates would largely depend on counterpart technologies you plan on using. Database engines do not exist in a vacuum; they work with some counterparts very well, and not so well with others. For example, if you are developing a Web application in ASP.Net and expect it to run on a single physical machine (or on a series of parallel machines), SQL Server would be a good choice, because you can take advantage of tight integration of the Microsoft-only software stack; if you plan on having a layered architecture, tight integration is not going to do much for you (IIS and SQL Server are not going to run on the same machine), so you might consider using Oracle on the DB layer. If you intend to deploy on Linux (or any other Unix or Unix-like platform), this automatically excludes SQL Server from consideration, as it only runs on Windows. If you intend to write a JSP/Tomcat Web application, you should probably stay away from MySQL, as this pairing is known to have performance issues. Combinations of other JSP application servers with MySQL have not been extensively tested, so JSP shops tend to lean towards Oracle (especially considering its long history of peaceful and productive co-existence with Java). If you want to write a scalable PHP or Python application to be deployed on Linux, MySQL will provide an unbeatable combination of price and performance.
more visit:
Comparison of Different SQL Implementations.
MS SQL works only in Windows and is expensive; MySQL works on Windows and Unix and is free; Oracle works on Windows and Unix and is expensive. All three can be used to develop high-performance applications."
Moreover, advantages and disadvangates would largely depend on counterpart technologies you plan on using. Database engines do not exist in a vacuum; they work with some counterparts very well, and not so well with others. For example, if you are developing a Web application in ASP.Net and expect it to run on a single physical machine (or on a series of parallel machines), SQL Server would be a good choice, because you can take advantage of tight integration of the Microsoft-only software stack; if you plan on having a layered architecture, tight integration is not going to do much for you (IIS and SQL Server are not going to run on the same machine), so you might consider using Oracle on the DB layer. If you intend to deploy on Linux (or any other Unix or Unix-like platform), this automatically excludes SQL Server from consideration, as it only runs on Windows. If you intend to write a JSP/Tomcat Web application, you should probably stay away from MySQL, as this pairing is known to have performance issues. Combinations of other JSP application servers with MySQL have not been extensively tested, so JSP shops tend to lean towards Oracle (especially considering its long history of peaceful and productive co-existence with Java). If you want to write a scalable PHP or Python application to be deployed on Linux, MySQL will provide an unbeatable combination of price and performance.
more visit:
Comparison of Different SQL Implementations.
No comments:
Post a Comment