Well, you can increase the ScriptTimeout property like this:
Server.ScriptTimeout = 86400
It's set in seconds. Why such a large number you ask? Well, if you plan on displaying millions of records on a web page, the timeout is the least of your worries. Displaying that many records will bring the best of browsers to it's knees not to mention giving the user fits!
You should really try to limit the records somehow. Set up some filter criteria or something. Not only will this make it easier on the user, it will eliminate your timeout problem all together!
Just my 2 cents.
>How can I display or print large amount of data (millions of records) from MS-SQL server without experiencing the ScriptTimeout error?
"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
