severe search slowness after upscale

[dmcdivitt]

A user group has an ms access application with forms in a front end and database in a back end. But the front end is a compiled accde and they don't have the original. They've been using this for several years. Because they have too much data we said we would upscale to sql server, and made a test set up. Everything went fine, but they do searching in the application by way of the wizard, which means they click the binoculars after selecting a field. On the sql server this takes a long, long time, while their original setup works quickly.

If I had the source code I would make them some search screens.

Does anyone have any ideas how the searching they do can be improved against the sql server? I tried indexing some of the fields to see if that would help, but no, and I didn't think it would.

The users are obviously faced with a decision which way to go for their needs. But I do want to see if there's any way possible to improve sql server.

 

[Minty]

if you can (it depends on the runtime version and a number of other factors such as if the forms allowed filters etc.) instead of searching use the filtering that can be found by right clicking the field. It's pretty instantaneous by comparison.