WSS! UserData table... why they did that ????
Denis Heliszkowski
If you did that (creating triggers on the tables) like I did... you are in
trouble now...
You should have noted that the table that WAS created when a list was
created in STS 1 is no longer created. All the list records are now stored
in a table called UserData. A huge table with hundreds of fields...
So you should now create a trigger on that table... but be aware that this
trigger will be fired always!!! if a user changes a record in ANY list on
your site... this trigger will be fired... so be careful about what it does.
Don't ask why the hell they did it !!! but the fact is that they really done
it :(
I think that it is because of the FullText index that is in SQL now... But
IMHO that was a VERY BAD approach... all the beauty of STS was that it
really created tables and relationships like a real world database
application do... anyone can comment on this ?
Regards,
Denis Heliszkowski
Portugal.
"Lisa Parris" <li...@parrisonline.com> wrote in message
news:eOhseOw8...@TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction regarding where I should
looking
> to replicate the functionality we've incorporated into STS 1.0 using SQL
> triggers in WSS?
>
> Basically, we're sending notifications to the creator and assignee when an
> item on a list is changed, and more importantly, we're running some stored
> procedures that tell people what's due the next day or overdue.
>
> Anyway, I just want to know from the technology standpoint what we should
be
> looking at.
>
> Thanks,
> Lisa
>
>