July 5, 2007 at 2:07 pm
i have an access 2003 application that uses linked tables to three backend access 2003 databases.
the front-end application has queries and reports.
i used SSMA to migrate the backend databases to SQL Server 2005. Everything went fine.
i did not think i had to do much with the front-end application but relink the tables via ODBC to the newly migrated backend databases. the execution of some of the queries from the front-end application are not working well at all.
many of the queries are based off other queiries and the speed is unacceptable...the pc seems to even lock up!
if i create a new query to just read directly from a linked table, everything seems fine however.
my question is...should i also convert the front-end .mdb via SSMA so that the queries will be converted to SQL Server views? if so, what do i do next?
July 6, 2007 at 7:19 am
July 6, 2007 at 7:41 am
In general I would say "yes" to your question. The query to view conversion works with the exception of when a query in Access calls a parameter. For those queries I recommend converting to a stored procedure.
July 6, 2007 at 8:07 am
the queries on the front-end application refer to the "local" Access tables that are linked via ODBC to the backend databases now residing in SQL Server.
it would seem like the queries would work just as they did before...only that they are getting their data now from a link to tables in SQL Server rather than another Access database.
there are over 100 queries and they are very complex. at this point i am trying to determine the business intent of each and actually if they ever really worked. this is an application that has grown over the years and i did not have a part in its design.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply