|
|
Posted by Tom Moreau on 06/01/07 13:12
Check out:
http://msdn2.microsoft.com/en-us/library/aa224818(SQL.80).aspx
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Sonny" <SonnyKMI@gmail.com> wrote in message
news:1180703291.252760.209290@a26g2000pre.googlegroups.com...
On May 31, 4:58 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> Sonny (Sonny...@gmail.com) writes:
> > In that case, how should I deal with the ID1? I need that column to
> > be an identity column. Thanks.
>
> Oh, I should have added the the IDENTITY appears to work fine, as soon
> as I had changed the CHECK constraint.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005
> athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000
> athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Thanks for all your help. I changed CHECK constraint, and now it is
not complaining about missing partition column anymore, however, when
do the Update or Insert it gives out Server: Msg 4450, Level 16, State
1, Line 1
Cannot update partitioned view 'UTable' because the definition of the
view column 'ID1' in table '[pTable1]' has a IDENTITY constraint. So
I think IDENTITY is the another issue. As Tom mentioned in his post,
using INSTEAD OF trigger, would anyone please give me an example,
never used before.
Again, thank you very much for your help.
Navigation:
[Reply to this message]
|