September 7, 2003 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/usingsp_addalias.asp>http://www.sqlservercentral.com/columnists/awarren/usingsp_addalias.asp
September 23, 2003 at 7:25 am
this article give some example scinario of why we need sp_addalias, it's helpful.
September 23, 2004 at 4:01 am
A useful reminder of an old and under publicised stored procedure. Microsoft seem to be 'suppressing' sp_addalias in favour of roles but as you say roles don't always fit the bill. I used to work somewhere were all the developers were members of the db_owner role on the dev databases so any objects they created were owned by them, not dbo. This created complications when we moved the development into production where all objects were dbo-owned. Also, 3rd party apps seem to use aliases quite a lot.
I also agree that objects not owned by dbo are a pain. In my experience 3rd party applications are the main offenders again!
Maybe people object to aliases because it's confusing to associate login 'fred' with another database username (e.g. 'dbo', 'mary') but you can do this with database usernames anyway (e.g. sp_grantdbaccess @loginname='fred', @name_in_db='mary') so the issue is not specific to aliases.
September 23, 2004 at 4:04 am
Andy Warren - 5701 posts ??!!??
October 26, 2005 at 2:32 pm
Once I've used sp_addalias, is there a way after the fact to see what has been aliased ?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply