SQLite Reviews

I used it for assignments, putting in code, and learning. The course itself provided everything sorted by links, so there were no issues there. If I were working on a new assignment or data system, it would suggest things to me. Unfortunately, I had to switch to Microsoft tech.

It was a bit easy to use compared to other tools.

It's simple. I found it pretty easy to execute my SQL queries. Since I was a beginner, it was comfortable for me to learn SQL using SQLite. However, when I used it for my professional work and for my assignments, I found some complications. Maybe I'm not proficient with it, that's why.

The main benefit for me was learning. Since I was new to SQL, SQLite helped me understand how to work with structured data.

There were some complications. For example, you have to upload the dataset into SQLite, and once it's uploaded, you might find difficulties working with it.

I used it for two to three months. 

I would rate the stability a six out of ten. There is room for improvement. 

Compared to other tools, the performance was less effective than that of Microsoft Access. There were no complications in Access when importing datasets, which is a crucial first step. If you are stuck on the first step, you are not gonna work with it. So, I faced issues importing my dataset into SQLite. Since I couldn't get assistance with SQLite, I again had to switch to Access for my work.

I didn't find SQLite to be reliable. 

I would rate the scalability a six out of ten. Most of my classmates are Windows users, and Windows already provides Microsoft Access. 

Since I have a Mac, I used SQLite. Unfortunately, I faced complications when working on my assignments, so I had to switch back to Access.

I used PostgreSQL. However, I found difficulties using PostgreSQL. 

I had to switch to Microsoft Access because I faced issues while uploading and importing my dataset into SQLite.

The SQL aspect of it is straightforward. The work itself is not complicated.

SQLite was easy to integrate into our development environment.

I learned from videos, and they guided me. It took me about five to ten minutes to get comfortable with it.

Overall, I would rate the solution a six out of ten. I would recommend it. Many people don't have good tools available. If they want to work on databases without using Microsoft Access, then SQLite is a better option for macOS users.

I also tried Oracle and SQL, but it was very hard for me to set them up. SQLite is a simpler choice. My biggest issue was importing the dataset into SQLite. If I could have done that, the rest would have been easy. It has a responsive design and is also visually appealing.

In this organization, we use SQLite as a local database stored within the mobile applications themselves.

SQLite's small footprint has positively contributed to our project's performance overall. SQLite has helped us achieve exactly what we need in terms of our requirements and goals.

In my experience, SQLite is good for scenarios where you need offline capabilities within your mobile applications. Sometimes, you want data to persist within the app even when there's no internet connectivity. To avoid showing blank screens, we can use SQLite to store data locally and then sync it with the cloud database when connectivity is restored.

There are some difficulties on the server side. When syncing data with databases like SQL Server or Oracle, SQLite requires a kind of double effort. 

We need to implement business logic either on the API side or within the mobile application for proper data syncing – both when pushing data from the server and when syncing incoming data. It would be an improvement if SQLite could connect more automatically. Right now, there's no automatic syncing approach built into SQLite, so we have to write code to fulfill that requirement.

There should be an automated thinking approach in SQLite. 

I currently work with an organization that uses SQLite. 

In my experience working with SQLite for the last six years – across three or four applications – I haven't found any major issues that would cause problems for clients or developers. 

It's a very useful plugin. We don't see other replacements for it right now. There are file-based solutions, but for local storage as opposed to cloud-based, I find this to be a stable product.

It is a scalable product. We don't always know who else might be using SQLite, as it's often adopted based on specific project requirements. If a project needs local data storage on mobile devices, then SQLite is the go-to choice. There's good adoption of SQLite in my company. 

So, we might have more than five end users using this solution. 

When I first started working with SQLite, I had concerns about how to sync data – specifically, how to sync when an application goes from offline to online. I had some questions initially, but later I found the solution.

Neutral

I'd consider myself more of a full-stack developer.

I have over ten years of experience in the IT industry, working with technologies like ASP.NET, .NET Core, and, more recently, mobile application development – specifically Android and iOS using Xamarin and MAUI.

