General discussion


Consider MySQL for Windows

By debate ·
What database does your organization use? What experience do you have with MySQL? Do you agree that it's a viable solution for government IT shops? Share your comments about the potential of MySQL, as discussed in the Aug. 12 Government IT e-newsletter.

If you haven't subscribed to our free Government IT e-newsletter, sign up today!

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Upgrade Option

by USMCLOGdBA In reply to Consider MySQL for Window ...

We've been using MS Access 97 for over 5 years w/o troubles. In the past year, an IT refresh has forced many users to use Access2000. I successfully converted our database, but I despise the new 'feel' of Access 2000, so I run both while primarily staying in Access 97. If I were to choose MySQL, would my users have to have any thing on their workstations beyond Access 2000? How difficult is it to use an Access front end with MySQL as a back end? I think I need more information before I go downloading a whole new scheme.

Collapse -

Single-user Experience

by bw65 In reply to Upgrade Option

First, I'd recommend that you go to one of the extremely helpful MySQL community forums and ask the folks there the same questions. From my own experience, I know you'll get some great advice to use in deciding which way to go.

In my case, I simply had to install MyODBC and set up a System DSN. MySQL's User and Host tables needed to be configured to allow connections from the host/user that I came in as. It's been awhile since I've done anything with MySQL, but I recall that you can specify access permissions for all users from a range of IPs and that it's not terribly painful to do this.

Again, ask the pros at I'd recommend both the 'MySQL on Win32' and 'MySQL General Discussion' groups.

Collapse -

Great DB

by bw65 In reply to Consider MySQL for Window ...

MySQL is a great database. I worked at a firm which used it as the database behind an online ad system. MySQL 3.22 was loaded on a Solaris machine and I managed it from a W2K box. As the article states, I had a very easy time connecting to it using Access, Excel, and Cold Fusion. Using the MySQL command center for graphic manipulation of tables was also a snap -- though I tended to do most of my work from the (UNIX) command line/prompt. My firm didn't have a support contract, but I found the MySQL user community very helpful and consequently didn't see the need to obtain commercial support.

I agree with the author's assertion that MySQL is a viable choice for the Government IT world.

Collapse -

Not Really

by mattohare In reply to Consider MySQL for Window ...

Until MySQL enforces foreign keys in all instances, authors on this site should not call MySQL a relational database. There's more to business than setting void foreign keys.

Collapse -

MySQL is easy to use

by peter.suehlo In reply to Consider MySQL for Window ...

We use both, MS Access as Frontend and Oracle as Backend for our Dataprocessing. For our Website we change for security reasons now from Windows2000/MS Access to Linux/MySQL and we have good experiences. MySQL is easy to install and you can put it on a notebook to develog at home or at train or where ever you want.
For Websites with great contents on text it is usefull, that an fulltextindex is included. If you want to use fulltextindex at an Oracle-database, you have to pay extra charge.

Collapse -

The Ultimate Question

by USMCLOGdBA In reply to MySQL is easy to use

I guess what I really want to know is WHY depart the MS Access pattern when it is clearly working and working well? What in the world can MYSQL, Oracle, or any other database system do for me that Access can't? I've been researching, testing, and experimenting with all of them for months now, and all I've discovered is that there is a 'prestige' or 'status symbol' associated with the database system you use. They all seem to be the same for my purposes. I don't see any advantages for leaving Access. There is an old saying which we've all heard and probably practiced at some point in time: "If it aint broke, don't fix it!" (which by the way, I wish Microsoft had pressed this motto to task before creating Access 2000)

Related Discussions

Related Forums