Dbm

This course is important to everyone's career to have a better understanding of data. We us data to gather information and make decision that are important. We are in the information age with data and software all around us. Data management is important to my career because in most jobs that I want to move up into I need experience in data management and working knowledge of SQL. Every company big and small has data that they are trying to store, query, or manipulate and it seems to have fallen into the IT realm to facilitate this. Just in my small function within the company as a computer technician we have a database for software, licenses, and computers to name a few of them. I don't even touch the accounting, sales, and marketing databases that they use to pull information. It is a small company of less then 150 people. I can only imagine the terabytes of information that giant corporation have on their databases.

No, Microsoft Access is not an enterprise tool. I know this because you said so in your first lecture. When I think about it now I see there are a few differences between Access and the other database tools. The large enterprise database software tools, such as Oracle or SQL server, are designed for mainframe operating systems and works like a client/server setup for multi-user environments. Microsoft Access on the other hand was developed for PC environment that are used by novice programmers with little or no experience. It handles relatively small database functions.

http://www.databasedev.co.uk/ms-access-vs-sql-server.html

It is bad practice to develop database systems on the fly and from what I have heard it will cause you to loss more time then you think you save. You need a plan when you design a database so that you have a precise purpose and goal in mind. This way you have all the angles covered down in an easy to follow guide. Then you physical develop the database. If you don't do it this way you are more likely to make mistakes when you design a system without a plan. With out it drawn out you can easily miss a step or even have a hard time debugging it because you don't know what steps are good and which ones aren't. This will cause further delays and more money.

Data architecture is the physical layout of your resources. It contains the data, process, and technology that are used to make up the whole system. A good architecture