On Jun 28, 8:51 pm, "news.usenetserver.com" <charle... (AT) msn (DOT) com> wrote:
You say nothing about the requirements for the applications, so we
cannot comment about the database design specifically.

I would suggest that you learn data modeling. Take a course or two at
your community college on databases. Or find a senior developer at
your company to mentor you. Also, talk to the DBA about your database
design. Try to learn both the practical aspects of the DBMS you are
using and the theory of Relational databases.

HTH,
ed

news.usenetserver.com wrote:

Disclaimer: I am not a DBA. I also started as a sysadmin.

I found the following quite useful and well written:


Data Modeling Essentials - Third Edition (by G. Simsion - G. Witt)
SQL Programming Style (J.Celko)
Data and Databases; Concepts in Practice (J.Celko)

Although there is some overlap, you might benefit from several books and
grok more nuances.
Avoid traps and books with examples in mysql-ese or a deep love for
surrogate keys.

These 3 books are not about theory: if you are not bored by theory or
something doesn't click right in you head about how relations and
non-procedural stuff works, you could read "Databases in Depth:
Relational Theory for Practitioners" by C.J.Date.

If you are dealing with legacy schemas there are some recipes to keep
sanity:

Refactoring Databases: Evolutionary Database Design (S.W. Ambler -P.J.
Sadalage)

At last, when you know how to deal with correctness and clarity, you
will want to keep performance in mind from the start:

The Art of SQL (Stephane Faroult)

news.usenetserver.com wrote:

Disclaimer: I am not a DBA. I also started as a sysadmin.

I found the following quite useful and well written:


Data Modeling Essentials - Third Edition (by G. Simsion - G. Witt)
SQL Programming Style (J.Celko)
Data and Databases; Concepts in Practice (J.Celko)

Although there is some overlap, you might benefit from several books and
grok more nuances.
Avoid traps and books with examples in mysql-ese or a deep love for
surrogate keys.

These 3 books are not about theory: if you are not bored by theory or
something doesn't click right in you head about how relations and
non-procedural stuff works, you could read "Databases in Depth:
Relational Theory for Practitioners" by C.J.Date.

If you are dealing with legacy schemas there are some recipes to keep
sanity:

Refactoring Databases: Evolutionary Database Design (S.W. Ambler -P.J.
Sadalage)

At last, when you know how to deal with correctness and clarity, you
will want to keep performance in mind from the start:

The Art of SQL (Stephane Faroult)

news.usenetserver.com wrote:

Disclaimer: I am not a DBA. I also started as a sysadmin.

I found the following quite useful and well written:


Data Modeling Essentials - Third Edition (by G. Simsion - G. Witt)
SQL Programming Style (J.Celko)
Data and Databases; Concepts in Practice (J.Celko)

Although there is some overlap, you might benefit from several books and
grok more nuances.
Avoid traps and books with examples in mysql-ese or a deep love for
surrogate keys.

These 3 books are not about theory: if you are not bored by theory or
something doesn't click right in you head about how relations and
non-procedural stuff works, you could read "Databases in Depth:
Relational Theory for Practitioners" by C.J.Date.

If you are dealing with legacy schemas there are some recipes to keep
sanity:

Refactoring Databases: Evolutionary Database Design (S.W. Ambler -P.J.
Sadalage)

At last, when you know how to deal with correctness and clarity, you
will want to keep performance in mind from the start:

The Art of SQL (Stephane Faroult)

My apologies. One of the applications is a casino ban form that will
be shared among seven casino sites. It has to use a browser UI and I
have MS SQL 2005 Enterprise as the backend database.

I suppose my biggest problem with that is establishing the necessary
security so that only certain users can create and update bans and
other users can only view the bans and perform searches using criteria
available on the ban form. The criteria would be items such as the
date of the ban, casino location, type of ban, etc.

The other application is a little too complex to explain in one
posting and I do not plan to start on it until I finish the ban form.

Unfortunately, there is no DBA or senior developer here. The
combination of those two positions is what I am being migrated toward.
I know that there is a lot to learn but I will gradually get to where
I can create professional databases.

On Mon, 30 Jun 2008 05:29:52 -0700 (PDT), Ed Prochak
<edprochak (AT) gmail (DOT) com> wrote:

My apologies. One of the applications is a casino ban form that will
be shared among seven casino sites. It has to use a browser UI and I
have MS SQL 2005 Enterprise as the backend database.

I suppose my biggest problem with that is establishing the necessary
security so that only certain users can create and update bans and
other users can only view the bans and perform searches using criteria
available on the ban form. The criteria would be items such as the
date of the ban, casino location, type of ban, etc.

The other application is a little too complex to explain in one
posting and I do not plan to start on it until I finish the ban form.

Unfortunately, there is no DBA or senior developer here. The
combination of those two positions is what I am being migrated toward.
I know that there is a lot to learn but I will gradually get to where
I can create professional databases.

On Mon, 30 Jun 2008 05:29:52 -0700 (PDT), Ed Prochak
<edprochak (AT) gmail (DOT) com> wrote:

My apologies. One of the applications is a casino ban form that will
be shared among seven casino sites. It has to use a browser UI and I
have MS SQL 2005 Enterprise as the backend database.

I suppose my biggest problem with that is establishing the necessary
security so that only certain users can create and update bans and
other users can only view the bans and perform searches using criteria
available on the ban form. The criteria would be items such as the
date of the ban, casino location, type of ban, etc.

The other application is a little too complex to explain in one
posting and I do not plan to start on it until I finish the ban form.

Unfortunately, there is no DBA or senior developer here. The
combination of those two positions is what I am being migrated toward.
I know that there is a lot to learn but I will gradually get to where
I can create professional databases.

On Mon, 30 Jun 2008 05:29:52 -0700 (PDT), Ed Prochak
<edprochak (AT) gmail (DOT) com> wrote: