<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MongoDB on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/mongodb/</link><description>Recent content in MongoDB on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Sun, 03 Mar 2013 22:05:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/mongodb/index.xml" rel="self" type="application/rss+xml"/><item><title>MongoDB ASP.NET Session Store Provider v1.1.0</title><link>https://www.adathedev.co.uk/2013/03/mongodb-aspnet-session-store-provider.html</link><pubDate>Sun, 03 Mar 2013 22:05:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2013/03/mongodb-aspnet-session-store-provider.html</guid><description>Since I created the MongoDB ASP.NET Session State Store Provider (v1.0.0), a few things have moved on in the MongoDB C# Driver. I&amp;rsquo;ve pushed a number of changes up to the project on GitHub (which I&amp;rsquo;ve incremented to v1.1.0), so it now uses v1.7.0.4714 of the driver. There is no change to way it is configured in web.config, so if you are using v1.0.0 of my provider it should be painless.</description></item><item><title>The importance of "Working Set"</title><link>https://www.adathedev.co.uk/2011/06/importance-of-working-set.html</link><pubDate>Fri, 24 Jun 2011 20:55:00 +0100</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/06/importance-of-working-set.html</guid><description>One of the things that I see cropping up pretty often is this thing called &amp;ldquo;working set&amp;rdquo;. After recently chipping in on another StackOverflow question on the subject of &amp;ldquo;What does it meant to fit &amp;lsquo;working set&amp;rsquo; in RAM?&amp;rdquo;, I thought it was a good subject for a blog post. This is really just a copy and extension of my input on that question and focused in certain parts on MongoDB, but is also as relevant to other databases.</description></item><item><title>MongoDB ASP.NET Session State Store Provider</title><link>https://www.adathedev.co.uk/2011/05/mongodb-aspnet-session-state-store.html</link><pubDate>Tue, 03 May 2011 21:03:00 +0100</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/05/mongodb-aspnet-session-state-store.html</guid><description>Please note: v1.1.0 of this Sesssion State Provider is now available. See blog post: https://www.adathedev.co.uk/2013/03/mongodb-aspnet-session-store-provider.html
I&amp;rsquo;ve pushed up an initial drop of a custom ASP.NET session state store, backed by MongoDB, to my GitHub repository. After a quick test it seems OK, though could do with a real hammering before being deemed production worthy! So if you want to use it, just make sure you give it a good test through and most importantly, let me know how it goes!</description></item><item><title>MongoDB Journaling Performance - Single Server Durability</title><link>https://www.adathedev.co.uk/2011/03/mongodb-journaling-performance-single.html</link><pubDate>Fri, 18 Mar 2011 10:34:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/03/mongodb-journaling-performance-single.html</guid><description>Note: Relates to v1.8.0 release. v1.8 of MongoDB (production release hot off the press, available from here) brings single server durability to MongoDB via its support for write-ahead journaling. The following summarises the key points from the journaling documentation, administration guide and from my initial playing around.
you have to specify the &amp;ndash;journal switch for mongod in order to enable journaling (was previously &amp;ndash;dur prior to production release) journal files are created within a journal subfolder of your dbpath, up to 1GB each in size in the event of a crash, when mongod restarts it will replay the journal files to recover automatically before the server goes online if mongod shuts down cleanly, the journal files are cleared down.</description></item><item><title>MongoDB 1.8.0 Release Candidate 2 Available</title><link>https://www.adathedev.co.uk/2011/03/mongodb-180-release-candidate-2.html</link><pubDate>Thu, 10 Mar 2011 10:04:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/03/mongodb-180-release-candidate-2.html</guid><description>Fast on the heels of my previous blog post about MongoDB 1.8.0 Release Candidate 1 becoming available, I&amp;rsquo;ve just seen 1.8.0 RC2 is now available which includes a handful of changes (Download | Change Log).
Did I mention, MongoDB is rapidly evolving?!</description></item><item><title>Thoughts on MongoDB from a SQL Server Dev</title><link>https://www.adathedev.co.uk/2011/02/thoughts-on-mongodb-from-sql-server-dev.html</link><pubDate>Fri, 25 Feb 2011 14:20:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/02/thoughts-on-mongodb-from-sql-server-dev.html</guid><description>As someone with a background in SQL Server development dating back to 2000, the whole NoSQL jazz has been something that&amp;rsquo;s been on the radar for a while but never made it under the microscope so to speak. Partly because SQL Server is my comfort zone and there&amp;rsquo;s plenty more to still learn about that; partly because I&amp;rsquo;ve had my career mapped out in my head and NoSQL didn&amp;rsquo;t feature much in that vision; partly because until you have something real-world driving a push into a technology then you tend to have that technology remaining as a distant dot on the radar.</description></item><item><title>MongoDB 1.8.0 Release Candidate is out</title><link>https://www.adathedev.co.uk/2011/02/mongodb-180-release-candidate-is-out.html</link><pubDate>Thu, 24 Feb 2011 09:26:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/02/mongodb-180-release-candidate-is-out.html</guid><description>MongoDB 1.8.0-rc0 is now available, you can download from here and find the release notes here.
The main changes over the current 1.6 production release relate to:
durability, a much talked about topic (!), with support now for write-ahead journaling (docs)
sparse and covered indexes (on my radar to try out)
support for more Map/Reduce functionality (note there are some breaking changes in this area)
The full info on the changes is in the Release Notes document.</description></item><item><title>MongoUK 2011 - Upcoming MongoDB event</title><link>https://www.adathedev.co.uk/2011/02/mongouk-2011-upcoming-mongodb-event.html</link><pubDate>Wed, 23 Feb 2011 15:45:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/02/mongouk-2011-upcoming-mongodb-event.html</guid><description>There&amp;rsquo;s a one day conference on MongoDB coming up, being held at the Skills Matter eXchange in London on Monday 21st March 2011. If you&amp;rsquo;re interested in MongoDB or even just curious as to what it&amp;rsquo;s all about, then it&amp;rsquo;s worth registering for it based on what&amp;rsquo;s on the agenda - it&amp;rsquo;s going to be tough to choose between the different sessions, which include ones on:
schema design storage engine internals indexing and query optimiser scalability map/reduce &amp;amp; geo indexing It will also be a good chance to hear from speakers outside of 10gen such as Thoughtworks, Guardian and Boxed Ice.</description></item><item><title>MongoDB replication - oplogSize</title><link>https://www.adathedev.co.uk/2011/02/mongodb-replication-oplogsize.html</link><pubDate>Mon, 21 Feb 2011 11:10:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/02/mongodb-replication-oplogsize.html</guid><description>Background An oplog is a write operation log that MongoDB uses to store data modifications that need to be replicated out to other nodes in the configured set. This oplog is a capped collection which means it will never grow in size beyond a certain point - once it reaches it&amp;rsquo;s max size, old data drops off the end as new data is added so it keeps cycling round. The size of the oplog basically determines how long a secondary node can be down for and still be able to catch up when it comes back online.</description></item><item><title>MongoDB - Does My Data Look Big In This?</title><link>https://www.adathedev.co.uk/2011/02/mongodb-does-my-data-look-big-in-this.html</link><pubDate>Mon, 07 Feb 2011 10:10:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/02/mongodb-does-my-data-look-big-in-this.html</guid><description>You have an existing relational database containing x amount of data and you decide to migrate that data, for whatever reason, into MongoDB. You may have an pre-conceived belief that as your relational database is x GB in size, that after loading that data into MongoDB your NoSQL database size will be around about x GB too - after all, you&amp;rsquo;re loading exactly the same data from one to the other right?</description></item><item><title>Running MongoDB as a Windows Service</title><link>https://www.adathedev.co.uk/2011/01/running-mongodb-as-windows-service.html</link><pubDate>Tue, 18 Jan 2011 09:58:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/01/running-mongodb-as-windows-service.html</guid><description>Following on from my opening &amp;ldquo;Getting started with MongoDB and .NET&amp;rdquo; post, one of the next logical steps was to get mongodb running as a Windows service.
From a command prompt, in the mongodb bin directory run:
mongod --install --serviceName &amp;#34;MongoDB&amp;#34; --dbpath C:\mongodb\data\db --logpath C:\mongodb\logs\mongolog.txt --logappend Obviously you can tweak the arguments for your environment - I opted to use a different dbpath to the default \data\db
Starting the service is then just a case of running:</description></item><item><title>.NET Admin GUI for MongoDB</title><link>https://www.adathedev.co.uk/2011/01/net-admin-gui-for-mongodb.html</link><pubDate>Mon, 10 Jan 2011 09:04:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/01/net-admin-gui-for-mongodb.html</guid><description>Having just started out fiddling around with MongoDB from .NET, finding a GUI over the top of MongoDB to help me out while I find my feet was one of the first things I looked for. And I&amp;rsquo;ve been using the first tool I found : MongoVUE - there undoubtedly are others out there, but at the moment I&amp;rsquo;ve found no reason to continue searching.
Can it do everything I want it to?</description></item><item><title>Getting Started with MongoDB and .NET</title><link>https://www.adathedev.co.uk/2011/01/getting-started-with-mongodb-and-net.html</link><pubDate>Fri, 07 Jan 2011 21:28:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2011/01/getting-started-with-mongodb-and-net.html</guid><description>Getting up and running with MongoDB using C# is a very simple process. It literally takes a couple of minutes, including the time to download MongoDB itself and the C# drivers - so if you fancy having a play around with it to see what it&amp;rsquo;s all about, there&amp;rsquo;s no barrier stopping you.
Nutshell To quote MongoDB.org:
MongoDB (from &amp;ldquo;humongous&amp;rdquo;) is a scalable, high-performance, open source, document-oriented database.
Check out the MongoDB homepage for a highlight of the key features.</description></item></channel></rss>