You are prefectly right ... But from Mysql 4 it is supporting clustering/replication etc. Regards Adrian
MySql is very popular I heard that PostgreSql also offers a lot of advantages and is becoming very popular replacement for MySql (as somebody told me recently it consumes less resources on huge databases) so I will give it a try (I mean I will try to learn about it ) As for enterprise solutions.... watch out for MySQL (or other opensource database) soon I think there will be big movements in this field
Depends on your application. The rule of thumb I use is. Thumb1: MySql - If your doing reads (SELECT *) 80-90% of the time use MySql. Thumb2: PostGres - If your application has more than 50% inserts then use PostGres. I only have two thumbs
Flat text database because for my needs it is enough and that never causes "connection refused", "invalid resource, blah, blah" and other disastrous messages returned by mysql, which btw, reveal the path where your scripts reside, creating security threats when they occur apart of the unprofessional impression. Many people may argue speed in favour of mysql, I don't deny is quicker making a query to mysql that retrieve info from a text flat database, particularly when this grow excessively. However I cannot tolerate the errors caused due the lack of control over mysql on the server. When it is your, it's fine because you can change the connection settings at your convenience to avoid them, but when you have a shared hosting or reseller hosting you rely on the hosting provider's settings. Besides, sometimes mysql is down while apache keeps running so websites using mysql are down when this occur, while those not using mysql are up. In conclusion, I only use mysql when I have no other option (i.e. installing IPB or other forum based on this database), otherwise if flat text is not enough or no convenient, I switch to my Windows Server to use a MS Access database solution.
good point i use php5 exceptions to catch these errors send me a detailed error email and show the user a nice polite message allong the lines of "ooops thers a problem with site, please try later"
Ah!, that sounds much better because if you can't prevent errors at least you can tell your visitors about the temporary problem being aware when it occurs and without comprising your absolute path.
Could'nt agree more. I've heard about lots of companies running mySQL very successfully in "THE ENTERPRISE"-environment, although I thinkg the "ENTERPRISE" environment is abit over-rated these days... hehe I'm using mySQL, PostgreSQL as my main database systems. At the moment my PostgreSQL one is the biggies, but when moved over to mySQL they performed even better. Depends all on the type of data and structure of the database. Also on the queries done as mySQL maybe performs better on a plain index search where postgres maybe will perform better on a foreign key join on multiple tables. anyways, thats my 2cents worth...
There's nothing overrated about it, its just another level of business and system complexity. Scale can be different, but there's some line between need4speed and need4HighAvailability, where you're making the choise with compromise -- and you will choose most reliably packed, documented and supported solution for HA case. Another case is when you're bound to certain DB because your, say, ERP system using it (SAP DB).
I use MySQL the most these days. I wouldn't say that it's the best and safest way to go, in fact, it lacks quite a few nice features, but really, it does the job when it comes to the web.
I use MSSql. Only way to go. Easy, powerful, all the features and integrates well with .NET. Also love the XML capibilities.
Microsoft developer here so I tend use Access, and MS SQL server in it's various flavours....MSDE, Express, 2000, 2K5. I've also got my eye on the new express version of oracle but haven't had time to investigate it yet. It looks like a contender for the MSDE/Express race but whether it has more to offer and warrants a migration is a question I have yet to answer. I would think on face value I will stick with Microsoft.