SQL Language
SQL Programming
In order to work
with databases you must have some knowledge of SQL programming. SQL is a
programming language that is not owned or developed by any company, however
most all databases vendors rely on this programming standard. This must
not be confused with Microsoft's SQL Server, which is merely one database, that
as well uses the SQL programming language.
(For purposes on
this article, all references to SQL are referring to the standardized
programming language.)
Most of the lower
level databases such as Microsoft's Access or FileMaker have easy to use design
interfaces which simplify the design of a database. On the other hand,
the more powerful databases don't have easy to use interfaces, and if you want
to work with a robust DBMS (Database Management Systems), you will have to have
a solid understanding of how to create tables, fields, indexes, triggers, and
manage relationships.
If you choose to
visit any of the sites listed above, you will want to become familiar with
their design environment. The design environment and administrative
functionality will help you get an idea about managing a database. Once
you get an idea about how things work, you will be better able to participate
in selecting the best database to suit your needs.
You should expect
that the more complicated the DBMS, the more it will cost to develop and
maintain. Even once the project is completed, you will undoubtedly need
professional help to manage your database solution. However, if it is
setup properly and configured correctly, you these additional costs can be
minimized.
Learn
More about SQL Programming
|
SQL Programming (Continued)
SQL is a language
that is text based and the exact same commands will work within any database
management system. Now DBMS systems have not stopped there, they have
gone an extra step and some have enhanced their software with additional
programming languages. MS SQL Server has T-SQL, and Oracle has PL/SQL,
etc... These additional software design platforms can simplify and
enhance the design capabilities of a database.
Primary and
secondary keys are invaluable and necessary part of database design. Keys
are a part of what is typically referred to as a relational design.
Primary and secondary keys are used to relate data elements to one
another. For example, let's assume to have a customer named Bob.
Bob is in your database with many different fields of information ( First Name,
Last Name, Phone Number, etc...) Now assume that you ask bob for his
address. Bob responds that he has different addresses. He
likes to use his business address, his home address, and he likes to have his
packages shipped to his mothers house. You can probably see from this
example that Bob's three address represent a one-to-many relationship.
Bob is the one / with many different addresses. One way to handle this in
a database would be to create two tables. One table with customer
information and a second table with customer addresses. The second table
would relate to the first table using a primary key and secondary key
relationship. Let's assume that Bob's customer number is "bob1". In
the customer table "bob1" will be title the primary key, and in the address
table "bob1" will also appear and will be titled the secondary key. Using
this design, you will be able to look at any address and relate it back to a
particular customer.
Indexing should be
a major concern of any database that expects to have a large database, or a
high number of users. Both of the previously listed constraints are
subjective and primarily dependent on the servers and operating systems that
surround your database. The server and the network being two primary
causes of slow database reaction. An index helps a database to
Designing
databases using SQL can be both a time consuming and difficult task. It
is generally best left up to professionals and qualified database
administrators. If you have design questions, please don't hesitate to
visit our contact us page. If you are building your own site or want to
find out about the services we offer, please visit our Contact
Us page and we will be glad to help you.
Continue Learning about Entity Relationship
Diagrams
|