Never used MySql

[stormcloudgathering]

Hi chaps
OK...we're a SQL Server site through and through, loads of skill and experience inhoue, and we have to lie down in a darkened room at the mere mention of Oracle or AS400.
Our print department is in dire need of an MIS and have found the one they want. It meets all the business needs, fits with everything strategically, but it sits on a MySql database.
At first the IT manager had a fit, but after many discussions with the vendor we all feel a little less discomfited.
We're nervous about things like installing the latest security patch on Windows only to find it screws up MySql and because it's not the application the vendor may or may not be able to help us.
I would be interested in your collective opinion - good or bad on our proposed implementation.
DO I need to get my IT boys trained up on this - is it way different to MSSqlServer?
Are there any pitfalls I should be aware of?

Your help is much appreciated
thanks

 

[KarveR]

I'm at the opposite end, one of our suppliers is pressing us to take up MSSql .. we run MySQL and have been doing so for 6+ years now.

I guess I too need to know the differences between the 2.

______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.

 

[bastienk]

We use both for our apps (db allowed to be client driven). there are some differences wrt adminning the db and backup and recovery. This is where most of the learning curve will be. We find it very stable and simple to manage. Since the app is from the vendor and includes the db, I doubt you'll have to do a lot of db/table maintenance. Hopefully most functions are included into the app.

Its well worth bookmarking the mysql.com site for the manual, it will answer most questions that you may run across.

The one thing that may be problematical is upgrades to newer versions of mysql as you may feel the need. Perhaps the vendor will manage this...

SQL Server is more complex to manage (it does more things) but we have no real issues with either.


Bastien

Cat, the other other white meat

 

[Crowley16]

well, I certainly wouldn't put it past microsoft to make future "upgrades" to MSSqlServer that'll mess up intergration between other non ms products like MySQL

Unfortunately, since everyone else is using ms, there's nothing u can do but conform...

 

[bastienk]

Crowley16

Sure you can, move to linux with postgresql/mysql


Bastien

Cat, the other other white meat

 

[sleipnir214]

Crowley16:
It's not a matter of MSSQL's being compatible in future to MySQL.

It's a matter of both database servers' providing client access libraries. All you need then to get data from one to the other is a client that can use both libraries simultaneously.



Want the best answers? Ask the best questions!

TANSTAAFL!!

 

[dchristensen]

Regarding the support issue, you can purchase a variety of support agreements from MySQL AB. The actual MySQL mailing list has been an invaluable source of information and help, but having a direct line to MySQL support is nice, too.

 

[ingresman]

It's a good db if you don't expect a great deal !!. Traditional mysql has no stored procs, triggers , transaction etc. It is however great for web apps as it is really quick (because it has no overhead). Like all things it's horses for courses if you don't want to pay the (sometines eye watering) license fees off you go. As for interaberability between mysql and anything else, its got an ODBC and a JDBC driver so the worlds your oyster. For support post on the tek-tips forum and you get some really good advice.