MySQL to MSSQL

I havent used MSSQL in a couple of years now, and even when i did use it wasnt for long. Well i needed a quick guide to MSSQL and found one on Sitepoint.com.

Its about an hour long and skips all the junk like installing - so if you need to play catch up check out:- sitepoint.com/article/sql-server-2000-database

Posted: 07-Mar-2005

View: 2495

Permalink: here

Comments

just out of curiosity andy, what makes you want to come out of MySQL to go to MSSQL? project specifcations for a client? something mysql doesnt do?

#1 Ryan Guill
07/Mar/05 8:01 PM

Really its a bit of both, though not for a client but for the company i work for. We have MSSQL server sitting on the back-end running along side some legacy apps and MySQL on the front-end(web server). Replacing a back-end DB is enough trouble at best and as the SQL server is deeply routed, replacing it with MySQL would be a big enough project on its own - thats reason 1.
2. The use of triggers and stored procedures. If MySQL 5.0 was stable now then we might of changed current deployment strategy and would of at least looked into creating a project for #1.
3. Support - in a nutshell we the developers support the MySQL install. But as the MSSQL server has critical data stored on it we have got some good support contracts all ready paid for to give everyone ease of mind.

Moving towards a complete MySQL deployment stategy would of been neat. I mean the lowest level of support is £154 ($295) at the moment, thats a steal, but until it starts to incorporate these "enterprise" level features, when it comes to the the crunch it just cannot compete

#2 Andy Jarrett
08/Mar/05 12:21 AM