Re: SQL Server
- From: "JimP" <jpockmire@xxxxxxxxxxxxxx>
- Date: Sat, 9 Jun 2007 07:12:05 -0500
2 Questions
1. Where is the processing done in a pass through query?
2. One of the SQL Server programmers is pushing stored procedures, I guess
because the processing is done on the server and you're not relying on ODBC
to carry large amounts of data. Do you think a stored procedure for a
complex query is likely to have a significant performance boost vs a
traditional ODBC connection, linked tables and query?
"Duane Hookom" <duanehookom@xxxxxxxxxxxxxxxxxx> wrote in message
news:3EB6BC75-9617-47E2-9E89-C2D6EF97D4CE@xxxxxxxxxxxxxxxx
If you don't need to link to Access tables, I would consider using only
pass-through queries. If you need to change the criteria of your
pass-through
query, you can use a couple lines of DAO code to change the SQL property
of
the p-t.
--
Duane Hookom
Microsoft Access MVP
"JimP" wrote:
I'm currently using MS-Access to write reports using a SQL Server db as
the
data source in a client/server arrangement.
The database is sufficiently large (2gb) that data retrieval speed is an
issue.
The current setup is linked tables to the SQL Server db via ODBC, and
then
the usual queries.
1. Can views and/or stored procedures on the SQL Server side along with
paramaterized queries provide a significant performance boost?
2. I've read that views and stored procedures can be created w/i Access.
Is
this the same as creating them in SQL Server?
3. Are there other things I should try?
.
- Follow-Ups:
- Re: SQL Server
- From: Rick Brandt
- Re: SQL Server
- From: MH
- Re: SQL Server
- References:
- SQL Server
- From: JimP
- SQL Server
- Prev by Date: unmatched query
- Next by Date: Re: SQL Server
- Previous by thread: SQL Server
- Next by thread: Re: SQL Server
- Index(es):
Relevant Pages
|