Forum Moderators: open
I have no choice at the moment but use Access as the database backend (no choice, really).
Realistically,
(1) can my site handle say 1000 pageviews daily if much of the content is pulled from Access tables? How about 5000 page views? Let's assume that the db is well designed.
(2) how many concurrent users can this site support at any given time?
(3) I have broken down the entire database into multiple independent mdb files to lighten up the load of each mdb. Will this help?
By the way, Iam using ADO 2.8, dsn-less.
When SQL Server is finally available, I'll migrate. But for now Iam really stucked with Access.
Hope you guys can help out.
Thanks.
My feelings:
1. use a better database if you can
2. If you have control over your server, compile the business logic as MTS components rather than running as a script. instantiate and call the components from your asp.
3. when reading, use disconnected recordsets & close your connections as quickly as possible.
4. use error handlers & transaction based updates to ensure writes happen. (The previous comments about concurrent operations are right. Access doesn't handle them well.)
5. post to a log from your error handlers. If you are having a problem, (I.E. failed writes) you might never know otherwise.
I have used access for the application database on a number of web based apps. I have also used Access in higher load applications that are not web based (we're talking around 250000 reads and writes a day). It will work if you implement correctly.
Good luck with it.
Last week my last Win2k box died and I quickly had to migrate about 30 sites to a shiney new Dell running Win Server 2003. Within minutes of getting my first site up which uses Access, I had the database lock up. If fact, it locked up so bad that once I stopped IIS, it wouldn't restart. After about 15 minutes of experimenting, I finally rebooted, which solved the problem until it locked up again, 3 hours later. The worse part is that when the Access database locks up, it takes out ASP processing on that web site and every other web site that uses the same Application Pool, which by default, they ALL share.
7 Days later I have the troubled web sites isolated in their own app pools, but I still have to reboot that server several times a day. I've updated the MDAC and the Jet drivers, and tweaked the app pools, but I'm still loosing the battle....
Can't wait to get them migrated to SQL Server....
If you install MSDE you can use Access to manage it. It's not intuitive but it does work. You can design tables, stored procedures, assign permissions, backup the database, and almost everything else you can do with Enterprise Manager.
Here's another option. You can install MSDE and then only the tools in the free SQL Server Evaluation download. Those tools include EM, DTS, Query Analyzer, Profiler and everything else you get with the full SQL Server. Unlike the database in the evaluation version the tools continue to function indefinitely. To me that gives you the best of both worlds even though there are some limitations with MSDE like the 2GB database limit.
From all the discussion above , i gather that - migrating to mysql would definitely speed up my pages, isnt it?
But i am a novice to mysql. Any help in this regard is appreciated.
Regards,
MB
Note: I know asp, have a lot of asp pages on the website i am working on, and intending to design new sections in asp.net, retaining all the old pages in asp.
An early reply is needed.
Regards,
MB
MySql, although free, is more for PHP and CGI.
[Unfortunately, Money is A BIG ISSUE...
I am not a professional programmer or the one who is getting paid for what i am doing. I just take some free time out from my schedule (right now, u can say i am addicted to net).
It's just pure love for computers, that i designed my first website (to help me in my studies). But gradually, while maintaining and upgrading it, i came to learn alot. Anyway, back to our topic..]
I have realised that i do not have MS SQL in my hosting service plan. And so i will have to stick to mySQL (or end up paying more...)
Asp / Asp.net is not my fascination. However, as there is not going to be an improved version of asp in future, so i am planning on asp.net
If however, php / perl is better you can PLZ advice, as i have never worked on them BUT I AM READY TO DO ALL THE HARD WORK (if its worth the effort).[It is better to redesign now than in future, when i will have much more pages.]
Besides, i am on a new website project, starting from scratch, so please do advise on the scripting language to use (PHP / PERL / ASP / ASP.net / ANyother)
Regards, (and thanks for the reply to my post)
MB
If you've been running on an Access DB, you probably won't notice the difference between running MySQL with PHP vs ASP because EITHER option will be much better than what you are using right now. It might even be a good idea to switch over the MySQL first with your ASP pages and then try tinkering around with PHP to see if it's really worth it to learn a new programming language.
However, I do suggest looking around for a web host that offers a small MS-SQL database. You can usually find them for as low as $50/month.
I get it that - mysql works better with PHP/PERL & MS-SQL works better with ASP.NET/ASP
Considering the number of portals and discussion forums available for php , made me think that may me i need to shift to it from asp / asp.net
However, i don't know which is better for future (scalability) among PHP / PERL / ASP.NET
Regards,
MB
Regards,
MB
MySQL is better suited to the PHP/Perl world and MS-SQL is better suited for the ASP.NET/ASP world.
This is flat out not true.
MS-SQL and mySQL are databases.
PhP/Perl/ASP are web scripting languages.
They have nothing to do with each other.
You can run either database with either scripting language and it will be just fine.
the only reason "tech" people lump PhP with mySQL is that both are open source products and are available for free.
Regards,
MB
