{"id":1835,"date":"2011-07-22T14:30:52","date_gmt":"2011-07-22T13:30:52","guid":{"rendered":"http:\/\/www.gamlor.info\/wordpress\/?p=1835"},"modified":"2021-07-03T13:31:35","modified_gmt":"2021-07-03T12:31:35","slug":"ravendb-preventing-database-slaughter","status":"publish","type":"post","link":"https:\/\/www.gamlor.info\/wordpress\/2011\/07\/ravendb-preventing-database-slaughter\/","title":{"rendered":"RavenDB: Preventing Database Slaughter"},"content":{"rendered":"

After we\u2019ve covered the basics<\/a>, documents<\/a> and queries<\/a>, we take a short look at another \u2018feature\u2019 of RavenDB. Have you ever had this issue: You\u2019ve developed nice application which runs fine during development. Then you go to a production system and your application becomes slow or even dies under higher loads. And the database administrator comes angry to your team and asks who\u2019s killing the database. What happened? Well often these issues are related to bad queries and unbound result sets. Let\u2019s see what RavenDB does to prevent these situations.<\/p>\n

No Unbound Result Sets<\/h2>\n

What do most databases do when you run a query like \u2018give me all .NET related blog posts\u2019? Well they try to fulfill that request. What\u2019s the issue with that? Often the result set too is big. When too large result sets hits your application it will choke on it. How do we prevent that? We add limitations to the result set size. However how many times have you forgotten to add that limitation in your application? I think it\u2019s a very common mistake to forget it and get an unbounded result set. Well RavenDB just doesn\u2019t allow unbounded set. Let\u2019s see it in action (btw: The domain classes are here<\/a>, the insert code<\/a> here):
\n