Get around Access traffic limits?
My understanding is that an Access database is okay initially, until it starts getting a certain "load" of hits against it, then one usually converts to SQL 7.0.
Two questions:
1) How will I know that I need to do this? It will cost me money to buy SQL, as well as to upgrade my web hosting account, so I'd rather put this off as long as possible. What types of errors will I or my visitors see that tell me it's time?
2) I thought of a way to get around this, for awhile at least. Is there any reason that I couldn't put up several identical copies of my Access database (which is read-only, as far as visitors are concerned) on my site, and randomly hit one for each query? For example, I could put up 4 copies, and on each "open" use a random number generator returning 1 to 4 to determine which particular copy to use. Other than taking up more of my space (not an issue now), and the minor hassle of making the copies, are there any downsides to doing this? (I'm using DSN-less connections for now, so using up my DSNs is not an issue, either.)
Still in "pre-launch", but things are coming together...
------------------
http://www.RewardsLookup.com
Kristen
http://www.RewardsLookup.com and
http://www.cancerdrugfeedback.net still under early development
Personal page:http://www.isd.net/kwong/kristen.html
Peter J. Boettcher posted this at 18:35 — 8th May 2000.
They have: 812 posts
Joined: Feb 2000
KLWong,
1) You'll know you're starting to have problems when your scripts start timing out, due to the fact that Access is busy with to many other users.
2) While this would would work, it sort of defeats the purpose behind a central db. Will you be synchronizing these databases so the data is the same in each?
You don't really have to "buy" SQL Server. As long as your host installs the server portion, all you need is Enterprise Manager (part of the client install). You can get a SQL Server 7 evaluation copy and just install the client tools, I don't think the client portion ever expires.
Regards,
Peter J. Boettcher
PJ | Are we there yet?
pjboettcher.com
KLWong posted this at 18:53 — 12th May 2000.
They have: 135 posts
Joined: Apr 2000
Sorry to take so long getting back, but thanks for your answer!
The way I am managing my database is by keeping a "master" on my personal hard drive and uploading copies to my website whenever the data changes. Since the database content never changes except in the master, this workaround would only mean that I'd be uploading several copies at a time, instead of one.
Also (correct me if I'm wrong), wouldn't I need to buy a copy of SQL Server to continue with this "master at home, copy on the web host" paradigm? Could I do maintenance and everything on the local master database without it, or is that what the Enterprise Manager does?
------------------
http://www.RewardsLookup.com
Kristen
http://www.RewardsLookup.com and
http://www.cancerdrugfeedback.net still under early development
Personal page:http://www.isd.net/kwong/kristen.html
Peter J. Boettcher posted this at 20:16 — 12th May 2000.
They have: 812 posts
Joined: Feb 2000
KLWong,
Maybe the best thing to do is to keep your Master database in Access format and just import it when it changes, into SQL 7. To do this you would need:
1) Access on the master computer
2) Enterprise Manager on the master computer
3) SQL Server on the Web Server
Importing is fairly easy using a wizard, or if you're comfortable you can use a SQL statement.
This would work if there's no issues with script timeouts on the master computer (it sounds like you don't use the DB for web stuff on the master computer).
Regards,
Peter J. Boettcher
PJ | Are we there yet?
pjboettcher.com
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.