ASP-DB Pro. MS SQL Server 2000. OK... I need to have a page go straight to a filter page. I have dbStartup set to filter. When I try to go to the page it hangs for a while, and then times out. Running SQL Server Profiler, I see that ASP-DB has issued the following SQL: Select count(*) from MyTable. If I am going straight to a filter why is it doing a count of all the records? The table contains more than 30 million records, but once the users filter on what they are looking for, the result set will be less than 100 records. My timeout is set to five minutes. If I set it to qo minutes, it might finish before it times out, but it doesn't make sense to scan the whole 30 million records, when the actual data we will filter on will only be ~100 rows. Plus, users will not be happy about having to wait 10 minutes just to bring up a filter screen. Am I doing something wrong?