Contents
When should you use a database?
It is typical to use a database when different sets of data needs to be linked together, such as:
- Pupils in a school and their grades.
- Customer records and sales information.
- Patients’ and doctors’ records.
- Transactions between different bank accounts.
- Taxpayers and income tax payments.
Why we use databases and not lists?
You can look up data from a database relatively rapidly. You can relate data from two different tables together using JOINs. Databases can handle very large data sets. Databases are concurrent; multiple users can use them at the same time without corrupting the data.
Why is using a database more efficient than using a list?
User Access and Security Databases are ideal for sharing and collaboration of information. Since multiple people can access and update the database concurrently, a database is more efficient and the potential for errors is reduced. Databases provide centralized data storage and offer better security.
When should a database be used in an organization?
Businesses use their databases to:
- Keep track of basic transactions.
- Provide information that will help the company run the business more efficiently.
- Help managers and employees make better decisions.
How is a database better than a spreadsheet?
The big difference is that in a database each table has a unique set of columns and rows, and different relationships can be made between the different tables. Databases are better for long-term storage of records that will be subject to changes. Databases have a far greater storage capacity than spreadsheets.
Why is a database considered to be self describing?
A database system is referred to as self-describing because it not only contains the database itself, but also metadata which defines and describes the data and relationships between tables in the database. This information is used by the DBMS software or database users if needed.
When to use a list in a database?
If you have complex queries, I suggest you put them into a separate database. Lists are good when the data model doesn’t grow that often. Extending the amount of fields inside the columns of a list includes updating the ContentTypes directly with an STSADM that you will have to code.
When to use a database instead of a spreadsheet?
Both spreadsheets and databases are used to store and manage sets of data. The basic content in a spreadsheet or a database is a set of data values. Where spreadsheets and databases vary is in how they store and manipulate the data.
When to use database instead of SharePoint lists?
Thanks. It depends on your requirements, but from my experience here are the cases when you should use database instead of lists: 2) When you have two or more entities linked together (e.g. Customer > Invoice > Invoice Product). SharePoint is great but in the above scenarios you will have problems with SharePoint UI limitations.
Is it better to use lists or cache?
However, querying the data directly from the database (with some cache of course) will lead to a faster development without having to update all ContentTypes linked to every lists associated with it. Of course, if you activate the Caching, the data queryied from the database will be cached at the page output level.
https://www.youtube.com/watch?v=v5e_PasMdXc