ODM Timeout. . .

nmhydro[CodePlex]
I'm curious if there is an estimated functional size limit on the ODM in SQL Server. My db is currently at 40+ million measurements and ~12GB in size.
nbsp
At the moment all queries timeout, even with SQL timeout set to 0. A second smaller db, ~1.2GB, on the same server works fine so we are pretty sure its not a server issue. Our database guru, loosely associated with the project, suggested additional indexing.

nbsp
Has anyone run into this timeout problem on large databases and if so, what is the solution? Are there any tested ODM indexing scenarios that we could implement without reinventing the wheel?
nbsp
You can check out the site at http://nmhis.unm.edu
nbsp
Excuse any runtime errors you find, I'm still trying to work out glitches in the assorted web.config files. The Rio Grande ET project times out, the ET Wells run fine and actually work pretty fast.

Thanks,
Stephen B

Start by examining the SQL Server ODM database and comparing the failing Rio Grande ET query with the working ET Wells query on the smaller database. Done means identifying whether the timeout is caused by database size or indexing and documenting a tested indexing or configuration approach that prevents the timeout.

Written by the indexing model from the issue text.