Re: Access and processor usage
- From: Rich P <rpng123@xxxxxxx>
- Date: 04 Apr 2007 22:24:19 GMT
If you are pulling data from a sql server (MS Sql Server, Oracle, ...)
and you are using an ODBC connection, that would be your bottle neck.
The fix is to use ADO (com based ADO) to pull your data (much more
bandwidth than ODBC). If Access is your backend, then Access is the
bottleneck - need to step up to Sql Server.
If neither of the above are your scenario, and you really are pulling in
hundreds of megs of data, then Access is still the bottleneck. Access
has a 1 gig data limit (more like a 500 meg limit). If you are working
with genuinely big data you need to step up to server based tools like
Net and sql server. ADO.Net has way more bandwidth than com based ADO.
BTW, core2Duo is sweet, heh? I just upgraded my workstation to one last
month - the shop that upgraded me said that you can maximize its full
potential by using 4 gigs of memory.
Rich
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- Re: Access and processor usage
- From: '69 Camaro
- Re: Access and processor usage
- References:
- Access and processor usage
- From: WannaKatana
- Access and processor usage
- Prev by Date: Re: Access and processor usage
- Next by Date: Re: modeling tools useful for Access
- Previous by thread: Re: Access and processor usage
- Next by thread: Re: Access and processor usage
- Index(es):
Relevant Pages
|