Author |
Topic  |
|
leatherlips
Senior Member
   
USA
1838 Posts |
|
laser
Advanced Member
    
Australia
3859 Posts |
Posted - 18 March 2006 : 19:20:13
|
Ideal ... hmmm, MySQL maybe
Does it matter ? ... certain mods are written with Access in mind and may strike problems on mySQL, the probability is quite low though
Advantages ... Access is "normal" Windows stuff, mySQL can handle more connections Disadvantages ... Access will eventually run out of puff on larger sites, to edit mySQL you need to install it or use a web interface like phpMyAdmin
It's a close call either way, but if I knew more about mySQL when I first started I probably would have chosen that over Access. When my forum got "too big" for Access I moved to SQLServer. |
 |
|
Jezmeister
Senior Member
   
United Kingdom
1141 Posts |
Posted - 18 March 2006 : 19:32:00
|
quote: Originally posted by laser
to edit mySQL you need to install it or use a web interface like phpMyAdmin
Not true, there's a lot of windows compatible and easy-to-use managers for MySql almost all of which are much better than phpMyAdmin.
If the choice is access and mysql and you need to ask then go with access as it's obviously not giving you any grief. If it is struggling with the load then I would definately choose MySql over MS SQL - for cost if nothing else. |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 18 March 2006 : 20:34:45
|
Well, sometimes cost is not limited to what you actually pay. Given the choice of the two, I would always go with SQL Server. Some Snitz code won't work properly with MySQL 5.x, and the problem does not lie with Snitz... For the same amount of data, I've found MySQL needs a lot more tweaking than SQL Server, indexing wise. So, sometimes cost is the least of your problems and you can have good hosting offers with MySQL and SQL Server for the same price or very similar. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
leatherlips
Senior Member
   
USA
1838 Posts |
|
spyderuk
Junior Member
 
United Kingdom
211 Posts |
Posted - 22 March 2006 : 20:02:52
|
Leatherlips Access is holding out for me, for now. 
86 of 128 Members have made 3209 posts in 17 forums, with the last post on Today 00:53:44 by: MCFC Marky. There are currently 430 topics and 5 active topics since you last visited. There are 243 archived posts in 53 archived topics
DB is currently 3.63Mb which I think is a healthy size. Forum can be slow sometimes but I think it is a server issue more than anything, seems to be up and down recently.
If you don't have more than around 10-12 active users and around the same details as above you should be fine with access. I gonna see how far access can go  |
Snitz 3.4.05. Mods Installed, Additional Smilies, Poll's, PM's, Email All Users, Today/Yesterday, Active Users 4, Portal Mod, My Own Google, Referer Mod, Avatars, Intergrated Conqueror Chat, Usergroups, IPGate, File Attachment Mod & Image Resize Mod.
Next Mod? My Snitz Forum 
|
 |
|
AnonJr
Moderator
    
United States
5768 Posts |
Posted - 23 March 2006 : 09:04:16
|
Just remember that with Access the key is the volume of simultaneous users. The program I wrote for someone is running into problems not because of how many users there are, but how many users there are at the same time. I'm planning on migrating everything I can to either MySQL or MS SQL (depending on which is available) now so I don't have to worry about it later... but that's just me. |
 |
|
leatherlips
Senior Member
   
USA
1838 Posts |
|
AnonJr
Moderator
    
United States
5768 Posts |
Posted - 24 March 2006 : 14:22:04
|
I suspect read-only recordsets are a little different, but the basics of what I've read around are that Access databases can't handle much more than 10-12 requests to 'do something'.
Remember that once the page is delivered to the user, they are no longer using up a connection to the database (or the server for that matter). Also, as mentioned elsewhere in these forums, for the big operations instead of opening a recordset and running through it (which uses up one of those connections) it dumps the recordset into an array and works with the array leaving more potential connections available.
Its worth noting that the '10-12' number is a rough guesstimate and really depends on code optimization, memory, (probably) which drivers you are using, (probably) what version of the drivers you are using, and probably more things than what I know of. Having said that, my experience has shown that its a good number to work by.
I'm probably not the most knowledgeable person on databases here on this forum, so take what I say with a grain of salt. I know a lot about database design and use (normalizing data, setting up tables and relationships etc.), but not as much about the nuts and bolts of database engines.... Did I just help clarify or confuse? |
 |
|
|
Topic  |
|