how database works??
Answers
Answered by
4
, this is your answer dear friend
plZzzzzzzzz mark me brainliest
plZzzzzzzzz mark me brainliest
Attachments:
Answered by
2
Hey Friend!!! Here is your answer _____
Access can work with remote databasesuch as SQL Server, but is normally used as a package on a single computer using its own database. The Access application server is called Form View. The Access developer modules for forms, tables, etc. are called Design Views.
Originally Answered: How do databases work?
Original question
How do databases work?
There are different kind of databases, my daily work is on MS SQL Server so I'm focusing on this particular kind.
SQL Server is a Relational DataBase System from Microsoft. The main purpose of a database (loosely speaking) is to collect, store, edit and retrieve data in a quick and secure way.
This is accomplished with several actions, one of them being inserting data into tables. It's an easy analogy to think about a database table like an excel spreadsheet with rows, columns, and data in the cell at the intersection of such rows and columns, of course a table is more than that but we can assume for a moment that a table is a "glorified spreadsheet".
Let's assume you have 100 books in your house, finding the book you want to read could be a difficult task: maybe you remember the title, maybe you remember the author, maybe you remember the publisher or only the year such book was published and the main color for the cover. What could be the solution for you?
Instinctively you may think to sort the books on the shelves alphabetically by author, then by year; this is easy to accomplish with a limited number of books, but when the books you have will reach 1000 how do you accomplish it? It still doesn't answer your needs of searching books by different criteria. When the books you have are 10,000? How about a big library with more than 100,000 books? The task would become impossible.
A solution to this problem would be to create a database which will contain all the information you may need to find your books: author, title, publisher, the year in which the book came out, the number of pages, the main color of the cover, a little image of the book cover, the number of the shelf this book is sitting on, the position in that shelf and so on...
These information could be initially stored all on a single table, in a spreadsheet kind of way, but soon data will be redundant and data entry could be a long task ad prone to errors since each author will hopefully write more than one book, every publisher has lots of authors under their contract and may be some books by different authors and different publishers may have the same title.
You see where this is going: we may need a table for storing authors names (and relative information), a table for publishers along with our books table.
Our books table will now contain a "number" in place of the author name, it will be like the author's code-number that will be stored in the author's table, the same will be done for the publisher.
A database is a solution to this kind of problems (and more, much more) and it's very important to design a database with it's usage in mind.
#Hope it will help you!!! Thanks______
Access can work with remote databasesuch as SQL Server, but is normally used as a package on a single computer using its own database. The Access application server is called Form View. The Access developer modules for forms, tables, etc. are called Design Views.
Originally Answered: How do databases work?
Original question
How do databases work?
There are different kind of databases, my daily work is on MS SQL Server so I'm focusing on this particular kind.
SQL Server is a Relational DataBase System from Microsoft. The main purpose of a database (loosely speaking) is to collect, store, edit and retrieve data in a quick and secure way.
This is accomplished with several actions, one of them being inserting data into tables. It's an easy analogy to think about a database table like an excel spreadsheet with rows, columns, and data in the cell at the intersection of such rows and columns, of course a table is more than that but we can assume for a moment that a table is a "glorified spreadsheet".
Let's assume you have 100 books in your house, finding the book you want to read could be a difficult task: maybe you remember the title, maybe you remember the author, maybe you remember the publisher or only the year such book was published and the main color for the cover. What could be the solution for you?
Instinctively you may think to sort the books on the shelves alphabetically by author, then by year; this is easy to accomplish with a limited number of books, but when the books you have will reach 1000 how do you accomplish it? It still doesn't answer your needs of searching books by different criteria. When the books you have are 10,000? How about a big library with more than 100,000 books? The task would become impossible.
A solution to this problem would be to create a database which will contain all the information you may need to find your books: author, title, publisher, the year in which the book came out, the number of pages, the main color of the cover, a little image of the book cover, the number of the shelf this book is sitting on, the position in that shelf and so on...
These information could be initially stored all on a single table, in a spreadsheet kind of way, but soon data will be redundant and data entry could be a long task ad prone to errors since each author will hopefully write more than one book, every publisher has lots of authors under their contract and may be some books by different authors and different publishers may have the same title.
You see where this is going: we may need a table for storing authors names (and relative information), a table for publishers along with our books table.
Our books table will now contain a "number" in place of the author name, it will be like the author's code-number that will be stored in the author's table, the same will be done for the publisher.
A database is a solution to this kind of problems (and more, much more) and it's very important to design a database with it's usage in mind.
#Hope it will help you!!! Thanks______
Similar questions