title: Pros and Cons of using MongoDB instead of MS SQL Server
body: <p>I am new to NoSQL world and thinking of replacing my MS Sql Server database to MongoDB. My application (written in .Net C#) interacts with IP Cameras and records meta data for each image coming from Camera, into MS SQL Database. On average, i am inserting about 86400 records per day for each camera and in current database schema I have created separate table for separate Camera images, e.g. Camera_1_Images, Camera_2_Images ... Camera_N_Images. Single image record consists of simple metadata info. like AutoId, FilePath, CreationDate. To add more details to this, my application initiates separate process (.exe) for each camera and each process inserts 1 record per second in relative table in database.</p>
  
  <p>I need suggestions from (MongoDB) experts on following concerns:</p>
  
  <ol>
  <li><p>to tell if MongoDB is good for holding such data, which eventually will be queried against time ranges (e.g. retrieve all images of a particular camera between a specified hour)? Any suggestions about Document Based schema design for my case? </p></li>
  <li><p>What should be the specs of server (CPU, RAM, Disk)? any suggestion?</p></li>
  <li><p>Should i consider Sharding/Replication for this scenario (while considering the performance in writing to synch replica sets)?</p></li>
  <li><p>Are there any benefits of using multiple databases on same machine, so that one database will hold images of current day for all cameras, and the second one will be used to archive previous day images? I am thinking on this with respect to splitting reads and writes on separate databases. Because all read requests might be served by second database and writes to first one. Will it benefit or not? If yes then any idea to ensure that both databases are synced always.</p></li>
  </ol>
  
  <p>Any other suggestions are welcomed please.</p>