Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am starting a simple windows forms application that requires a database to store inventory and purchasing records (less than 1000 items). What I want to ask is for your opinion which 'lite' database should I use for this small project, considering that the prerequisites I'll be installing in a client computer should have 'minimal' file size.
The client computer has a running OS of Windows 7, and I don't want him to install so many files, such as the .NET framework and the server that hosts the database, just to install the main application I'm currently developing.
What I'm really asking from you guys is to find out which of these two commonly known databases should I use, and look for the 'right recipe' to be used when building the installer. Thank you.
Of the two, SQLite is simpler to install and deploy. Fewer files, smaller distribution footprint and fewer configuration options to deal with (mostly because SQLite is a library that links into your application where as MySQL is a full client/server RDBMS).
SQLite is made for extremely simple database needs, and is probably a good fit based on your description.
I have never heard of MySQL Lite and a web search turned up nothing, so I will assume you meant MySQL. MySQL is a RDBS client/server system and probably major overkill unless you plan to store many records, or to have multiple people accessing the database at the same time.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm needing to make a stand-alone application with NodeJS for Windows, Mac, and Linux
My first option for the database was SQLite but it's very small for my big data
My reason for using MySQL is that support many data and it's quickly
But the big problem is installing MySQL that it's hard to install it with end-user
And the important note is I packaging the NodeJS project and convert to exe file
Also, I use mosquito broker in this project and still no problem in the run this application.
Can I use MySQL like SQLite (stand-alone)?
Thanks
It's bad if you think Sqlite is weak
Because it's the best choice for your needing
It's simple, high performance, stand-alone and many features
My suggestion is using SQLite
Finally, I decide to use the same Sqlite because :
"SQLite supports databases up to 140 terabytes in size"
Also, I assign database file for each device and I think that is the best solution without Mysql database
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am curios why some prefer MYSQL over SQLITE, i am interested on learning MYSQL
SQLite is an embedded library, it requires no server process, and everything it saves is contained within a single, portable file. MySQL is an RDBMS server that's a lot more work to set up, but is multi-user, more scalable, and far more featured.
For example, SQLite is used for mobile applications as well as "development" instances of code where it's only lightly loaded. It can be used at scale but generally isn't, its simple design has limitations.
If you're writing a mobile application and need a local database, SQLite is not a bad call. Spinning up a huge, cumbersome MySQL process to do the same thing on a mobile device is a bad plan.
Although they're both "SQL databases" and have a lot of functional overlap, they're engineered to solve some very different problems. In some trivial use cases it might be an arbitrary choice as to which is best, but in most cases it's pretty obvious which of the two you need.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm a bit confused of this and I just want to ask: which one is a better database for our project?
Our project is a library system using bar code and a online website for the reservation of books and for the user to view if the book is available or not...
Both system and website mush have one database.
I just wanted to ask this because I'm confused about these 2 databases.
I already tried using the workbench of mysql and people keep saying that I should use sql in wamp. But I don't know the difference and what will be the outcome in storing data in our system and web.
This question is both subjective and unclear, but I'll try to add some information regardless:
WAMP (Windows, Apache, MySQL, PHP) isn't a database, it's a software stack using mySQL as the database.
By definition, you can't use WAMP (ie PHP) if you're using VB.NET: You're using WIMVB (Windows, IIS, MySQL or another database, and VB)
If you're using .NET, it usually makes sense to complete the Microsoft stack and use SQL Server, making your stack into: Windows, IIS, SQL Server and VB.NET (Although I'd recommend using C#.NET, not VB, as you'll it more widespread while being every bit as capable.
MySql would be a better choice for most applications, in my opinion. It as a good connector for .Net, and will be more flexible down the road. I would be more likely to use WAMP for a simple application with little chance for later enhancements -- a quick one-time app.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm currently setting up ghost on my server. I will host my own blog and probably some more for my friends.
Ghost uses sqlite per default. Sqlite is good for small applications and development environments.
I plan to run my blog for at least 1 - 2 years or longer if ghost will work out well. A blog contains a lot of images and text. The sqlite db will grow over time with more and more images and so on.
Is it ok to use sqlite for this purpose for several years? MySQL would be much more powerful but also more complex to setup.
What would be the best choice for a Ghost Blog?
Please note that database performance depends not so much on the amount of data (until you run out of local disk space) but on the amount of concurrency.
The SQLite documentation says:
SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, 99.9% of all websites). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.
[…]
But if your website is so busy that you are thinking of splitting the database component off onto a separate machine, then you should definitely consider using an enterprise-class client/server database engine instead of SQLite.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am working on an open source project which can use a number of DBMS' as backend. So far we supports SQL Server 2005 and SQL Server 2008 but we would also like to support some additional databases including some file based DBs.
Note: The file based databases must work on a 64-bit platform, so MS Access is not an option as there is no 64-bit provider AFAIK.
Which DBMS should a database centric open source project support in your opinion?
SQLite, definitely.
Provide ODBC support, then the end-user can choose from just about any database going.
Firebird, either in its embedded variant or as a (small footprint) server.
MySQL, it's a widely used free/open source RDBMS.
Not a file based DBMS, but you didn't say it had to be, only that you wanted a few of those too.
Support these: sqlite,mysql,postgresql
You don't mention what language you're developing in. Some, like Java, have standard database APIs, so supporting multiple SQL servers is easy, provided you can use the common denominator of the SQL language in your application.
I agree that firebird can be better than SQL Lite and M$SQL Express , or even is better than mysql , scales better with the number of CPUS and is more mature (triggers , and transactions are implemented for many many light years ago)