Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: open
My question is when should I be looking to upgrade?
Traffic: Almost 8000 page views a day (6 views a minute)
Access db size:
12.5 MB (expected to grow to 15MB in 2 years
About 1500 records
Programmed in very efficient none inline simple Classic ASP
[edited by: Johan007 at 8:26 am (utc) on April 11, 2008]
I'd recommend switching to SQL Server asap if possible. There is a relatively simple upgrade path from Access. The other alternative is some form of caching eg generating static pages from your database.
In the meantime 12.5MB seems big for a db with only 1500 records - is this correct? Are you storing binary data? Are you doing lots of updates or just pulling info from the db?
I feel the db works well but I guess I need to bite the bullet lean mySQL some time.
[edited by: Johan007 at 1:48 pm (utc) on April 24, 2008]
joined:Dec 10, 2005
Biting the bullet and learning mySQL would definitely be a good idea. It will not only improve this site, but will also increase your marketability with an additional (and very important) skill.
I did it last year. There are some free conversion tools (on the official MySQL site if my memory serves me right) which work well.
If you want a graphical front end for MySQL there are several available, I use NaviCat which is pretty good.
If you are on Windows hosting, does your host offer MySQL? Part of my reason for swapping was moving to Linux/Apache hosting.
can you get MySQL on Windows hosting?
You can, but I'm not sure how common it is.
Windows hosts tend to use MS SQL and ASP (more likely .NET these days), while Linux hosts use Apache/PHP/MySQL.
I swapped ASP for PHP because I didn't like .NET. Buts that's a very personal decision, PHP suits my coding style - quick and dirty!
Actually PHP is very easy to learn, it took me about a week to learn enough to move a simple site. There are plenty of free scripts for forums, shopping carts, blogging , etc. So perhaps you don't need ASP as much as you think!
With your existing Access database it might be worth either writing an application to compact the database (go google 'asp compact access database') or download it and compact it offline if feasible. You can get quite dramtic size reductions doing this.