We have just migrated our back end database from Access to MS SQL Server 2008 R2. We have noticed better performance on our searches - unless we select to search in "any part of field" in Access (with Access' built-in search function - we use a mix
of Access 2003 and 2007). This takes nearly 20 seconds to find the result, whereas before the migration it was taking 5-7 seconds (compared to instant results we now experience when searching for whole fields). The main fields we search are not large - usually
just two words.
Obviously it is better to search for a whole or start of a field, but this is not always possible. The contractor that assisted us in this project has told us that this "is just the way SQL works with Access". Is this really true? I find it hard to believe
two MS products would have such a big issue between them. I presumed using SQL with an Access front end would be a common setup, which is why I thought this must be a problem with our setup.
Is there any way to fix this speed issue?
Edit: Alberto, thanks for the reply. I'm glad its not just me who thinks it isnt right!
However, Indexes are set up, and are scheduled to defrag every night, so they shouldnt be a problem.
I notice you refer to queries - it isnt a "query" as such (at least not with Access' terminology). All our queries run fine, it is just the built in search option that causes a problem (eg the data is displayed on a custom form, press ctrl+f to bring up the search dialog, enter search term), and even then only when the specifc option of search "any part of field" is selected.
The contractor has already used the SQL Server Profiler tool to test the searching - apparently you can see hammering the server with requests as it searches through, but it didnt help them come up with a solution. I think I will investigate this avenue myself.
Any further comments?
Thanks for the help,
Ross