Skip to main content

Introduction to Mongo Database

It's been long time, since the last post. Let's get to know about mongo database. So mongo is one of the front runners in nosql databases. Nosql databases do not adhere to rules and principles to standard relational databases. So coming to Mongo it a document oriented database which is written in C++.
 
Mongo is an open source database. It is simple to install more of a plug and play type.
 
Once you are done with the mongo installation To start the mongo server in our local machine. Execute the command in command terminal
 
C:\MongoDB\bin\mongod.exe --config="C:\MongoDB\mongo.config"
 
To start the client in our local machine execute the following command in the command terminal
 
C:\MongoDB\bin\mongo
 
Upon executing we can see the following screen
 

 
 By default there will be a test database created in our mongo database. So it will be connected to that particular database.
 
We can create our own database by executing the following command
 
 use local_test
 
So a database under name local_test will be created. To see the list of databases created we can use the following command
 
show dbs   But upon executing the following command you will not see the database which is created just now local_test.
 
 
 
 
This is because it is an empty database. We need to insert a document to make it visible.
 
In mongo data can be inserted only in Json format.

To insert the data execute the following command
 
db.firstdocument.insert({"Name":"AAA","ID":"101"})
 
Now if we execute show dbs we can see the local_test database being created.
 
When we inserted firstdocument in local_test, automatically a collection is created under that name.So basically documents are stored in collection. We can insert any number of rows(i.e. documents) in a given collections
 
To display total number of collections in a given database
 
show collections
 
 
system.indexes  is implicitly created upon creating a collection. This stores indexes information of all documents
 
To see data inside the collections
 
db.firstdocument.show()
 


_id is a unique value which is automatically generated while inserting a row. we can override _id
value and pass our own value in the following way
 
 



These are some of the basics queries in mongo in the next article we will see how to update,delete operations on databases and collections
 
Hope this article helps you in understanding basic mongo queries

Comments

Post a Comment

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

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',

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.