In the last six years, I've worked extensively with technologies like CRM, Jamf, Jamf Native, MAUI, SQL Server, SQLite, .NET Core, and others. I'm also familiar with various project management methodologies.

Anything seems difficult when we start. However, it's not overly difficult once you start working and thinking about the particular model or requirements. So, initially, it might seem a bit challenging, but overall, it's easy.

It's a good value, especially considering [SQLite's open-source nature].

I'd recommend using SQLite, especially since I already know this particular plugin. If you're familiar with SQL Server concepts – tables, queries, and so on – then I definitely recommend SQLite.

It is easy for a beginner to learn to use SQLite. If you have knowledge of SQL Server, understand how to write queries, and have a basic grasp of database structures, then it's very easy to pick up and use in your project. It's straightforward.

Overall, I would rate the solution a six out of ten. I've not encountered major limitations. While we've had some questions, we've always found solutions.

We use SQLite to store data locally within our mobile applications.

We use it for storing data within the local storage of the mobile application. That's its primary purpose.

A potential drawback is that the database file stored within the application's local storage could be accessible to users. 

When you build a mobile application with SQLite, the database file is often included in the assets folder. When the app is installed, a folder is created in the device's local storage. 

In older Android versions, it was possible to access that database file directly from the local storage. I'm not sure if this is still a concern with the latest Android versions like 10, 11, or 12.

I have been using it for three years. 

I haven't encountered any problems in my use cases. So, it has been a stable product for me. 

Usage depends on project requirements. Some applications need local storage, so developers might use SQLite; others might use something like Entity Framework. It varies, and sometimes, client preferences also play a role.

There might be over a hundred end users. 

SQLite was a standard approach for storing data locally in mobile applications. That's the main reason for its adoption.

The initial setup quite simple. You download the setup files from the official source, install them on your Windows system, create a database, and then copy that database file into your mobile application. The process is clear and easy to follow.

SQLite is primarily used for embedded storage in mobile applications.

It is not expensive.

There are both pros and cons to SQLite. 

• On the positive side, it's easy to use. 


• However, a potential drawback is that the database file stored within the application's local storage could be accessible to users. 

You need to consider both the advantages and the potential security concerns.

Overall, I would rate the solution an eight out of ten. I would recommend using it. 

I can pull data from either local storage or the internet. It enables me to access data directly from my local storage or databases, even without an internet connection.

I use Flutter Technology with the JSF plugin. 

I primarily use SQLite for small-scale applications due to its limitations in storing large amounts of data. For larger-scale projects, I typically opt for MySQL or other alternatives. Storing a large number of dates in SQLite can significantly impact its performance.

I have been using the product for six years. 

SQLite is stable.

It's difficult to provide an exact number, but SQLite is used by several team members in our company. We rely on SQLite for scenarios where internet connectivity is limited or unavailable. In such cases, SQLite allows us to store and access data locally. 

I haven't contacted the tool's technical support. 

SQLite's installation is easy. We retrieved data from the product in JSON format, converted it into the desired format, and then shared it with our backend server.

The tool is open-source. 

We can use the tool for small and large projects. SQLite is the way to go if you're developing an Android application and need to store data locally. There aren't many alternatives available.

Initially, I used SQLite, and one of the reasons was that there were no issues with it. It operates using query-based storage and supports current operations. Later, I transitioned to room DB. It offers a framework with various features, making inserting and updating data easier. Additionally, it supports cloud versions, simplifying the process.

I rate the overall product a six out of ten. 

Our client’s use case for the product is database backup.

SQLite’s most valuable feature is the ability to store granular-level backups of databases.

The product’s price requires optimization. It could have a user-friendly GUI and better intelligence features. It should be integrated with HADR solutions as well.

We have been using SQLite for four years. At present, we use the latest version.

The product is very stable. I rate its stability an eight out of ten.

We have enterprise businesses as our customers for SQLite. I rate its scalability a seven out of ten.

The technical support services need improvement.

Neutral

I rate the initial setup process a seven out of ten. It takes a few days to complete by following the IT system process.

