Hi,

We have backed up our database that was developed for SQL 7, and uses some
triggers and stored procedures.
It then was restored on SQL 8.

For some reason, triggers or stored procedures are not called for all users
who log in (Via NT authentication).
Everything works fine for the administrator, but ordinary users lose
functionality.

I don't know what is different in SQL 8, compared to 7, that might cause
this issue.

I'm assuming that it has to do with user rights on triggers and stored
procedures.

Can anyone give me hints as to what difference in MSSQL 8 causes this, and
how to resolve it?

Thanks,
Lisa

Your problem is likely caused by orphaned users and not by differences in
SQL versions. Look up sp_Change_users_login in BOL. That procedure will
help identify and reconnect users and logins for your new server and old
database.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com




"Lisa Pearlson" <no@spam.plz> wrote in message
news:O%23X4PtMmDHA.2528@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> We have backed up our database that was developed for SQL 7, and uses some
> triggers and stored procedures.
> It then was restored on SQL 8.
>
> For some reason, triggers or stored procedures are not called for all
users
> who log in (Via NT authentication).
> Everything works fine for the administrator, but ordinary users lose
> functionality.
>
> I don't know what is different in SQL 8, compared to 7, that might cause
> this issue.
>
> I'm assuming that it has to do with user rights on triggers and stored
> procedures.
>
> Can anyone give me hints as to what difference in MSSQL 8 causes this, and
> how to resolve it?
>
> Thanks,
> Lisa
>
>
>