SYM-400: Introduction to Database Structures
Storage, Indexing and Views
Paragraphs: (Any references used are after the paragraphs)
1. Likely Causes for slow returns
- Drawing from my own knowledge a likely cause could be outdated tech system
databases are on, since like other systems like my computer they need to be
constantly updated I think the same would need to be done for databases. Another one
that I can think of is something that we deal with normal network latency, since when
a query is run the requested data must be sent back over the Wi-Fi and if it is having
problems then this would be a cause for slow returns. One more thing that I can think
of is simply trying to run things on my computer is hardware limitations, since
databases are stored on servers’ things like RAM and optimization are important since
with poor RAM like on a computer it will cause slow returns.
2. Solutions for speeding up processes
- Some solutions for speeding up the query process would be indexing, in which you
will enable the database to quickly and efficiently search for specific criteria
requested, next is using the appropriate data types in which this would simply be if
you are searching for numbers use the integer data type instead of a text one and vice
versa for other things, the last solution I will talk about is trying to avoid using the
, Select *, using this one can slow down performance because it will return all columns
in a table, including the ones you may not need so it’s important to search for specific
columns instead of searching the whole thing no matter how convenient it might be
(Babu, 2023).
3. Why implementing the index will speed queries
- Drawing from what we learned in class about indexes there are many reasons so I
will go over a couple of my knowledge of what we learned in class learning about
them and using them. The index will speed up queries because they allow databases
to have increased performance when a search is run along with that the index will
allow for queries to dynamically evaluate requirements. Now drawing from the
activities and practice we did with indexes I can say that using and implementing an
index speeds up queries by allowing for us to use joins more efficiently and lastly
allowing for the WHERE and GROUP BY code we use in practice to be more
optimized.
4. Two indexing issues that affect databases with examples
- Well one indexing issues that affects databases is simply finding and removing
unused indexes, over time some data may not be needed anymore in a database and if
it has been indexed then it needs to be deleted, for example assuming if you know
what index needs to be removed let's say “OldProducts” is an index and you know it
needs to be deleted you will simply alter the table and drop the index, now if you
need to find and index then you will input a select, from, where and order by function
that will search for everything related to the index like table name, column name,
Storage, Indexing and Views
Paragraphs: (Any references used are after the paragraphs)
1. Likely Causes for slow returns
- Drawing from my own knowledge a likely cause could be outdated tech system
databases are on, since like other systems like my computer they need to be
constantly updated I think the same would need to be done for databases. Another one
that I can think of is something that we deal with normal network latency, since when
a query is run the requested data must be sent back over the Wi-Fi and if it is having
problems then this would be a cause for slow returns. One more thing that I can think
of is simply trying to run things on my computer is hardware limitations, since
databases are stored on servers’ things like RAM and optimization are important since
with poor RAM like on a computer it will cause slow returns.
2. Solutions for speeding up processes
- Some solutions for speeding up the query process would be indexing, in which you
will enable the database to quickly and efficiently search for specific criteria
requested, next is using the appropriate data types in which this would simply be if
you are searching for numbers use the integer data type instead of a text one and vice
versa for other things, the last solution I will talk about is trying to avoid using the
, Select *, using this one can slow down performance because it will return all columns
in a table, including the ones you may not need so it’s important to search for specific
columns instead of searching the whole thing no matter how convenient it might be
(Babu, 2023).
3. Why implementing the index will speed queries
- Drawing from what we learned in class about indexes there are many reasons so I
will go over a couple of my knowledge of what we learned in class learning about
them and using them. The index will speed up queries because they allow databases
to have increased performance when a search is run along with that the index will
allow for queries to dynamically evaluate requirements. Now drawing from the
activities and practice we did with indexes I can say that using and implementing an
index speeds up queries by allowing for us to use joins more efficiently and lastly
allowing for the WHERE and GROUP BY code we use in practice to be more
optimized.
4. Two indexing issues that affect databases with examples
- Well one indexing issues that affects databases is simply finding and removing
unused indexes, over time some data may not be needed anymore in a database and if
it has been indexed then it needs to be deleted, for example assuming if you know
what index needs to be removed let's say “OldProducts” is an index and you know it
needs to be deleted you will simply alter the table and drop the index, now if you
need to find and index then you will input a select, from, where and order by function
that will search for everything related to the index like table name, column name,
