Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2001-11-26 : 09:36:04
|
| Richard writes "Hi,I keep hitting a problem with the ASP & SQL online database that I am building.Basically I have one page that runs a stored procedure and the whole page is run as a transaction.........this is fine if I ask the stored procedure to deal with upto 50000 records, but I am working on a database of 3,500,000, and anything above 50000 gives me an error, well the transaction aborts and the page displays nothing.I have set the the ConnectionTimeout, CommandTimeout and ScriptTimeout variables, but the transaction is still falling over.Do you have any ideas for what I should do? Am I missing a setting on the transaction?" |
|
|
yakoo
Constraint Violating Yak Guru
312 Posts |
Posted - 2001-11-26 : 09:46:53
|
| What is the exact error that you are recieving? |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2001-11-26 : 16:35:58
|
| SQL Server can definitely query a table of 3.5 million rows in less time than a page would timeout. What are you doing with them? I pray that you are not even considering displaying 50,000 rows on a single ASP page. Check your database to make sure it has appropriate indexes. Look into using RS.GetRows or RS.GetString instead of doing a While Not RS.EOF loop.If you need more help, we need more details.-------------------It's a SQL thing... |
 |
|
|
|
|
|