search

CUAHSI / HydroServer

BSD 3-Clause "New" or "Revised" License
8 stars 4 forks source link

ODM Timeout. . . #64

Open xhqiao89 opened 7 years ago

xhqiao89 commented 7 years ago

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

xhqiao89 commented 7 years ago

csebranek[CodePlex]
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

xhqiao89 commented 7 years ago

valentinedwv[CodePlex]
can we get access to it, or an ftp site to get a look at it?

For the wells, Looks like some series have 100k values.

It may need to have some custom indexing, to cluster the result together. You might need to manage the series rather than manage by data value

I'm seeing error with both endpoints (clicking on the WSDL links)