I recently converted a Sql Server 2000 database to Slq Server 2005. I am a
relative rookie to 2005 and I was poking around SSMS.
I noticed a Contstraint for for each table column with a default value. Is
this the norm? I didn't notice it in 2000 but then again I am not sure I
looked.
Thanks,
RJI found the Answer. Yes a constraint is built for default values
"RJ" wrote:
> I recently converted a Sql Server 2000 database to Slq Server 2005. I am a
> relative rookie to 2005 and I was poking around SSMS.
> I noticed a Contstraint for for each table column with a default value. Is
> this the norm? I didn't notice it in 2000 but then again I am not sure I
> looked.
> Thanks,
> RJ|||Hi
It is usually good practice to explicitly name your constraints (including
defaults) rather than allow SQL server to give it a name, that way you know
what it is called on all instances of the database.
John
"RJ" <RJ@.discussions.microsoft.com> wrote in message
news:B6628A4E-FA2B-435F-B33F-AE988FE610DD@.microsoft.com...
>I found the Answer. Yes a constraint is built for default values
> "RJ" wrote:
>> I recently converted a Sql Server 2000 database to Slq Server 2005. I am
>> a
>> relative rookie to 2005 and I was poking around SSMS.
>> I noticed a Contstraint for for each table column with a default value.
>> Is
>> this the norm? I didn't notice it in 2000 but then again I am not sure I
>> looked.
>> Thanks,
>> RJ|||Hi John,
I came to exactly the same conclusion and standardized the naming of all my
objects. I inhertited an Access > Sql Server 2000 > Sql Server 2005 project
and object names were all over the place.
Thanks for your input,
RJ
"John Bell" wrote:
> Hi
> It is usually good practice to explicitly name your constraints (including
> defaults) rather than allow SQL server to give it a name, that way you know
> what it is called on all instances of the database.
> John
> "RJ" <RJ@.discussions.microsoft.com> wrote in message
> news:B6628A4E-FA2B-435F-B33F-AE988FE610DD@.microsoft.com...
> >I found the Answer. Yes a constraint is built for default values
> >
> > "RJ" wrote:
> >
> >> I recently converted a Sql Server 2000 database to Slq Server 2005. I am
> >> a
> >> relative rookie to 2005 and I was poking around SSMS.
> >>
> >> I noticed a Contstraint for for each table column with a default value.
> >> Is
> >> this the norm? I didn't notice it in 2000 but then again I am not sure I
> >> looked.
> >>
> >> Thanks,
> >> RJ
>
>
No comments:
Post a Comment