A company wiki can be easily configured in under 10 minutes using Mediawiki the open source LAMP software that powers the top 10 website Wikipedia.
A company wiki is an ideal means for a centralized and user contributed documentation system. The following steps show you how to download, configure and get your Mediawiki site operational.
Software Pre-Requisites
[Read more]Even though Data warehouse is picking very rapidly in the last year or so, but few companies who are already made a right mark in the right time could not[...]
The notion "eventual consistency" is bogus to me, in my mind,
either it's consistent or it is not. Full stop. Which is not to
say that consistency is always a requirement, there are many
cases where you can do without it. But do not think that
"eventual consistency" is a kind of "relaxed consistency", rather
it is a lack of consistency.
Look, any kind of distributed system could claim to have
"eventual consistency", in the meaning that at some point, things
will be consistent. Eventual consistency does not mean that we
know when things will be consistent at some known point in time.
Frankly, not even if all the involved servers in a distributed
system claiming "eventual consistency" would stop at the same
time, would the data be consistent. But there is a way o achieve
consistency: If all the application transactions running were
allowed to stop in a controlled manner, and all operations are
then stopped, then data should, I guess, be …
Any time you can get two for the price of one (a “2Fer”), you’re
ahead of the game. By implementing our shared cache as a separate
tier, you get (1) improved performance and (2) storage
flexibility…a 2Fer.
What do I mean by storage flexibility? It means you can use
enterprise storage, cloud storage or PC-based storage. Other
shared-disk cluster databases require high-end enterprise storage
like a NAS or SAN. This requirement was driven by the need
for:
1. High-performance storage
2. Highly available storage
3. Multi-attach, or sharing data from a single volume of LUN
across multiple nodes in the cluster.
Quite simply, you won’t see other shared-disk clustering
databases using cloud storage or PC-based storage. However, the
vast majority of MySQL users rely on PC-based storage, and most
are not willing to pay the big bucks for high-end storage.
ScaleDB’s Cache …
Getting closer to some serious MySQL Cluster NDB API development on Windows, we still need a decent development environment, and as for myself, I like the ability to have a self-contained environment for this, at least contained within one computer, so that I can develop when on the road. So this means I have to use Windows as a Server anyway, right, if I am developing Windows applications? Well, not necessarily, there is always the option of using a VM, such as VirtualBox or something. But I really do prefer to use the native Windows environment for this, which has a few issues.
As I have said before, I do prefer Linux / Unix as a Server platform. But in this case, Windows will only be a development server, which is different. And if you want to use Windows as a production server, well as I have said before, that is fine too, although not my cup of tea,
But running MySQL Cluster on Windows as of version 7.1.4b of MySQL Cluster is …
[Read more]The bug I talked about a little while ago has now also had the fix I wrote committed to the mysql-trunk 5.5.6-m3 repository.
[Read more]Protecting information in databases and possibility to restore databases in case of need is the highest priority task in many companies. But not all DBMSs have built-in tools for data protection (tools to backup and restore databases). And MySQL is one of such DBMSs.
Making database backups is one of the most important things in the process of administrating MySQL databases, because some critical data loss can be irreplaceable.
The task of making daily mysql backup can be solved with the help of the backup database function of dbForge Studio for MySQL. To use it, you should setup backup in the wizard manually and schedule making backups.
To open the Database Backup wizard, you should choose Database → Backup Database from the main menu. …
[Read more]Connector/J has long provided an effective means to distribute read/write load across multiple MySQL server instances for Cluster or master-master replication deployments, but until version 5.1.13, managing such deployments frequently required a service outage to redeploy a new configuration. Given that ease of scaling out by adding additional MySQL Cluster (server) instances is a key element in that product offering, which is also naturally targeted at deployments with very strict availability requirements, we had to add support for online changes of this nature. It’s also critical for online upgrades – the other option is to take a MySQL Cluster server instance down hard, which loses any in-process transactions and generates application exceptions, if any application is trying to use that particular server instance.
Mark Matthews and I first …
[Read more]In a previous blog post, I wrote about Connector/J’s failover policies, I described three triggers which cause Connector/J to re-balance (potentially selecting a new physical connection to another host):
Those conditions fit most needs very well, but there are situations where people are running with auto-commit enabled (no explicit transaction commit or rollback), and the end result is that Connector/J never …
[Read more]In posts on June 30 and July 6, we explained how implementing the commands “replace into” and “insert ignore” with TokuDB’s fractal trees data structures can be two orders of magnitude faster than implementing them with B-trees. Towards the end of each post, we hinted at that there are some caveats that complicate the story a little. In this post, we explain one of the complications: the calculation of affected rows.
MySQL returns the number of rows affected by a “replace” or “insert” statement to the client. For the “replace” statement, the number of affected rows is defined to be the sum of the number of rows …
[Read more]