Current version Mongo DB GUI tools cannot be connect to MongoDB 2.x in 2021 years.
Dose have some tools can connected? (Windows And Linux).
Or can be installed at server and use web to connecting.
Not working screenshoot List
Studio 3T 2021.10.1
Compass 1.29.6
With MongoDB Compass, sometimes shortened to Compass, you can access most of the features the MongoDB database engine offers through an intuitive visual display. You can glance through databases, collections and individual documents, interactively create queries, manipulate existing documents, and design aggregation pipelines through a dedicated interface.Download here
Finally, I found the "rock mongo" based on PHP 5.
Available to connect mongo 2 last version is 1.1.7
Github source is #iwind/rockmongo
I make that installers cache at: rockmongo-v1.1.7.zip
Related
Apologies if this question is too open-ended.
I have inherited an aging tech stack and am required to upgrade our 200GB MongoDB Community Edition v3.4 installation (hosted on Ubuntu 20) to MongoDB v5 in order to support some new features.
MongoDB advises that to install v5.0, one must be already on MongoDB v4.4:
https://www.mongodb.com/docs/manual/release-notes/5.0-upgrade-standalone/
They say that if you are on a version older than 4.4, then you need to incrementally upgrade to v4.4 before upgrading to v5.
However, if you follow the links in that official upgrade tutorial, you will find that in order to upgrade to any version of MongoDB, they insist on you upgrading version-by-version, successively.
So for me on v3.4 the upgrade path will look like this:
v3.4 -> v3.6 -> v4.0 -> v4.2 -> v4.4 -> v5.0.13
Following these tutorials:
https://www.mongodb.com/docs/manual/release-notes/3.6-upgrade-standalone/
https://www.mongodb.com/docs/manual/release-notes/4.0-upgrade-standalone/
https://www.mongodb.com/docs/manual/release-notes/4.2-upgrade-standalone/
https://www.mongodb.com/docs/manual/release-notes/4.4-upgrade-standalone/
https://www.mongodb.com/docs/manual/release-notes/5.0-upgrade-standalone/
I'm not entirely sure why this is necessary, as the tutorials themselves seem to mostly involve copying over newer binaries and then setting a feature compatibility version in the database config.
To test whether this was necessary I did a mongodump of our entire v3.4 database and then installed a standalone MongoDB v5.0.13 on the same server and then mongorestore to the new v5.0.13 database. Everything seems to work fine, mongorestore spent two hours recreating all the indexes as its last step (something various articles told me would not happen using the mongodump/mongorestore method).
I am able to connect Mongo clients to this new v5.0.13 Community instance without issue. All the data is there and I am able to query it just fine.
So my question is, why does MongoDB strongly advise doing the upgrade incrementally, one version at a time when dumping the database and restoring it to a new version of MongoDB seems to work just fine?
The only issues I have currently is having to rewrite some client code which is using an older Mongo Java driver. This is something I am going to have to do regardless of the upgrade method I used.
Our MongoDB instance is Community Edition and is a single, standalone instance (not a replica set) so I don't know if this matters. Perhaps the upgrade process described by MongoDB is for Mongo Cloud or for Enterprise?
I'm just looking for clarification on whether the simpler method I tried is going to cause me issues. Maybe I've missed something I hadn't considered.
I need a MongoDB GUI client to see my mongodb database on my local computer but i cannot find any 32 bit version. Can someone link any client except Navicat 15 for MongoDB
My MongoDB shell version: 3.2.22
I found these Open Source Tools
MongoUI
A Open Source Node Web GUI for Mongo DB.
Nosqlclient
(Formerly Mongoclient), MongoDB Management Tool. Runs with Docker.
Or if you if you also look for paid software you can check out:
humongous
A Secure and Modern Online MongoDB GUI.
Acho
StackOverflow isn't the best place to search for a tool. Maybe you better check out the tools listed on:
Alternativeto.net/Mongodb-Compass
We are integrating Tableau with MongoDB and wants to decide on cost effective way connecting with MongoDB. We used trial version of Simba and that seem to be costing around $3000/year. Are there other options which are cheaper? We are not on enterprise version of MongoDB so BI Connector is not an option.
Apache Drill has a Mongo Storage Plugin which allows Drill to be used as an 'interrogator' for MongoDB. Drill's ODBC driver can provide BI tools (such as Tableau) with access to MongoDB via Drill.
The setup would be something like:
Install Drill
Add the MongoDB Storage Plugin to your Drill installation
Verify access via the Drill server and using Drill's ODBC driver to MongoDB
Configure Tableau to use Drill's ODBC driver
More details in the docs:
Drill's MongoDB Plugin
Using Drill with BI Tools
Tableau Examples
This solution is free (or has no licensing costs, at any rate) but it is somewhat bespoke and cobbled together. My own experience is that ...
Installing Drill is a no brainer
Installing the MongoDB Storage Plugin is a no brainer
Drill's MongoDB Storage Plugin isn't very widely used (or at least it isn't under active development) so you'll likely find the driver works fine but you might find issues with the MongoDB query capabilities providing by Drill's plugin. For example LIKE and IN operators are not supported.
I have work a lot with MongoDB 2.6, then I decide to start using MongoDB 3.0.2.
1) When I create an Database using the shell command, the command return true but
the database is not created.
use NewDatabaseName
2) When i try to create some collections, sometime is created and sometime no
I'm using Debian 64Bit, latest version.
Anybody is having this issue?
MongoDB 3.0 is not compatible with all GUI.
For example today MongoVUE do not work at all.
But MongoDB Management Studio sounds like the only one that really work.
Also here some other post related.
mongodb version 3.0.0 client robomongo mongovue
Yes your problem is GUI-related. You can check out different tools on this page:
http://mongodb-tools.com/
I will most probably be using MongoChef from now on.
We are using mongo client tools such as Robomongo and MongoVUE from our windows/mac machines. On the mongodb server side, we decided to try out the new MongoDB 3.0.0rc8 with wiredtiger storage. However, we find that we are not able to list any collections from our client tools and mongo shell. If we login to the server box running mongodb, and then start a mongo shell, then we are able to view the collections.
Is this a known problem - that the existing tools like Robomongo and MongoVUE which have been supporting up to 2.6.X are not yet supporting mongodb 3.0.0?
Is there any mongo client that supports version 3.0.0?
Thanks and Regards,
Archanaa Panda
We encountered the same issue today and started evaluating MongoChef http://3t.io/mongochef which looks promising, both seen to UI, features and support for WiredTiger.
Here is the answer to this question i got on google forums from Will Berkeley-
Yes, those tools need to be updated to support 3.0 on WiredTiger. Many
tools enumerate namespaces by querying system collections that do not
exist when MongoDB is running WiredTiger. The mongo shell function
db.getCollectionNames() and the show command pre-3.0 does this, too -
the reason you can list collections on the 3.0 mongod box is that you
have the 3.0 mongo shell installed there.
-Will
I use NoSQL Manager for MongoDB with Mongo 3.0/WiredTiger
This is fixed as of February 1, 2016 with Robomongo.
Using the right version that is robomongo-0.9.0-rc8 fixed my problem.