I rate the product’s pricing a six out of ten.

I recommend SQLite and rate it an eight out of ten. It is a good product.

We use the solution for the backend for deployment purposes. SQLite is the backend. If you want a dashboard, etc., you need to get a third-party app to do it. However, there are lots of options available. 

It's helped our company in two main ways. Due to the fact that it's lightweight, we are easily able to deploy even onto tablets. We can use it for handheld devices or maybe for the mainframe, and we are able to use Android. 

The product is lightweight and highly scalable.

It's easy to set up.

The solution is quite stable.

The solution is open-source and free to use.

There's a lot of great documentation online to help you troubleshoot issues or learn about processes.

There are a lot of third-party tools you can use to achieve a whole management solution. Some of them are not open-source. However, we use open-source ones.

It's not a very fast product. The performance could be better. That said, for what we have to do, it doesn't really affect us much.

I've used the solution for over 20 years or so.

The solution is stable. It's reliable. There are no bugs or glitches. It doesn't crash or freeze. It's light and easily can be put on handheld devices without weighing them down.

The solution is very scalable. If a company needs to expand it out, it can do so.

We do not interact with people. There are a lot of technical documents available that can help you figure out how to troubleshoot issues. We just download them or go to Youtube and seek tutorials. 

We have also used Pentaho, which is more robust. Setting it up was difficult and we reverted back to this product once we had so much trouble.

The initial setup is simple. It's an easy, straightforward process and is not complex or difficult. It works on all devices and is easy to install on Android. 

The solution is open-source. You do not have to pay for it in order to use it.

My company is a customer and an end-user.

I would rate the solution at a nine out of ten. It's a very good product overall and I've been very happy with its capabilities. 

I would recommend it. It is like a baseline. It is one of the things any big organization can start with. As you mature as a company, you can migrate to more robust options like Pentaho and other databases that are available.

Whenever I need a single file database that works server-less, cross-platform and has acid properties, I use SQLite. It also supports triggers which can be used for many things like handling data integrity. One more important point is that there is a Firefox extension called SQLite Manager which is a free client that helps you to do almost anything that you expect from client software.

I mostly used it at university in a Database Systems class where students are first introduced to SQL. They need something easy to use in their projects, so SQLite is the perfect candidate. As SQLite truly is cross platform some students were able to build Android applications for their final projects.  

We can share sample databases as files so no one has to populate their own. People are no longer needed to setup a server which saves time. As it is server-less you can just pop-up a browser window and start experimenting on your SQLite DB, or create one without installing any drivers whatsoever.

SQLite does not have user defined functions like other database management systems do, and you have to write C code, which is a complication that you may not get into for a user defined function.

Over four years.

I previously used the H2 database and I changed because I had problems while connecting with the PHP server.

I also looked at using an embedded MySQL DB but it was not single file and there are problems using it on a PHP server as it needs some effort to run on a Windows machine.

In my experience, I have never used SQLite in a large project, but I used it teach and create proof of concept applications, and it has served me well. For one case, I needed spatial extensions which SQLite does not have but someone else created a project which extends SQLite called SpatiaLite.

- For me it was a really fast setup, I only needed to include a library into my application
- This DMS is embedded, there is no need for the user to think about connections
- It is used for testing because many frameworks, for example Rails use SQLite as testing database
- For me was very easy to move a database
- I observed that it has not external dependencies

- I used both SQLite and MySQL and I observed that SQLite’s capabilities are inferior to MySQL.
- I noticed that SQLite does not have users and permissions, so everyone who can access the file can access all data
- Also SQLite does not have performance improvement, it does not cache queries or optimizes selects.
- I wanted to use SQLite with PHP, but I did not find many articles on the web about combining PHP with SQLite

When I first heard about SQLite, I read that it is a single-file based database which is useful for testing and for embedding in many applications. This means that all the information is stored in a single file on a file system and I use a SQLite library to open this file to read and write my data. Then I compared it with MySQL and I noticed that MySQL is a database server which got different forms to store its data.