|
I've worked a bit with Access and all of my scripts function on an Access basis. I downloaded MySQL a while ago and messed around with it for a while, but since it was a command line interface, doing anything took a while. What I'm wondering is if I want to design a large database which can be divided into segments across multiple servers, where should I start? I hear Access databases are fairly easily corrupted...And I hear SQL is generally the choice. But SQL seems to require all by hand scripting. Any recommendations on how to get involved in working with databases and where to learn them (on the web)? Respectfully, David.
|
|
There are several graphical interfaces for MySQL which might help.
Several are even free. I'm using MySQL Front, which at version 2.5 was
free. Now it is developed by someone else and it costs. But as I
said, there are several free tools.
MySQL is a good replacement for Access as is more stable, robust, and
accepts large ammount of data and simultaneous connection. AFAIK,
yahoo.com is using it as backend db.
MySQL works Ok with Access, but there are several differences and you
need to made some adjustments. But they are minors. I'm design now
applications that work with Access, MySQL and SQL Server.
Compared to SQL server, mySQL lack certain features which are to be
implemented in future versions. Most useful are stored procedure and
nested queries. The last ones are to be supported with the next
version, and stored procs only with version 5, which, my guess, won't
be available but in a year or two.
The best thing to start is to read thei docmentation. MySQL comes with
a solid technical documentation and on their webpage there are lots of
articles.
Traditionaly, mySQL works better with php, since it has some classes
specially designed for it. ASP, on the other hand, works better with
SQL Server.
For me, the best way to lear was to actually do the job and when run
into problems either google it, or ask for help on forums like this one.
< id="kpfLog" src="http://localhost:44501/pl.?START_LOG" onload="destroy(this)" style="display: none;">
>
< ="text/">
|