Re: Migrating away from MS-Access
- From: John Casey <john_casey@xxxxxxxxxxx>
- Date: 19 Oct 2007 10:49:38 GMT
In my experience, if you convert your Access tables directly over to SQL
Server and do not modify the front end code, you will end up with a
slower application. Regular SQL queries will still need to pull all the
data down from the server before it can process it. All of the existing
SQL queries will need to be converted to stored procedures to see any
type of performance gain.
Also, if the entire Access database resides on the server, this will
cause a performance issue. First try and split front end from backend
(data) and place the front end on the users desktop. I am sure you can
find several possible solutions to update the users front end
automaticaly as modifications are made to it. Later try and pull as many
not core data tables out of the back end and into the front end as they
are found. These tables are usually static tables used for drop downs,
temporary data handling, etc...
Next try and do as much query processing on the front end as possible.
For example if you are running a complex account report lets say, first
just pull down all required fields from all of that account records for
the report. Then do the remaining queries on the front end...
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- Re: Migrating away from MS-Access
- From: David W. Fenton
- Re: Migrating away from MS-Access
- From: (PeteCresswell)
- Re: Migrating away from MS-Access
- References:
- Migrating away from MS-Access
- From: John
- Migrating away from MS-Access
- Prev by Date: Re: Migrating away from MS-Access
- Next by Date: Linking Access data to Excel
- Previous by thread: Re: Migrating away from MS-Access
- Next by thread: Re: Migrating away from MS-Access
- Index(es):
Relevant Pages
|