dbo not tested
Brian Donahue
Posts: 6,590 Bronze 1
Hi Fred,
SQL Compare doesn't compare and synchronize the dbo user. I think this
is because there is no way to drop and re-create it anyway.
Regards,
Brian Donahue
Red Gate Technical Support
"Fred" <No@Thanks.com> wrote in message news:dRM8B$tAEHA.2256@server53...
> LS,
> If I compare two databases, the user 'dbo' isn't tested. So if I have a
> login
> 'dbo_database1'
>
> who is asigned to the name
> 'dbo'
>
> in the first database and this account isn't in the second database at
all,
> I don't get a difference.
>
> Regards,
>
> Fred Schenk
>
>
SQL Compare doesn't compare and synchronize the dbo user. I think this
is because there is no way to drop and re-create it anyway.
Regards,
Brian Donahue
Red Gate Technical Support
"Fred" <No@Thanks.com> wrote in message news:dRM8B$tAEHA.2256@server53...
> LS,
> If I compare two databases, the user 'dbo' isn't tested. So if I have a
> login
> 'dbo_database1'
>
> who is asigned to the name
> 'dbo'
>
> in the first database and this account isn't in the second database at
all,
> I don't get a difference.
>
> Regards,
>
> Fred Schenk
>
>
This discussion has been closed.
Comments
That's a good point. I didn't think about leveraging sp_changedbowner.
Regards,
Brian Donahue
Red Gate Technical Support
"Fred" <No@Thanks.com> wrote in message news:RMhwDshBEHA.2768@server53...
> Ofcourse there is a way to make this work.
> First you test to see if the desired user is already in the database. If
so
> you drop or revoke it. And then you bring it back or introduce it using
the
> sp_changedbowner procedure. At least that is how I have been doing it all
> the time.
>
> I needed this since we have some 3rd party software from a company who is
> only used to MS Access. If there is an update it creates any new objects
> using the active login. If the program itselfs then runs using another
login
> there is a problem.
>
> Then again, MS should drop this whole table-owner thing I haven't found
any
> good use for it anyway ;-)
>
> Regards,
>
> Fred Schenk
>
> "Brian Donahue (Red Gate)" <brian.donahue@red-gate.com> wrote
>
> > SQL Compare doesn't compare and synchronize the dbo user. I think
this
> > is because there is no way to drop and re-create it anyway.
>
> > "Fred" wrote
>
> > > If I compare two databases, the user 'dbo' isn't tested. So if I have
a
> > > login
> > > 'dbo_database1'
> > >
> > > who is asigned to the name
> > > 'dbo'
> > >
> > > in the first database and this account isn't in the second database at
> > all,
> > > I don't get a difference.
>
>