If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
SQL server backend
My mdb file is moving tables from mdb backend to ODBC link to SQL
server tables, but queries are in the front end. Should I change the queries to stored procedures to increase performance or I can leave the queries in the front end mdb file that the SQL server analyze the queries at server end even I have queries in the front end? Your information is great appreciated, |
#2
|
|||
|
|||
SQL server backend
In many cases I find that the performance of queries that are using links to
MS SQL database have very good performance. In some cases stored procedures are faster or have more capability. I generally just use odbc to do the queries unless I am having a performance problem. If I do have performance problems I will then look at alternative solutions - pass through queries, stored procedures, etc. I have tables in SQL server with millions of records and unless I do something foolish (like return a million records) the performance is fine. John Spencer Access MVP 2002-2005, 2007-2010 The Hilltop Institute University of Maryland Baltimore County inungh wrote: My mdb file is moving tables from mdb backend to ODBC link to SQL server tables, but queries are in the front end. Should I change the queries to stored procedures to increase performance or I can leave the queries in the front end mdb file that the SQL server analyze the queries at server end even I have queries in the front end? Your information is great appreciated, |
#3
|
|||
|
|||
SQL server backend
I'll echo John's observations ...
Unless there are performance issues, I tend to keep the queries in the front-end. The one exception is when I need to repeatedly (i.e., in several different contexts) work with the same "filtered" subset of data. In that instance, I'll create one/more views in SQL-Server and link to the view(s). That would be another alternative to creating SPs. Good luck! Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "inungh" wrote in message ... My mdb file is moving tables from mdb backend to ODBC link to SQL server tables, but queries are in the front end. Should I change the queries to stored procedures to increase performance or I can leave the queries in the front end mdb file that the SQL server analyze the queries at server end even I have queries in the front end? Your information is great appreciated, |
Thread Tools | |
Display Modes | |
|
|