Forum Moderators: open

Message Too Old, No Replies

ASP and MySQL

instead of MS Access

         

markfox

7:21 pm on Aug 28, 2004 (gmt 0)

10+ Year Member



Hello Everyone,

I was wondering if it was possible to for ASP scripts to connect and use MySQL databases. If so maybe someone can guide me to some usefull sites.

I currently have a asp application that uses MS Access. The application is running fine but the site has now begun to receive a huge amount of traffic and i am worried MS Access will not handle it. I cannot switch to MS SQL because of the licensing issue and cost. So i was wondering if MySQL will work, and if so would it be possible to make the switch just by editing the connection file.

Thank you

txbakers

8:04 pm on Aug 28, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Yes. You've discovered all the correct things at the correct time.

So many of us did that very thing - start with Access and migrate to mySQL because MSSQL was either too expensive or too robust.

You can do it, however, some of the SQL Syntax is not the same. You will need to download mySQL and the "connector" (odbc driver).

You don't need to connect through ODBC, but you do need to install the "connector"

Just take it slowly, check your SQL statements each time, read the mySQL manual as needed ( no need to memorize the entire thing right now ), and go for it!

You've taken your first step to becoming a serious webmaster!

Welcome.

dataguy

1:35 pm on Aug 30, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You may want to look into the new SQL 2005 Express. The price is right (free) and it will keep you on the path to SQL Server (which may or may not be important to you). SQL Server 2005 Express doesn't have the performance governor as did the previous MSDE, so as long as you database isn't too large (4 gig limit) it may be just the thing you need.

Small Website Guy

7:07 pm on Aug 31, 2004 (gmt 0)

10+ Year Member



I cannot switch to MS SQL because of the licensing issue and cost.

It costs $5000 to buy a license for SQL Server. Well worth the money. If the site is run by a real company, the cost of the SQL Server license is small compared to the cost of paying the IT staff.

My personal sites use SQL Server. How can I afford it? Shared hosting. Plenty of places where you can have a SQL Server website starting at $25/month.

jweighell

10:38 pm on Sep 17, 2004 (gmt 0)

10+ Year Member



You may want to look into the new SQL 2005 Express

Am I right in thinking that this is a *free* version of SQL Server?

I am currently using a shared SQL Server machine, but have recently aquired a dedicated webserver. I've been considering running the database on this machine - this may be an option...

Warren

2:33 am on Sep 18, 2004 (gmt 0)

10+ Year Member



Just make sure you understand the limitations of any "free" product. For example, I have seen a number of people caught about using MSDE as the back end only to discover that they have hit one of the limitations of the product.

They couldn't justify the upgrade to a "real" database.

As long as you understand what the limitations are and are prepared for the consequences when you hit those, then go for it.

dataguy

3:36 am on Sep 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



From what I read, you can't really compare SQL 2005 Express with the old MSDE, since many of the old limitations have been removed.

If you google "SQL 2005 Express" you'll get a good list of reading material to see if the new version is right for you. I haven't tried it myself, so I can't give any first-hand insight, but it sure seems like a winner.

Warren

12:44 pm on Sep 18, 2004 (gmt 0)

10+ Year Member



Dataguy

This is a new product for myself as well (I used to work at MS Australia and was very farmilar with the entire product line). Seems like quite a nice solution from MS.

The risk I see (with many different types of IT projects) its that people go for the "cheap" version initially but are backed into a corner because of a lack of planning for growth or future requirements.

It ends up costing so much more in the long run. As long as you know what the limitations are (and the risks) than that is fine.