Tag Info

Hot answers tagged

6

Row count isn't a great indicator of database size. I would not be worried about Oracle scaling to 2 billion rows. Relational databases can practically scale up into the many terabyte range. The ability to scale comes down to data model, hardware, and developer skill, user requirements, and budget. It's feasible to scale an Oracle (or SQL Server) data ...


5

Option 4: Class Table Inheritance This is a design technique used to implement a class/subclass situation. In this situation, attributes often apply only to one subclass, and not to all rows in the table. Visit the tag of the same name over in SO to see a bunch of relevant questions and answers. This has the advantage eliminating NULLS (mostly), ...


4

It's really too early to tell from what you've described - not enough detailled information. There are those who say (probably correctly) that NoSQL systems can update rapidly - even more rapidly than RDBMS technology. However, that speed comes at a price (no SQL/poor indexing) - this is the ONE thing that people should realise about NoSQL. It does have ...


3

You did not mention whether this was an OLTP or Decision Support solution; lets assume OLTP. Basically, you are asking about superclass (the set of common attributes) and subclass (the set of different attributes) by some classification. In your example you have indicated that the sub-class can have many values. When the number of sub-classes are known ...


2

Though this is years old question... In short, you can understand ACID as guarantee of data integrity/safety in any expected circumstances. As like in generic programming, all the headaches comes from multi-threading. The biggest issue on NoSQL is mostly ACI. D(urability) is usually a separated issue. If your DB is single-threaded - so only one user can ...


2

MongoDB's dynamic schema supports different fields for documents within the same collection, so there is no strict requirement for all documents to have an active field. The main consideration here will be how that affects your application logic; it may be simpler to have an explicit field present and check the value. If you have an index on a field, ...


2

To monitor - OpsCenter: http://www.datastax.com/what-we-offer/products-services/datastax-opscenter To query - DevCenter: http://www.datastax.com/what-we-offer/products-services/devcenter


2

I would recommend using InnoDB memcached over Handlersocket. The advantage of InnoDB memcached is that: It uses a standard memcached protocol, with drivers available for many programming languages. It does not automatically allow access to all tables in your database, but instead tables 'opt-in' via a mapping containers table. It has a stated support ...


1

cqlsh -k mykeyspace -e 'COPY fromTable(columnNames) TO STDOUT' | head -n -1 | cqlsh -k mykeyspace -e 'COPY toTable(columnNames) FROM STDIN'


1

There's two parts to this question: Where should the data be persisted permanently? Let's hold off on that part until we answer the second one, which is much more important: Where should the clients query to check for vulnerabilities? A caching layer. Your clients should never hit the underlying data store first. There's not a need for atomic ...


1

The data structure that maintains the bin information grows monotonically during the life of the process. The only way to remove Bin[s] is from Aerospike is to first remove the bin from all records containing it followed by a rolling restart of the cluster. You can find documentation on using scan here And see DeleteBin.java in aerospike/examples for how ...


1

I think your first idea is better. The second way, as you state, is how you would model the data in an RDBMS. If you're going to use MongoDB for fun, you might as well explore the fact that it has a different data model, and structure your collections accordingly. While I'm sure performance is not going to be an issue for the scale of this project, ...


1

I would not recommend doing automatic migrations from any relational databases (or other that differs in logic) to MongoDB. Of course it can be done, but the database performance might not be (and will most probably not be) good. Now, answering your questions directly: 1) what do you mean by MySQL parameters? 2) Check the official docs page about the ...


1

The search is made on the server host where the database service is installed. And you will only get the result set sent to you. It would make no sense your client to make this, as your client is just an interface that allows your to interact with your database. This is available for all databases.


1

Did you take a look at sstableloader http://www.datastax.com/documentation/cassandra/2.0/cassandra/tools/toolsBulkloader_t.html ?


1

Have you tried Helenos: https://github.com/tomekkup/helenos It seems good


1

You can run a --repairDatabase for that node: mongod --repair --repairpath <repair_path> Keep in mind that the repair path should have at least as your data size free disk space. (if you have 100GB, the repair path should have at least 100GB free also. That should take care of problems of that sort. Also, in the future if anything of some sort ...


1

Normally you should never do so because other revisions may be deleted after compacting the database. You should include all necessary fields to recompose(reprint) the invoice in the invoice document, like: product description, product price, total, and so on. This is the same if you would store invoices in a rdbms.


1

As usual in similar cases, I would strongly recommend that you look at Open Source solutions - well before the design phase. EVEN if you are doing something truly radical, one can always learn by standing on the shoulders of giants. I have worked as a student on the OpenEHR project, so this interests me. It's been a while, but I would start by looking here, ...


1

http://docs.mongodb.org/manual/reference/sql-comparison/ check out full documentation. everything is perfectly explained.


1

The first thing you should realize is that Accumulo is not a relational database. If you want to make it work like one, you need to create that functionality on top. One way to do this would be to create rows that look like rows in a relational table, complete with foreign keys that you link together in your application's (an Accumulo client) code. Your ...


1

Sounds on the surface like a graph database problem. If you're going to be walking the edges between users, neo4j or such like may be the one for you. You might be able to do more generic processing using a document db where every user has an _id of user_id and an array of followers _ids. Perhaps you could output to MongoDb, then use Neo4j for creating ...



Only top voted, non community-wiki answers of a minimum length are eligible