Currently I am working on Authentication Database, the problem is I have to
capture so many thing in terms of users authentication.

1. Date / Time user logged IN
2. Is user login now
3. IP Address of user
4. Which Platform you last used in
5. Password must change on first login.

I have 100 types of scanario that needs to capture but I have to designed
the database in proper normalization and down the road we may have to
capture any thing, what is the best to way to design database model?

Thanks in advance.

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Sat, 19 Jul 2008 10:24:36 -0400, Noor wrote:

Hi Noor,

Three steps:

1) Gather an overview of all information required. Many people believe
this is the hardest part. It's not. It is hard, mind you, but only if
you believe that you must absolutely get it 100% right at the first go.
You don't. Just do your stinking best to get as close to 100% as
possible and prepare to add extra columns, and even tables, at a later
stage.

2) Find all functional dependencies. This is what actually is the
hardest part. Because the FDs are so simple for 95% of all cases that
one is often tempted to believe it's simple for the remaining 5% as
well. Unfortunately, errors made in this part are often harder to
correct than errors made in step 1.

3) Normalize. This is very simple once the FDs are known. Just follow
the rules up to at least 3NF (but preferably alll the way down to 5NF)
and you're set.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis