Skip to main content

SQL v/s SQLite

 


SQL (Structured Query Language) plays a pivotal role in data analysis. The main purpose to create SQL is to help in managing data stored in Relational Database Management System (RDBMS). In elementary terms, it is the language that is used to interact with the database. You must be aware of the RDBMS which uses SQL extensively such as Microsoft SQL Server, Access, Oracle. SQL and SQL lite both follow the RDBMS model. Let's check out where these two differ.

So let's understand what is SQLite? SQLite act as a library for software. As compared to SQL it does not require any server to function. Generally, RDBMS requires a server to function. SQLite functions by combining the database to the application. The application help in interacting with the database. There is this term "self-contained" which is associated with SQLite which means it can operate on its own without the support of the operating system. This feature is the highlight of SQLite and makes it available to be used on almost every device from mobiles to pcs. It supports almost every feature of SQL but does not support any stored procedures.

Unlike SQLite, SQL requires a database server which means you can't directly combine it with the app you need a server that will allow you to connect to the database files. SQL offers a better user management system where multiple users can work on large datasets which is not in the case of SQLite. When we talk about the security SQL comes with inbuilt security features which require authentication while SQLite doesn't require it.

The main question is among the two which one is used and when? Let's focus on the scenarios where each of them is effective according to my practice. When we talk about SQLite it is much effective when the data is not that big in size and you don't need any sort of scalability. There is a single user and the focus is on basic development and testing. Personally, I have worked more on SQLite because my goals are more oriented to it. 

When it comes to SQL it is much more effective when there are multiple users and require more security and authentication. SQL offers you more scalability on your project along with the ability to handle big data. SQL is used widely to create customized solutions.

Both of them are widely used database management systems it all depends on your needs. Both of them have some pros and cons associated to them. There are some differences in functionality and features at the end you need to select which befits your project.



Comments

Popular posts from this blog

Ultimate Beginners Guide to DAX Studio

There are zillions of external tools available with Power BI but DAX Studio is one of the most commonly used tools to work with DAX queries. It is a perfect tool to optimize the DAX and the data model. In this blog let's shed some light on the basic functionalities that can take your report to the next level. ARE YOU READY?  To start you will need the latest version of the DAX Studio. You can download it from their website . Don't worry you don't have to pay for the license. Fortunately, DAX Studio is a free tool As a BI Developer, I am using DAX Studio regularly. Based on my experience I use it for several purposes but in this blog, I will highlight the most common ones. Extracting a dump of all the measures used in your PBIX. Why do we need to do this? It can be used for documentation purposes also sometimes we try to reuse the DAX and such a dump comes in handy in this scenario. How to achieve it? Open the DAX Studio it is located under the external tools once you open t

Append v/s Merge in Power BI

Let's discuss another problem of the week. As a Power BI user, there are times when you want to combine queries. What are the ways to do so? In most cases, you can attain it by using either append or merge and both serve different purposes. Let's understand what do these terms mean in Power BI and how they are functionally different from each other.  It is quite common to get data from various sources and you need to combine those data depending on a particular column which is common in both tables so that you can add extra information or column to your big table. In such cases, we use merge queries. How to perform merge queries? For instance, I am considering Sample Superstore data and we will merge the returns table to the order table. You will find both merge and append in the home tab in extreme right in the power query editor. ProTip - You will find two options when you click on the drop-down in merge which are merge queries and merge queries as new. When you use merge que

Use Relationship in DAX

Data modeling is an essential part of creating perfect visuals. While creating complex data models there can be a case where you can find an inactive relationship represented by dotted lines and it occurs because you already have an active relationship between the two tables. But as a developer, you need to use both the relationship. How can it be done? You can use "Use Relationship" in such cases. Use relationship can be added to your DAX and act as a modifier or enhancer for calculation. It activates the inactive relation. But make sure you have an inactive relationship in place before using the use relationship function. Let's see how it works on Sample Superstore data. In my fact table I have two dates- Order date and Ship date. I am making the two relations between my date table and fact table. The relation between the sample superstore (date) to date table (date) is active while the relation between the sample superstore (ship date) to date table (date) is inactive