Michael Brösdorf
michael.broesdorf at web.de
Mon Apr 28 06:36:00 CDT 2003
Hi Selina, I had the same problem with some queries that where filtering data. Access obviously had to read the whole table(s) and did the filtering locally, which caused a lot of network traffic. Doing the filtering on the server using a view greatly reduced the amount of data sent over the network thereby increasing performance considerably. You can use the SQL Profiler that comes with SQL-Server to see what exactly gets requested from the server by ODBC. I found that a very usefull tool to find performance problems. HTH, Michael -----Ursprüngliche Nachricht----- Von: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]Im Auftrag von Selina Iddon Gesendet: Samstag, 26. April 2003 07:09 An: dba-sqlserver at databaseadvisors.com Betreff: [dba-SQLServer] Why is it so? Hi Everyone Can someone please explain the following. I had a SQL database with a Union View which took 4 seconds to open inside SQL. Using ODBC connection linked table with Access, it took 20-23 seconds to open. Trying all kinds of things I eventually made a new SQL View which did nothing but show all fields in the Union View. I then linked the new view and hey presto, Access also only takes 4 seconds to open it. Great that it worked, but I'd love to know why. Thanks Selina _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com