June 29, 2009 at 12:57 pm
I need to add a pin for each user in SQL login table..
Is there any way to add a column in SQL_LOGIN table.
Any suggestion on this...
Thanks
Rohit
June 29, 2009 at 12:58 pm
You can't modify the structure or content of the system tables.
June 29, 2009 at 1:55 pm
Besides, sys.sql_logins, sys.server_principals and syslogins aren't tables. They're views. The underlying tables are hidden and aren't even queryable.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 29, 2009 at 2:16 pm
Lynn and Gail, what would you say to creating a new table in a user database for holding the new data, along with the key fields from sys.sql_logins?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 29, 2009 at 2:20 pm
Alvin Ramard (6/29/2009)
Lynn and Gail, what would you say to creating a new table in a user database for holding the new data, along with the key fields from sys.sql_logins?
Hmm, wonder I do, what is the purpose of such a request? Much information still needed from OP before an answer I can provide.
June 29, 2009 at 2:24 pm
Lynn Pettis (6/29/2009)
Alvin Ramard (6/29/2009)
Lynn and Gail, what would you say to creating a new table in a user database for holding the new data, along with the key fields from sys.sql_logins?Hmm, wonder I do, what is the purpose of such a request? Much information still needed for OP before an answer I can provide.
To wait, back in the tent, we go.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 29, 2009 at 2:28 pm
Alvin Ramard (6/29/2009)
Lynn and Gail, what would you say to creating a new table in a user database for holding the new data, along with the key fields from sys.sql_logins?
It'd work. (I think, since I have no idea what the OP wants this for)
Be an absolute pain to keep in sync if a login name gets changed, added, deleted. Since neither a foreign key nor a trigger can be added to the system tables, there's no automated way to propagate such changes.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 29, 2009 at 3:35 pm
GilaMonster (6/29/2009)
Alvin Ramard (6/29/2009)
Lynn and Gail, what would you say to creating a new table in a user database for holding the new data, along with the key fields from sys.sql_logins?It'd work. (I think, since I have no idea what the OP wants this for)
Be an absolute pain to keep in sync if a login name gets changed, added, deleted. Since neither a foreign key nor a trigger can be added to the system tables, there's no automated way to propagate such changes.
Very good points Gail.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 29, 2009 at 8:38 pm
saxena.rohit (6/29/2009)
I need to add a pin for each user in SQL login table..
Why not just accept "PINS" as the password?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 9:58 pm
Picking up on what Gail was saying about triggers on the relevant system objects, whilst you can't use a trigger, you could use the "Audit Login Change" event to detect login changes
June 29, 2009 at 10:13 pm
Picking up on what Gail was saying about triggers on the relevant system objects, whilst you can't use a trigger, you could use the "Audit Login Change" event to detect login changes
Viewing 11 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply