Then the next place to look is in SQL Server. Make sure you have an index on the table that matches the column order of your WHERE clause. It sounds like you may be doing one massive table scan.
>I've tried increasing the ScriptTimeout property and inserting few conditions to my select statements so as to filter records from a MS-SQL table. I also tried changing parameters/properties of my computer's registry. Still, the same error keeps on appearing.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
