Well, I know little of applications that require seach over LARGE indexed cursor, for example, interactive search in grid. Instead I usually make Search form, where you enter one or more search fields, run query and it returns result into grid. In my search query number of rows in result usually limited to 200..1000 records because when user really search something, he/she do not need much of result rows because search criteria allows to find something quikly. With SQL server it works VERY well. In addition, I made Interactive search for SQL Server that works ok too without downloading of large cursor locally.
When you build applications for SQL Server, you need to think by completely another way. With SQL Server often query to server is better way than download large data to local machine and work with it locally further. This because users usually do not use 99.9% of these data.
[sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]