It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I want to know does mysql support nosql. i have gone through the MySQL Cluster which supports the noSQL, its very confusing. So, i want to knw whether we can integrate NoSQL with MySQL and are there any tutorials on that if possible.
NoSQL databases are not built primarily on tables, and generally do not use SQL for data manipulation.
NoSQL does not use SQL as its query language. NoSQL database systems arose alongside major Internet companies which had challenges in dealing with huge quantities of data with which conventional RDBMS solutions could not cope.
This should answer your question, since MySQL is a conventional RDBMS, uses SQL for data manipulation and it's based on tables.
tl;dr: No, it doesn't.
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I've been looking for a very fast and efficient way to search a database of an enormous size without using anything other than PHP and Mysql. What would be some options I could use?
The exact same way you would do it if you had 100's of rows. That's what indexes are for.
The most you can do is pay attention to the design of the tables, indexing strategy, and throw enough hardware at the solution.
If there was a silver bullet that anyone could answer in a paragraph or two here that applied universally (since you didn't give any insight to your table structure), don't you think it would already be built into MySQL?
The good news is that you will probably find that for most searches MySQL will do the job just fine even on massive databases.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
i wanted to ask a question that i myself have been asked in class by our database teacher;
What makes MySQL different from other Sqls? I've always been using MySQL due to the fact that's what we have been taught when i learned how to program websites, but honestly? I dont know what makes MySQL better then other SQL's(For program development) such as;
SQLite
MS Access
PostgreSQL
MongoDB
I was hoping someone could point me towards the answer or perhaps even give me a explanation of it.
I hope it was alright to post this question here as i'm unsure as to were else it should have been posted.
I'd choose MySQL over
SQLite, because SQLite is too "lite" for a lot of purposes; it does not have multi-user access, so would not work quite well in server environment
MS Access and PostgreSQL, because they are less common and I'm more likely to get useful community support for them (especially valid for MS Access :-)
MongoDB, because that is not SQL database at all, and you've asked about SQL databases
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
How come many startups used MySQL or PostgreSQL rather than MongoDB when they started? Many of them seem to migrate to MongoDB later - why's that? Does it need a lot more effort in working with MongoDB? Why don't they just jump straight into MongoDB?
To quote User Dan Grossman:
You dumped a decades-tested, fully featured RDBMS for a young, beta-quality, feature-thin document store with little community support. Unless you're already running tens of thousands of dollars a month in servers and think MongoDB was a better fit for the nature of your data, you probably wasted a lot of time for negative benefit. MongoDB is fun to toy with, and I've built a few apps using it myself for that reason, but it's almost never a better choice than Postgres/MySQL/SQL Server/etc. for production applications.
Mongodb and PostgreSql thoughts
MongoDB isn't SQL based nor is it relational which takes it out of the comfort zone of most developers and out of the common lingo of most CEOs. There are enough options that don't require re-inventing the development wheel and dealing with the learning curve of a different technology.
Also the first public release was in 2009, so you're still talking about a fairly new platform and people are going to be hesitant to use it. Not to mention the experienced developer base isn't as wide as for a SQL based DB.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
When storing data in MySQL and storing the same data in SQL Server, will the size of the database differs or will it be the same for both?
Updated: What I mean exactly if we have 20 GB of disk space, and we used both SQL Server and MySQL and stored the same data exactly for example, texts, dates. All data were the same exactly in both databaes, then will the size of both be the same?
The size of the DB on disk is entirely implementation dependent, so it will likely be different. If it's not, it's just a fluke. It is also something that you shouldn't really worry about. Just buy enough disk.
It depends on many factors: block/page size, kind of data, kind of tables, type of indexes, recovery model (ms sql), data types and so on and so on.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
How to optimize queries which are already written?
Use EXPLAIN to see what's going on - what indexes are being used and so on.
If you can not change the them:
Indexes and statistics.
So you don't optimize the query but their execution plan.
If you can't change the query then it really depends on what features are available on your database engine of choice. As Ovidiu said you can use indexes and generate usage statistics to see where the bottleneck is.
Otherwise you can employ techniques like materialised views or horizontal partitioning.
Before you start make sure you know what you're optimisation target is.
IBM Informix Dynamic Server supports a feature that allows you to add optimizer directives to pre-existing SQL when it is executed (without modifying the application). Look up 'external directives' at the Informix web site for more information (or Google 'site:ibm.com informix external directives').