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

Identify and Delete Unused Columns & Measures

Heavy dashboards and a bad data model is a nightmare for every BI Developer. Heavy dashboards can be slow due to multiple reasons. It is always advised to stick with best practices. Are you still figuring out about those best practices then you should definitely have a quick read on Best Practice Analyser ( link ). One of the most common issues with slow dashboards is unused columns and unused measures.  It is very normal to load some extra columns and create some test measures in your dashboard but as a part of cleanup process those unused columns and unused measures should be removed. Why we are removing them? Because if you keep them then ultimately it will increase the size of your data model which is not a good practice.  How to identify the culprits (unused columns and unused measures)? In today's blog we will provide you with 2 most common external tools which will help you in identifying the culprits. More external tools😒. Who's going to pay for this? To your surprise

Best Practice Analyser (BPA) Guide

Do you want to save tons of efforts to check if your data model and PBIX file follows the standard best practices and norms? Then this blog is for you. If you are a follower of our channel we already deep dive into the importance of the DAX Studio as an external tool. If you are a beginner I would highly recommend to visit this blog . In today's blog we will check how Tabular Editor can help to optimize the data model.  Best Practice Analyser allows to define or import best practices. It will make sure that we do not violate the best practices while developing a dashboard. Isn't it exciting!! Before we start make sure you already have Tabular Editor version 2.24.1 installed on your system. To install it do visit this link and select the link for windows installer. Once Tabular Editor is installed it will reflect in your PBIX file under external tool. Also, we need to define the standard rules. To do so in your advanced scripting or C# script copy this and save it via Ctrl+S. An