I have run into an interesting senario
on ASE 12.0 consider the following.
we had a requirement for an application to perform a conversion. as part of the conversion (3rd party), it wanted to drop and create tables and stored procs. the application normally access everything from a user login.
my solution to the problem was to create a login called 'conversion' and alias it to dbo. from that id they run the conversion and then I plan to drop the login...
when I go to drop the alias from the db, i find that it says the 'conversion' id owns objects. It should not because the alias is to dbo. when i look in the database, the objects show as owned by 'dbo' as exepected. this is specified by the uid (or so i thought).
what I find however is there is a new column in sysobjects called 'loginame' and this is where I found the 'conversion' id specified. I also note that sybase central will show the same.
I can find no reference to this in manuals, seemingly no way to alter it. what I eventually did was go in manually to sysobjects and update it to null which seems to be the norm.
so bottom line; if you create an alias of dbo, and create an object, it would seem that it is really no longer owned by dbo?
anyone experience this? know where there are further details? Paul
on ASE 12.0 consider the following.
we had a requirement for an application to perform a conversion. as part of the conversion (3rd party), it wanted to drop and create tables and stored procs. the application normally access everything from a user login.
my solution to the problem was to create a login called 'conversion' and alias it to dbo. from that id they run the conversion and then I plan to drop the login...
when I go to drop the alias from the db, i find that it says the 'conversion' id owns objects. It should not because the alias is to dbo. when i look in the database, the objects show as owned by 'dbo' as exepected. this is specified by the uid (or so i thought).
what I find however is there is a new column in sysobjects called 'loginame' and this is where I found the 'conversion' id specified. I also note that sybase central will show the same.
I can find no reference to this in manuals, seemingly no way to alter it. what I eventually did was go in manually to sysobjects and update it to null which seems to be the norm.
so bottom line; if you create an alias of dbo, and create an object, it would seem that it is really no longer owned by dbo?
anyone experience this? know where there are further details? Paul