Tag Info

New answers tagged

2

No its not necessary to uninstall. I don't really like yum or apt for installing mongoDB. I suggest you to download the binaries from https://www.mongodb.org/dl/linux/x86_64 , linux/mongodb-linux-x86_64-ubuntu1404-3.1.0.tgz (or the v12) and use it to start mongodb.


0

I have addressed something like this already Oct 17, 2014 : Any known issues upgrading from MySQL 5.1.73 to 5.6.21? Jan 31, 2014 : Upgrading mysql myisam 5.1 to mysql 5.6: force innodb on restore? Apr 11, 2013 : MySQL upgrade 5.0.88 to latest Feb 08, 2012 : will replication from 5.5.20 to 5.0.XX server work? Jul 26, 2011 : Restoring an old backup to latest ...


0

If you follow the upgrade process it is designed to avoid downtime -- for example using rs.stepDown() to gracefully step down the replica set primaries rather than abruptly triggering an election by shutting down the server. Of course there is no guarantee if something doesn't go to plan, but you should test your upgrade in a QA/staging environment before ...


0

I've used TDE in production many times and it in no way affects Windows/SQL Server patching unless there's some horrific bug or something of the sort; which has not yet happened. TDE simply uses the Windows DPAPIs to generate a cert in Master that then is used to make other certs which can encrypt/decrypt the remaining DB data at rest. Heads up though, ...


0

TDE only encrypts the data at rest. If they have the access to connect to the server and query the database then they can get to the data. But I don't think the person running the patch (CU or Service Pack) needs permissions to the database proper, just permissions on the server. The only way to separate the job functions as you seem to want would be to ...


5

From Microsoft BOL 'Supported Version and Edition Upgrades' SQL Server 2014 supports upgrade from the following versions of SQL Server: • SQL Server 2005 SP4 or later • SQL Server 2008 SP3 or later • SQL Server 2008 R2 SP2 or later • SQL Server 2012 SP1 or later So, as you have 'later' than 2012 SP1, then answer is yes. The actual 'Upgrades ...


1

The normal rules of replica set elections apply. If your shard is backed by a 3-node replica set, then you can have any single node down while still being able to maintain a primary. A strict majority of nodes must be available, so 2/3 in the 3-node example. If the data-bearing server you are planning to restart happens to be a replica set primary, I would ...


2

As part of the MongoDB 3.0 upgrade it is strongly recommended that you upgrade to the SCRAM-SHA-1 authentication scheme. New users will have their credentials created in this format by default; mixed authentication schemas will likely lead to confusion. You will need to upgrade your client driver & admin tools (if you're using a GUI) in order to use the ...


1

Doing this C:> mysqldump -uroot -p abc > abc.sql does not include the two lines you mentioned. On the Prod Server, do this C:> mysqldump -uroot -p --databases abc > abc.sql Using --databases abc makes mysqldump write those two lines On the Staging Server, do this C:> mysql -uroot -p < abc.sql Don't specify abc upon reload. Those ...



Top 50 recent answers are included