Wednesday, December 25, 2013

Dynamic pivot tables (transform rows to columns)

Dynamic pivot tables (transform rows to columns)

 

in MySql there is no function of automatically table transformation. Surely we can use some program (tool), which is able to connect to MySql and execute data transformation. But in this case we want to do it manually, and we have one variant – to write a query which will execute the data rotation in the table

 

http://buysql.com/mysql/14-how-to-automate-pivot-tables.html

  http://stackoverflow.com/questions/10925445/mysql-select-dynamic-row-values-as-column-names-another-column-as-value

 

http://stackoverflow.com/questions/10986031/sql-dynamic-view-with-column-names-based-on-column-values-in-source-table?rq=1

Sunday, November 10, 2013

Transform a CDE Dasboard to be loaded in a CDF only Pentaho Server



http://rhaces.blogspot.in/2011/08/transform-cde-dasboard-to-be-loaded-in.html


http://interestingittips.wordpress.com/2012/01/12/bullet-graph-dashboard/


Thursday, October 24, 2013

max_allowed_packet error in mysql



Caused by: java.sql.BatchUpdateException: Packet for query is too large (1434172 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.


The max_allowed_packet variable can be set globally by running a query.
However, if you do not change it in the my.ini file (as dragon112 suggested), the value will reset when the server restarts, even if you set it globally.

To change the setting for everyone until the server restarts:
SET GLOBAL max_allowed_packet=1073741824;

Wednesday, October 23, 2013

CDE CCC charts

http://redmine.webdetails.org/projects/ccc/wiki/FAQ_Main_Changes_New_Features_CCC_v2

http://forums.pentaho.com/showthread.php?150582-Bar-chart-colors-dynamically-changed-based-on-data-value-Along-with-JavaScript-vars/page2

http://www.webdetails.pt/ctools/charts/jsdoc/symbols/pvc.options.charts.Chart.html#clickAction



Property       Type Description
scene pvc.visual.Scene A scene is a node in a rendering hierarchy. Rendering generally follows the shape of a scene hierarchy. Each scene contains participating datums and vars (see below).

 function a(scene){
 this.scene.vars.series.value                  //for retrieving series value
this.scene.vars.category.value               //for retrieving category value
}

Tuesday, October 22, 2013

Creating Dashboards with CDE

Creating Dashboards with CDE

  http://helicaltech.com/blogs/tag/pentaho-cde/

Date Input Controls/ Components in Pentaho CDE with a working example

          http://helicaltech.com/blogs/175/

http://type-exit.org/adventures-with-open-source-bi/2011/06/creating-dashboards-with-cde/ 

 

http://pentahohispano.blogspot.in/2011/07/como-hacer-cuadros-de-mando-v.html

 

http://translate.google.co.in/translate?hl=en&sl=es&u=http://pentahohispano.blogspot.com/2011/07/como-hacer-cuadros-de-mando-v.html&prev=/search%3Fq%3Dcde%2Bdashboards.firechange%26client%3Dfirefox-a%26rls%3Dorg.mozilla:en-US:official%26biw%3D1024%26bih%3D674

 

http://mbostock.github.io/protovis/


http://www.osbi.fr/vos-tableaux-de-bords-pentaho-avec-les-ctools/

Dynamic coloring of PRD Charts

http://type-exit.org/adventures-with-open-source-bi/2011/05/dynamic-coloring-of-prd-charts/


Sunday, August 25, 2013

Pentaho Report Integration in iframe



http://pentahoreportingandintegration.blogspot.in/2013/04/pentaho-report-integration-in-iframe.html

http://jira.pentaho.com/browse/BISERVER-8090

http://jira.pentaho.com/browse/BISERVER-4067

forum issue

Thursday, August 22, 2013

session-region-list.xaction - ERROR-007 during login


If you get the following error message in the console:

14:02:38,763 ERROR [SolutionEngine] 89a06230-0b76-11df-b4e9-ab19d7ccef2f:SOLUTION-ENGINE:session-region-list.xaction: SolutionEngine.ERROR_0007 - Action sequence execution failed
14:03:34,760 ERROR [SolutionEngine] ab02fbe1-0b76-11df-b4e9-ab19d7ccef2f:SOLUTION-ENGINE:global-department-list.xaction: SolutionEngine.ERROR_0007 - Action sequence execution failed


Solution :-

Check inside this file : /pentaho-solutions/system/sessionStartupActions.xml and comment the bean that uses this deleted action. 

Monday, August 12, 2013

How to Create a Pentaho Report Using the REST Client

http://woodlouse.blogspot.fr/2013/02/how-to-create-pentaho-report-using-rest.html

http://woodlouse.blogspot.in/2013_02_01_archive.html

Thursday, July 18, 2013

/reporting/reportviewer/cdf/cdf-module.js not found in plugin reporting



ERROR [GenericServlet] GenericServlet.ERROR_0004 - Resource /reporting/reportviewer/cdf/cdf-module.js not found in plugin reporting


copy solutions/system/pentaho-cdf/js/cdf-module.js solutions/system/reporting/reportviewer/cdf/

http://forums.pentaho.com/showthread.php?138924-Report-does-not-appear-in-server

Wednesday, July 17, 2013

upgrading Pentaho community tools CGG community graphics generator



After upgrading CGG community graphics generator from marketplace on Pentaho BI 4.8, Stop BI server and Please remember to replace all batik, xml-apis and xmlgraphics jars on WEB-INF/lib with ones on system/cgg/lib


Pentaho BI 4.8 error Upgrade to Apache Xerces



Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support.

org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource [com/auchan/core/context/applicationContext.xml]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Unable to validate using XSD: Your JAXP provider [org.apache.crimson.jaxp.DocumentBuilderFactoryImpl@121f1d] does not support XML Schema. Are you running on Java 1.4 or below with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support.
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unable to validate using XSD: Your JAXP provider [org.apache.crimson.jaxp.DocumentBuilderFactoryImpl@121f1d] does not support XML Schema. Are you running on Java 1.4 or below with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support.
 Solution :-
Just add the following as JVM parameters:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl

http://marlowa.blogspot.in/2009/08/how-to-solve-weird-jaxbxerces-spring.html
http://forum.springsource.org/showthread.php?21140-Using-the-container-in-a-standalone-app-with-XML-definitions

Monday, July 8, 2013

error on cdc plugin 13.02.07 at pentaho startup

Error :-

09:25:10,924 ERROR [Logger] misc-class org.pentaho.platform.plugin.services.pluginmgr.DefaultPluginManager: PluginManager.ERROR_0011 - Failed to register plugin cdc
org.pentaho.platform.api.engine.PlatformPluginRegistrationException: PluginManager.ERROR_0017 - Could not load lifecycle listener [pt.webdetails.cdc.CdcLifeCycleListener] for plugin cdc
at org.pentaho.platform.plugin.services.pluginmgr.DefaultPluginManager.bootStrapPlugin(DefaultPluginManager.java:163)
at org.pentaho.platform.plugin.services.pluginmgr.DefaultPluginManager.registerPlugin(DefaultPluginManager.java:197)
at org.pentaho.platform.plugin.services.pluginmgr.DefaultPluginManager.reload(DefaultPluginManager.java:128)


Solution :-

Copy jar files located at biserver-ce\pentaho-solutions\system\cdc\pentaho-lib to biserver-ce\tomcat\webapps\pentaho\WEB-INF\lib

Issue will be resolve.

http://forums.pentaho.com/showthread.php?137442-error-on-cdc-plugin-13-02-07-at-pentaho-startup

Changing the Java VM Memory Limits in Pentaho BI

You can find docs biserver-ce\tomcat\webapps\pentaho\docs\



Changing the Java VM Memory Limits

If you are running out of memory even though your server has a lot of RAM, you probably need to increase the resources allocated to the JRE instance that runs the Pentaho software you're trying to improve performance on. Adjusting the memory limit is an easy configuration change to make, but the instructions differ depending on the client tool or Web application server you're using. Refer only to the sections below that apply to your situation.
Note: If you are running multiple Pentaho programs concurrently, the sum of their JVM maximum memory limits must not exceed the available RAM minus system overhead.

Increasing Memory Limits on Microsoft Windows with a Graphical Installation
By default, Tomcat has a relatively low memory allotment. This can cause out-of-memory errors in the BA Server fromtime to time. The below instructions will explain how to increase the memory so you don't get this error. Instructions are also included for renaming the tomcat6 executable file so that BA Server starts automatically.
These instructions are for those who installed Pentaho Business Analytics graphically (as opposed to manually) and are Windows users.
1. Go to the Windows Search Box and enter C:\Program Files\pentaho\server\biserver-ee\tomcat\bin\shutdown.bat to shutdown the Pentaho BA Server.
2. Type services.msc into the Windows Search Box.
3. Find the Pentaho Server name (Pentaho BA Server or Pentaho BI Server) and open it so you can find the servicename. The service name should appear at the top of the first tab (General). It will be pentahobaserver.
4. Go into the bin file (C:\Program Files\pentaho\server\biserver-ee\tomcat\bin\) and rename the tomcat6w.exe file to match the service name (pentahobaserver or pentahobiserver). This will ensure that the server starts with the software.
5. After you have renamed the file, open it by double-clicking on it. This will not open the file, it will allow you to edit it. The Properties Window will open.
6. Select the Java tab.
7. Set the memory setting to a minimum of 4096 M and a maximum of 6144 M, depending on your computer's memory capabilities.
8. Start the Tomcat server or service.

Your Tomcat server now has increased minimum and maximum memory limits. You can adjust the JvmMx number, which is a parameter that specifies the maximum limit, to a higher number if you prefer. However, if the java virtual machine refuses to start with increased limits, then you will have to add more RAM to your system, stop some memory intensive services, or reduce the maximum memory limit to a lower number. This problem occurs when there is not enough contiguous memory available to assign to the JVM.

Increasing Memory Limits on Linux with a Graphical Install
By default, Tomcat has a relatively low memory allotment. This can cause out-of-memory errors in the BA Server fromtime to time. To avoid errors, increase the memory allocation so you can start the BA Server automatically.
These instructions apply if you installed Pentaho Business Analytics using the graphical installer as opposed
to manual installer and are Linux users.
1. Go to /pentaho/server/biserver-ee/tomcat/bin/ directory and run the ./shutdown.sh command to stop the appropriate server.
2. Change the directory to biserver-ee/tomcat/scripts.
3. Edit the ctl.sh file.
4. Locate the line under start tomcat, which looks like this: export JAVA OPTS="-
Dpentaho.installed.licenses.file=/opt/pentaho/.insalledLicenses.xml -Xms128m
Xmx768m -XX-MaxPermSize=256m -Dsun.rmi.dyc.client.gcInterval=3600000 -
Dsun.rmi.dgc.server.gcInterval=3600000"
5. Set the memory to a minimum of 4096 M and a maximum of 6144 M, depending on your computer's memory capabilities.
6. Start the Tomcat server or service.
Your Tomcat server now has increased minimum and maximum memory limits. You can adjust the JvmMx parameter to specify a higher maximum limit if you prefer. However, if the Java virtual machine refuses to start with increased limits, then you will have to add more RAM to your system, stop some memory-intensive services, or reduce the maximum memory limit to a lower number. This problem occurs when there is not enough contiguous memory available to assign to the JVM, and appears to happen more often on Microsoft Windows at lower thresholds than on other operating
systems.
Increasing Memory Limits with an Archive or Manual Deployment
By default, Tomcat has a relatively low memory allotment. This can cause out-of-memory errors in the BA Server fromtime to time. To increase the memory limit, follow the below process.
1. Stop the Tomcat server or service.
2. Because you are modifying your own Tomcat instance and have performed a manual deployment of the BA Server WAR, edit the ~/.bashrc for the user account that starts the Tomcat service, or whatever configuration file or dialogue that contains global system variables on your BA Server machine. Set or modify the CATALINA_OPTS system variable to include reasonable minimum and maximum memory settings using the -Xms and -Xmx options.
export CATALINA_OPTS="-Xms4096m -Xmx6144m"
3. If you are using a Pentaho-supplied Tomcat instance provided in BA Server archive packages, edit the startpentaho script (.bat for Windows, and .sh for Linux), and modify the CATALINA_OPTS environment variable, adjusting the values of Xms and Xmx in the same manner as the previous step.
export CATALINA_OPTS="-XMs4096m -Xmx6144m -XX:MaxPermSize=6144m -
Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000"
4. If you are modifying a Windows service for Tomcat, you must use the tomcat6.exe command to reconfigure the service parameters within a command line window. You can access Windows Services by going to the Windows
Start Menu and typing services in the Search Programs and Files box. See the below example.
Windows (this only applies to a Windows service for Tomcat)
tomcat6 //US//Tomcat6 --JvmMs=4096m --JvmMx=6144m
5. Start the Tomcat server or service.
Your Tomcat server now has increased minimum and maximum memory limits. You can adjust the JvmMx number
(this parameter specifies the maximum limit) to a higher number if you prefer. However, if the Java virtual machine refuses to start with increased limits, then you will have to add more RAM to your system, stop some memory-intensive services, or reduce the maximum memory limit to a lower number. This problem occurs when there is not enough contiguous memory available to assign to the JVM, and appears to happen on Windows at lower thresholds than on other operating systems.

Increasing the Memory Limit in Aggregation Designer
Pentaho Aggregation Designer's startup script uses the default memory settings for your Java environment, which may be insufficient for your work. If you're experiencing an OutOfMemory exception, you must increase the amount of heap space available to Aggregation Designer by changing the Java options that set memory allocation. Follow the directions below to accomplish this.
Note: In the examples below, the memory size notations are m for megabytes and g for gigabytes. You can use whichever is most appropriate for your situation.
1. Exit Aggregation Designer if it is currently running.
2. Edit the startaggregationdesigner script and modify your Java command to include an -Xmx line that specifies a large upper memory limit.

Linux/Solaris shell script:
"$_PENTAHO_JAVA" $LICENSEPARAMETER -Xmx2g -jar "$DIR/lib/launcher-1.0.0.jar"
Windows batch file:
"%_PENTAHO_JAVA%" %LICENSEPARAMETER% -Xmx2g -jar "%~dp0lib\launcher-1.0.0.jar"
3. Start Aggregation Designer and ensure that there are no memory-related exceptions.
The Java virtual machine instance that Aggregation Designer uses now has access to more heap space, which should solve OutOfMemory exceptions and increase performance.

Increasing the Memory Limit in PDI
Pentaho Data Integration's startup script uses the default memory settings for your Java environment, which may be insufficient for your work. If you're experiencing an OutOfMemory exception, you must increase the amount of heap space available to PDI by changing the Java options that set memory allocation. Follow the directions below to accomplish this.
Note: In the examples below, the memory size notations are m for megabytes and g for gigabytes. You can use whichever is most appropriate for your situation.
1. Exit Spoon if it is currently running.
2. Edit your Spoon startup script and modify the -Xmx value in the OPT variable so that it specifies a large upper
memory limit.
Linux/Solaris shell script:
OPT="$OPT -Xmx2g -Xms256m -XX:MaxPermSize=128m -Djava.library.path=$LIBPATH -
DKETTLE_HOME=$KETTLE_HOME -DKETTLE_REPOSITORY=$KETTLE_REPOSITORY -DKETTLE_USER=
$KETTLE_USER -DKETTLE_PASSWORD=$KETTLE_PASSWORD -DKETTLE_PLUGIN_PACKAGES=
$KETTLE_PLUGIN_PACKAGES -DKETTLE_LOG_SIZE_LIMIT=$KETTLE_LOG_SIZE_LIMIT"
Windows batch file:
set OPT="-Xmx2g" "-XX:MaxPermSize=256m" "-Djava.library.path=%LIBSPATH%"
"-DKETTLE_HOME=%KETTLE_HOME%" "-DKETTLE_REPOSITORY=%KETTLE_REPOSITORY%"
"-DKETTLE_USER=%KETTLE_USER%" "-DKETTLE_PASSWORD=%KETTLE_PASSWORD%" "-
DKETTLE_PLUGIN_PACKAGES=%KETTLE_PLUGIN_PACKAGES%" "-DKETTLE_LOG_SIZE_LIMIT=
%KETTLE_LOG_SIZE_LIMIT%"
3. Start Spoon and ensure that there are no memory-related exceptions.
The Java virtual machine instance that PDI uses now has access to more heap space, which should solve OutOfMemory exceptions and increase performance.

Increasing the Memory Limit in Report Designer
Pentaho Report Designer's startup script uses the default memory settings for your Java environment, which may be insufficient for your work. If you're experiencing an OutOfMemory exception, you must increase the amount of heap space available to Report Designer by changing the Java options that set memory allocation. Follow the directions below to accomplish this.
Note: In the examples below, the memory size notations are m for megabytes and g for gigabytes. You can use whichever is most appropriate for your situation.
1. Exit Report Designer if it is currently running.
2. Edit the report-designer script and modify the value of -Xmx to allocate more memory to Report Designer's JVM instance.

Linux/Solaris shell script:
"$_PENTAHO_JAVA" "-Dpentaho.installed.licenses.file=$PENTAHO_INSTALLED_LICENSE_PATH"
-XX:MaxPermSize=256m -Xmx2g -jar "$DIR/launcher.jar" $@
Windows batch file:
set OPT="-XX:MaxPermSize=256m" "-Xmx2g"
3. Start Report Designer and ensure that there are no memory-related exceptions.
The Java virtual machine instance that Report Designer uses now has access to more heap space, which should solve
OutOfMemory exceptions and increase performance.
Increasing the Memory Limit in Weka
Weka uses the memory settings passed to it from the Java command line or the script that invokes it. If you're experiencing an OutOfMemory exception, you must increase the amount of heap space available to Weka by changing the Java options that set memory allocation. Follow the directions below to accomplish this.
Note: In the examples below, the memory size notations are m for megabytes and g for gigabytes. You can use whichever is most appropriate for your situation.
1. Exit Weka if it is currently running.
2. If you are running Weka standalone from the command line, modify your Java command to include an -Xmx line that specifies a large upper memory limit.
java -Xmx2g weka.jar
3. If you are running Weka as part of a script, change your Java invocation so that it includes the above -Xmx setting.
4. Start Weka and ensure that there are no memory-related exceptions.
The Java virtual machine instance that Weka uses now has access to more heap space, which should solve OutOfMemory exceptions and increase performance.

Thursday, June 27, 2013

TIPS : How to Get Help from Pentaho forum

http://forums.pentaho.com/showthread.php?26490-Getting-Help 

Understanding that those of us at Pentaho are volunteering our time to help users get started with the platform, if you reach a point where reading the provided documentation and looking through the forums can't solve your problem, here's a quick best-practices way to get the most out of the forum.

Start Here: http://community.pentaho.org/faq/forum_assistance.php



  • Post information about your environment, operating system, whether you're using the Preconfigured Install (PCI), what application server you're running in, what jdbc driver you're using, what version of the platform you have, what version of the client tool you're running, etc. If you're using Tomcat for example, we need to know the exact version of Tomcat you're running. We also need to know the JDK version. Without all this information, we just have to turn around and ask you what you're running. This wastes our time and yours.
  • Make sure that your Subject line has useful information. Posting a subject like "Please Help Me" wastes everyone's time.
  • Please post everything you've tried - that tells us that you're trying to solve the problem yourself. This includes information like "I googled for x and didn't get anything helpful", "I found this post in the forums which seemed close to my problem" and "The advanced install guide doesn't address x".
  • If, after searching the forums and googling for your problem, you still come up short and are posting for help in the forums, you need to provide some files to us so that we have some hope of resolving your issue. These files should be placed in a .zip file:

For Issues with JBoss
  1. Your pentaho.xml
  2. The web.xml
  3. The jboss-web.xml (for JBoss issues)
  4. The related xxxx-ds.xml involved
  5. Action sequence(s) that has the problem
  6. Any resources the action sequence(s) needs - like report.xml files
  7. The server log file (server.log) that shows the problem for server issues, or stack traces from the client utility if applicable.

For issues with Tomcat
  1. Your pentaho.xml
  2. The web.xml
  3. The tomcat server.xml
  4. Action sequence(s) that has the problem
  5. Any resources the action sequence(s) needs - like report.xml files
  6. The server log files that show the problem for server issues, or stack traces from the client utility if applicable.

Field ‘PRIORITY’ doesn’t have a default value BI 4.8.0

ERROR [org.quartz.core.ErrorLogger] An error occured while scanning for the next trigger to fire.org.quartz.JobPersistenceException: Couldn’t acquire next trigger: Field ‘PRIORITY’ doesn’t have a default value
[See nested exception: java.sql.SQLException: Field 'PRIORITY' doesn't have a default value]


Solution :-


Simply to set the DEFAULT of the column to 0 in following tables

QRTZ_TRIGGERS

                 COLUMN         PRIORITY          set default value 0

QRTZ_FIRED_TRIGGERS

                 COLUMN         PRIORITY          set default value 0

solu'n for error connecting quartz in pentaho BI server 4.8.0



In case you get this error
Failed to obtain DB connection from data source ‘myDS’: java.sql.SQLException: Could not retrieve datasource via JNDI url ‘java:comp/env/jdbc/Quartz’

Solution :- 

delete the following file
toncat/conf/Catalina/localhost/pentaho.xml
and try again. :)

Tuesday, April 9, 2013

MySQL Field Types



Mysql supports a number of column types, which may be grouped into three categories: numeric types, date and time types, and string (character) types. This section first gives an overview of the types available. Please refer to the MySQL manuals for more details. 

Type
Use for
Size
TINYINT
A very small integer
The signed range is 128 to 127. The unsigned range is 0 to 255.
SMALLINT
A small integer
The signed range is 32768 to 32767. The unsigned range is 0 to 65535
MEDIUMINT
A medium-size integer
The signed range is 8388608 to 8388607. The unsigned range is 0 to 16777215
INT or INTEGER
A normal-size integer
The signed range is 2147483648 to 2147483647. The unsigned range is 0 to 4294967295
BIGINT
A large integer
The signed range is 9223372036854775808 to 9223372036854775807. The unsigned range is 0 to 18446744073709551615
FLOAT
A small (single-precision) floating-point number. Cannot be unsigned
Ranges are 3.402823466E+38 to 1.175494351E-38, 0 and 1.175494351E-38 to 3.402823466E+38. If the number of Decimals is not set or <= 24 it is a single-precision floating point number
DOUBLE,
DOUBLE PRECISION,
REAL
A normal-size (double-precision) floating-point number. Cannot be unsigned
Ranges are -1.7976931348623157E+308 to -2.2250738585072014E-308, 0 and 2.2250738585072014E-308 to 1.7976931348623157E+308. If the number of Decimals is not set or 25 <= Decimals <= 53 stands for a double-precision floating point number
DECIMAL,
NUMERIC
An unpacked floating-point number. Cannot be unsigned
Behaves like a CHAR column: unpacked means the number is stored as a string, using one character for each digit of the value. The decimal point, and, for negative numbers, the - sign is not counted in Length. If Decimals is 0, values will have no decimal point or fractional part. The maximum range of DECIMAL values is the same as for DOUBLE, but the actual range for a given DECIMAL column may be constrained by the choice of Length and Decimals. If Decimals is left out its set to 0. If Length is left out its set to 10. Note that in MySQL 3.22 the Length includes the sign and the decimal point
DATE
A date
The supported range is 1000-01-01 to 9999-12-31. MySQL displays DATE values in YYYY-MM-DD format
DATETIME
A date and time combination
The supported range is 1000-01-01 00:00:00 to 9999-12-31 23:59:59. MySQL displays DATETIME values in YYYY-MM-DD HH:MM:SS format
TIMESTAMP
A timestamp
The range is 1970-01-01 00:00:00 to sometime in the year 2037. MySQL displays TIMESTAMP values in YYYYMMDDHHMMSS, YYMMDDHHMMSS, YYYYMMDD or YYMMDD format, depending on whether M is 14 (or missing), 12, 8 or 6, but allows you to assign values to TIMESTAMP columns using either strings or numbers. A TIMESTAMP column is useful for recording the date and time of an INSERT or UPDATE operation because it is automatically set to the date and time of the most recent operation if you dont give it a value yourself
TIME
A time
The range is -838:59:59 to 838:59:59. MySQL displays TIME values in HH:MM:SS format, but allows you to assign values to TIME columns using either strings or numbers
YEAR
A year in 2- or 4- digit formats (default is 4-digit)
The allowable values are 1901 to 2155, and 0000 in the 4 year format and 1970-2069 if you use the 2 digit format (70-69). MySQL displays YEAR values in YYYY format, but allows you to assign values to YEAR columns using either strings or numbers. (The YEAR type is new in MySQL 3.22.)
CHAR
A fixed-length string that is always right-padded with spaces to the specified length when stored
The range of Length is 1 to 255 characters. Trailing spaces are removed when the value is retrieved. CHAR values are sorted and compared in case-insensitive fashion according to the default character set unless the BINARY keyword is given
VARCHAR
A variable-length string. Note: Trailing spaces are removed when the value is stored (this differs from the ANSI SQL specification)
The range of Length is 1 to 255 characters. VARCHAR values are sorted and compared in case-insensitive fashion unless the BINARY keyword is given
TINYBLOB,
TINYTEXT

A BLOB or TEXT column with a maximum length of 255 (2^8 - 1) characters
BLOB,
TEXT

A BLOB or TEXT column with a maximum length of 65535 (2^16 - 1) characters
MEDIUMBLOB,
MEDIUMTEXT

A BLOB or TEXT column with a maximum length of 16777215 (2^24 - 1) characters
LONGBLOB,
LONGTEXT

A BLOB or TEXT column with a maximum length of 4294967295 (2^32 - 1) characters
ENUM
An enumeration
A string object that can have only one value, chosen from the list of values value1, value2, ..., or NULL. An ENUM can have a maximum of 65535 distinct values.
SET
A set
A string object that can have zero or more values, each of which must be chosen from the list of values value1, value2, ... A SET can have a maximum of 64 members

Create MongoDB service in Windows OS

1) Open Command Prompt 2) Create directory for Database and Logs                    mkdir c:\data\db                     mkdir c:\...