Skip to main content

Check Count, Delete Documents and Drop Collections in MongoDB

Checking the count of documents from collection in MongoDB:

In RDBMS, to check the count from table, we need to use count function. In MongoDB also, we have count() method to get the count from collection.

Syntax:

db.<Collection Name>.count()

Example:

db.FirstCollection.count(). This query will return the count of total number of records.

To get the count of records with specific filter then we need to use find() metho along with count().

Let's say we have records with different Student_Id values in StudentData collection. And we have to find the number of records with Student_Id 201. To do this, we have to pass below query.

db.StudentData.find({"Student_Id":201}).count()


Delete Documents in MongoDB:

In RDBMS, to delete data from table, we need to use DELETE statements.As MongoDB is noSQL database, we have to use remove() method to delete data from collection.

Syntax:

db.<Collection Name>.remove({<data selection criteria>},{<justOne: true or flase>})

to remove() method, we need to pass the query to select the data from collection to delete. Here, another option is there to limit the delete to one record. If you set "justOne" to true then it will delete only one record. This is optional.

Example:

Assume, i have a collection FirstCollection and I have records with Student_Id 201. I need to delete these records from collection.

db.FirstCollection.remove({"Student_ID":201})

The above query will delete all the records with the Student Id 201. In the above query, "{"Student_ID":201}" is data selection criteria to delete from collection.


To remove only one record, then pass true to the key "justOne".

db.FirstCollection.remove({"Student_ID":201},{justOne:true})


Drop collection in MongoDB:

In RDBMS, to delete data from table, we need to use DROP statements.As MongoDB is noSQL database, we have to use drop() method to delete data from collection.

Syntax:

db.<Collection Name>.drop()

This will drop the mentioned collection from the database,

Example:

Assume that you have to delete FirstCollection collection from database. to do this, you have to pass below command:

db.FirstCollection.drop()

drop() method will return "true" if collection dropped successfully. If collection does not exist to drop then drop() method will return "false".

You can see the video in the bellow link:
https://www.youtube.com/watch?v=mV11JykX1T8

Hope this is helpful.

Comments

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Target Load Type - Normal or Bulk in Session Properties

We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.

SCD Type 2 Implementation in Informatica using dynamic lookup

We have already covered how a dynamic look up works the same can be found out from the following link http://dwbuddy.blogspot.com/2014/06/dynamic-look-up-in-informatica.html  So let's see how we can use it in a regular SCD type 2 mapping. The logic used in SCD type 2 is same as discussed in earlier blog i.e.  http://dwbuddy.blogspot.com/2015/01/scd-type-ii-implementation-in.html . The only difference being here is we have used dynamic look up instead of a static one. We go for dynamic look up when there are duplicate entries for a PK value and only the latest record present in the file should be termed as active. Let us consider the following sample data So  for EMP_ID 101 we have two records in the same day flow so the latest record i.e. with salary as 1500 should be termed as Active record. The mapping will look in the following way So in here we have a dynamic lookup couple of expression transformations,a transaction control transformation which is use...