CODEWITHSUNDEEP
sql-servermongodbmigrationasp.net-4.0
saarthak
saarthak

Reputation: 41

SQL Server 2008 R2 to MongoDB - is it safe to migrate?

We are running a .Net 4.0 ASP.Net application with SQL Server 2008 R2. I often face database related issues and have to frequently look into possibilities of optimising my SQL code (procedures, triggers, jobs etc). I recently, came to know about MongoDB and read a few articles about it.

Invariably, all articles show that Mongo is much much faster than SQL Server 2008 R2 in CRUD operations.

I also read that sourceforge has migrated from MySQL to MongoDB and claim to be capable of handling 100x more data.

So, impressed with these stats, I went to the mongoDB site, I followed their short demo. It was nice. But I couldn't find much information about other database related aspects like SProcs, triggers, jobs, cursors, Key, indexes etc.

What is my main concern is that is MongoDB evolved enough that I can think of migrating from SQL Server 2008 R2. Also, things like Keys, Indexex, SProcs, triggers, SQL jobs etc do they exist in MongoDB as well? How good is their .Net integration API?

Does anybody have any idea about it?

Thanking in anticipation

Upvotes: 3

Views: 1511

Answers (1)

marc_s
marc_s

Reputation: 754518

What kind of issues do you face with SQL Server 2008 R2??

One option might be to figure those out and fix them. If you optimize your stored procs, if you redesign your table and indices to be more efficient, that might be more than enough to keep your app up and running very well.

I don't know MongoDB that well - but the basic approach is very different - instead of rows and columns and relations, you have "documents". As far as I know, MongoDB does not have any construct similar to stored procedures or triggers - all that would have to be handled in your application.

So it really depends on what kind of app you have - something like an accounting application is probably better off in SQL Server 2008 R2, while something else might be more suitable for MongoDB.

I don't think switching to MongoDB is a "quick fix" just for any kind of performance problems...

Also check out this other SO post on the very same topic:

Reasons for and against moving from SQL server to MongoDB

Upvotes: 4

Related Questions