Analytics - This is the database you will be concerned with when constructing queries for analytic purposes. It contains records of who (what user) did what action (edited, viewed, liked etc.) what content (document, discussion. blog post, etc.). It is in a raw format, so you will need to connect it to a BI tool such as SAP Business Objects or QlikView to query the data and generate reports.
System - Contains information related to the general Jive system and is not super useful for analytic purposes outside of filling in some detail level information that is captured in aggregate in the analytics database. You could use it for setting up a local development instance that contains all the data from your production environment.
EAE - Contains information related to the Jive Activity Engine and recommender service.
Awesome this makes sense. Thanks for the reply.
Currently we are running on Jive 5 and migrating to Jive 6, while working with databases for Jive 5&6. I noticed a difference in the tables.
Actually two tables what we are working on are not appeared in Jive 6(i.e., jivecommunitytag and jivetag) those two are related to each other in Jive 5.
I want to know weather these tables are deleted or the features are added to other tables? Can you clarify my doubt and specify the other tables which these features are included(if there)?
Waiting for response.
I'm not familiar with the specific tables you are referencing but they appear to deal with tags in some form, and as far as I know no tagging features have been lost in Jive 6. Are you manually performaing a database upgrade? If so, I would look into using Jive's upgrade process as they have already done the work for you: Upgrading a Database
Alternately, you could compare the Jive 5 schema to the Jive 6 schema and review the relationship of the tables to find what you are looking for, but I would definitely try the automatic upgrade first.
Hope this helps.
Thanks for your help and quick response Lukas.
Looking forward for the automatic upgrade.
I have the same requirement as Jason: "Can we setup an automated process to download nightly backups of the Jive database?"
Can this be done?
ended up writing a job that uses wget to download the file and then restores it.
wget --http-user=<USER_NAME> --http-password=<PASSWORD> "https://cloud.jivesoftware.com/admin/downloadDbFile.jspa?customerInstallationId=xxxxx&dbDownloadTypeCode=SYSTEM_PGDUMP&filename=aaaaaa-`date +%Y%m%d`-0000.dmp" -O bbbbbbbb-`date+%Y%m%d`-0000.dmp