Friday, February 17, 2012

Database Creation Help

Hi All,
I am trying to build a prototype in vb with sql server backend, I have a que
stion regarding the database , due to time constraints i am in a dilema whet
her to build a normalized database or to build a denormalized database and n
ormalize it later'
Which will be a good decision?
Thanks for any help
Sudha.If you don't have time to do it right, where are you going to find the time
to do it over? At least Normalize the biggest pieces.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
quote:

> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a

question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
quote:

> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>
|||I meant total Normalization ofcourse.Apllication comes into picture only aft
er approval for the project .
Thanks.|||Usual industry practice is to throw away the prototype code when you are
building it for production.
If that is what you anticipate, I guess either way is fine.
But if you want to prove your design concept and if that is the reason you
are building a prototype, then I would do it right the first way, which is
normalized way.
Keep in mind in certain hybrid systems of OLTP/OLAP, the data is
denormalized deliberately for optimum performance between OLTP and Reporting
operations.
HTH
Satish Balusa
Corillian Corp.
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
quote:

> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a

question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
quote:

> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>
|||Thanks for the advice.
sudha
quote:

>--Original Message--
>Usual industry practice is to throw away the prototype

code when you are
quote:

>building it for production.
>If that is what you anticipate, I guess either way is

fine.
quote:

>But if you want to prove your design concept and if that

is the reason you
quote:

>are building a prototype, then I would do it right the

first way, which is
quote:

>normalized way.
>Keep in mind in certain hybrid systems of OLTP/OLAP, the

data is
quote:

>denormalized deliberately for optimum performance between

OLTP and Reporting
quote:

>operations.
>--
>HTH
>Satish Balusa
>Corillian Corp.
>
>"sudha" <anonymous@.discussions.microsoft.com> wrote in

message
quote:

>news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
backend, I have a[QUOTE]
>question regarding the database , due to time constraints

i am in a dilema
quote:

>whether to build a normalized database or to build a

denormalized database
quote:

>and normalize it later'
>
>.
>

No comments:

Post a Comment