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.
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.
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?
You can check out the site at http://nmhis.unm.edu
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
Comments: ** Comment from web user: csebranek **
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.
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?
You can check out the site at http://nmhis.unm.edu
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
Comments: ** Comment from web user: csebranek **
Hi-- was this issue ever resolved? I'm having the same problem with our web service, too. How do I go about clustering the result together?
Thanks,
Chad
