From: a a r o n . k e m p f on
make sure that all Access tables get moved to SQL Server to increase
performance. Creating queries against a mix of Access (Jet) and SQL
Server using linked tables can be very resource-intensive.

http://technet.microsoft.com/en-us/library/cc917601.aspx
From: Tony Toews [MVP] on
"a a r o n . k e m p f @ g m a i l . c o m" <aaron.kempf(a)gmail.com>
wrote:

>make sure that all Access tables get moved to SQL Server to increase
>performance. Creating queries against a mix of Access (Jet) and SQL
>Server using linked tables can be very resource-intensive.
>
>http://technet.microsoft.com/en-us/library/cc917601.aspx

"Migrating Your MS Access Database to MS SQL Server 7.0
Updated : July 19, 2001"

Just a little out of date.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
From: Arvin Meyer [MVP] on
"a a r o n . k e m p f @ g m a i l . c o m" <aaron.kempf(a)gmail.com> wrote in
message
news:2966ac44-e6f1-422f-b5e2-946bf7f8b146(a)n11g2000prh.googlegroups.com...
> make sure that all Access tables get moved to SQL Server to increase
> performance. Creating queries against a mix of Access (Jet) and SQL
> Server using linked tables can be very resource-intensive.
>
> http://technet.microsoft.com/en-us/library/cc917601.aspx

You do realize that the article is 9 years old and contains advice which may
not have been the best even then? SQL-Server 7 was quickly replaced by those
of us developers who very quickly realized how much better SQL-Server 2000
was. Since then there have been 5 versions of both Access and SQL-Server.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access


From: Dirk Goldgar on
"a a r o n . k e m p f @ g m a i l . c o m" <aaron.kempf(a)gmail.com> wrote in
message
news:2966ac44-e6f1-422f-b5e2-946bf7f8b146(a)n11g2000prh.googlegroups.com...
> make sure that all Access tables get moved to SQL Server to increase
> performance. Creating queries against a mix of Access (Jet) and SQL
> Server using linked tables can be very resource-intensive.
>
> http://technet.microsoft.com/en-us/library/cc917601.aspx


The article is about procedures for upsizing an Access database to a SQL
Server back-end. The quoted passage is a caution to avoid joining linked
SQL Server tables and local Jet tables in queries, as that will be very
inefficient. It is in no way a statement that all tables in all Access
applications should be kept in SQL server.

--
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

(please reply to the newsgroup)

From: Gina Whipp on
I see you are still referencing old material... oh well.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"a a r o n . k e m p f @ g m a i l . c o m" <aaron.kempf(a)gmail.com> wrote in
message
news:2966ac44-e6f1-422f-b5e2-946bf7f8b146(a)n11g2000prh.googlegroups.com...
make sure that all Access tables get moved to SQL Server to increase
performance. Creating queries against a mix of Access (Jet) and SQL
Server using linked tables can be very resource-intensive.

http://technet.microsoft.com/en-us/library/cc917601.aspx