|
| Can the marriage of MySQL and ASP.NET match Sql Server and ASP.NET? |
 |
Thu, 21 Feb 2008 15:40:42 +000 |
Because ASP.NET works best with SQL Server (as its a Microsoft technology) would
there be a level of performance not obtainable with MySQL? This being because
MySQL isn't a Microsoft product so the integration isn't as tight as with
ASP.NET/SQL Server.
In other words, could I achieve the same performance between MySQL and ASP.NET
as can be achieved with a well optimised marriage with ASP.NET and SQL Server in
the most ideal environment?
Also, when using MySQL, will there be any classes/methods I can't use because
I'm not using a Microsoft DB provider. I know I can't use SQL Cache Dependency
(or is there a way to use that on MySQL)?
|
| Post Reply
|
| Re: Can the marriage of MySQL and ASP.NET match Sql Server and ASP.NET? |
 |
Sat, 23 Feb 2008 02:59:57 +000 |
First of all, ASP.NET does not necessarily "work best" with SQL
Server. If the database is sound and robust, and there is a quality provider for
the database, the bottom line is how good the particular database system is. A
good way to test this is to compare MIcrosoft's SQLEXPRESS product (the free
version of SQL Server 2005) with whatever other product you wish to compare.
Frankly, with the sophistication of SQLEXPRESS and the tools provided for free
by Microsoft, as long as you are using a Windows OS, I'd be surprised to see any
advantages to using MySql.
But - the choice is yours to make. So -- do some testing. and make your own
decision!
|
| Post Reply
|
| Re: Can the marriage of MySQL and ASP.NET match Sql Server and ASP.NET? |
 |
Sat, 23 Feb 2008 03:15:09 +000 |
It all comes down to the support offered by the drivers available from MySQL.
I've been using MySQL Connector/NET 5.1 and it supports the features I need.
The biggest hurdle is figuring out the vague differences in SQL styles between
the two databases. I'm sure there are also many DBA's who would tell you a fine
tuned SQL Server DB will outperform a MySQL DB. Of course, if you ask the MySQL
DBA's they'll take their database every day of the week and twice on Sunday.
You will, undoubtedly, find things that you can do with the built in SQL Server
provider that you can't do with the Connector/NET provider (such as SQL Cache
Dependency). This is simply because developing these features is a priority for
Microsoft and it is not for MySQL. Duplicating these behaviors will be
possible, but you'll have to manage it.
Will you have feature for feature parity in the providers? No. Will you have
enough functionality to build a top performing web application? Absolutely.
|
| Post Reply
|
|
|
|
|
|
|
|
|
|