OK Spike ;-), I will certainly say it is a sweeping statement but based on experience it is far far better.
I am not sure you mean about destroying a DB and restoring? With SQL Server it is certainly far better to totally avoid using Enterprise Manager as it is evil, I will give you that - stick to QA....and/or other backup tools such as Red-Gate tools to restore DB's in a few mins, OR take periodic detach db snaps which you can attach in a matter of seconds via QA. -----Original Message----- From: Spike [mailto:[EMAIL PROTECTED] Sent: 24 February 2005 16:34 To: CF-Talk Subject: Re: Pro/Con Moving from MSSQL to MySQL That's a ridiculous thing to say without at least qualifying it. MySQL is a far better tool for me than MSSQL because as a developer I often need to be able to destroy an existing database and replace it with a backed up version. With MySQL I can do that in a matter of a couple of seconds from the command line, or from a batch file. With MSSQL I need to open up Enterprise manager and run the restore database backup function praying that CFMX has dropped any existing connections because if it hasn't I'll have to go stop that before doing the restore. There's no doubt that there are times where MSSQL is a better fit, but blythely assuming that it's always the case is naive at best. Spike Robertson-Ravo, Neil (RX) wrote: > Well, whatever you think of Microsoft, SQL Server is far far better then > mySQL will ever be (cost aside that is!). > > > > -----Original Message----- > From: Mark W. Breneman [mailto:[EMAIL PROTECTED] > Sent: 24 February 2005 16:27 > To: CF-Talk > Subject: RE: Pro/Con Moving from MSSQL to MySQL > > Yeah, I thought that question might come up... > > We are configing a new windows 2000 webserver server and the owner walked up > and just asked out of the blue what if we install MySql and not MSSQL. (and > no this was not a Dilbert Pointy haired Boss sorta moment.) We have talked > about moving to a non Windows platform for our production servers in the > future. And since MSSQL only runs on windows we would need to move to > another database platform. We are still in the very early stages of mapping > out our tech plan for what OS platforms we want to use in production. So, > nothing is set in stone just yet. I am primarily just doing research now, so > I thought I would ask people who have worked with MySQL and have good and > bad experiences. > > Thanks, > > > Mark W. Breneman > -Cold Fusion Developer > -Network Administrator > Vivid Media > [EMAIL PROTECTED] > www.vividmedia.com > 608.270.9770 > > -----Original Message----- > From: Jochem van Dieten [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 24, 2005 10:07 AM > To: CF-Talk > Subject: Re: Pro/Con Moving from MSSQL to MySQL > > Mark W. Breneman wrote: > >> >>We are in the early stages of *thinking* about moving away from MS SQL >>server and moving to MySQL. > > > Why? What do you hope to gain from this move? > > Jochem > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196322 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
