MySQL and SQL Server 1

[jeanpierre]

I am starting out in databases. And I downloaded MySQL and have started to do simple commands.

I was wondering of the threshold of difference to learn when I migrate to SQL Server in the future. Will there be a steep learning curve in the migration?

Thank you. Jean Pierre

 

[munkyCmunkyDU]

ohhh jeanpierre...

Having worked fairly extensively in both...

Yes, there will be a significant learning curve. But the good news is that it will be mostly downhill. When you move to SQL Server you will discover that many of the things you wanted to do in MySQL CAN actually be done in MSSQL relatively easily.

.. and subqueries and stored procedures...

Well, that's a whole 'nother discussion.

For where you're at now though, MySQL is pretty good. It lacks many advanced db programming features but it's fast and can perform many of the standard database functions you will need in a typical application or website.

If you happen to be using PHP on the front-end, I would strongly recommend using the ADODB tools from

http://php.weblogs.com/ADODB

by Jon Lim. In fact, I would pretty well recommend using anything he has to offer related to PHP - its good stuff.

well - thats all for now.

Have Fun!!
munkyCmunkyDU

 

[jeanpierre]

Thanks munkyCmunkyDU,

Your posts are very helpful.

I was wondering on what the alternatives for a front-end are to PHP. I am very new to this and I am not sure why PHP was necessary.

My thinking is that the PHP gives a GUI to MySQL. Is this correct or am I barking up the wrong tree?

Thanks again. Jean Pierre.

 

[munkyCmunkyDU]

What is your end goal? What are you creating?

munkyCmunkyDU

 

[jeanpierre]

My end goal is to learn on database and the surrounding technology.

The path to get there is by developing and running an online inventory database.

Thanks

 

[munkyCmunkyDU]

You have a few choices, these are the two I would recommend.

If you have very little experienced support around you (aka other developers) and you don't have a strong company budget backing you, OR if the existing support around you (your company's IT group) leans towards Linux/Unix/Open Source/Java etc. then I would go with MySQL as a data store and PHP for your user interface.

Here are some of my reasons:
- PHP and MySQL are open source - this means "Free to good home!" They also have both been getting a lot of eyes on them for the last couple of years which has really matured the product.
- Because they are open source and inherently web related - the web is overwhelmed with avenues of support - find a few that you like and stick with them.
- PHP and MySQL are bed-buddies. They go together. I would not try a mix like ASP and MySQL. Although it's possible to do, you will find a lot more resources available to you if you stick with the main road.
- PHP and MySQL resource providers expect the novice to be in their audience. You will find things that you will understand.

For good php resources - go to phpbuilder.com, devshed.com and php.weblogs.com - not to mention php.net

----------------------

The other alternative is a Microsoft approach. I would only recommend this if you can afford it or if someone is footing the bill. If this is the case, then I would skip MySQL/PHP and jump into ASP/MS Sql Server. You can buy books for MS SQL Server that come with 90-180 day free trials of SQL Server 2000 and will take you through learning it. Also, you may be able to find a used copy of MSSQL 7 somewhere which is a good learning platform. There are many resources for this stuff. You may find some at msdn.microsoft.com, sqlmag.com, 4guysfromrolla.com (really great stuff here) and others.

Either way, there is really nothing out there that you can not learn and eventually master. Just ask questions and be ready to know that what you write now will look like junk to you in 6 months. It's ok, it's part of the process.

Have lots of Fun!
munkyCmunkyDU

 

[sjuarez1979]

I have programmed extensively in ASP. I decided to give mySQL a try and found that implementing mySQL with ASP is fairly easy. In fact, there was no learning curve at all. Personally, I feel that it really does not matter what backend you use as long as you feel it will handle the job. In the same vein, it really does not matter what front end you decide to use with it as long as you feel it will handle the job. I liked mySQL because it lacked the exuberance of the access front end which was unecessary in most Web applications that require a DB.

sjuarez1979