hi all,
how to change the password for sql server authenication.. the user
password.. if the password changed, what effect to database sideHi Julie
You can use sp_password to change the password for a login. The user would
need to use that password the next time they logged in. For more information
see Books Online.
John
"jullie" wrote:
> hi all,
> how to change the password for sql server authenication.. the user
> password.. if the password changed, what effect to database side
>|||Hi
Take a look at sp_password stored procedure in the BOL
"jullie" <jullie@.discussions.microsoft.com> wrote in message
news:FDC1C8B0-7FA6-44B7-ABA7-D26B52E48CF3@.microsoft.com...
> hi all,
> how to change the password for sql server authenication.. the user
> password.. if the password changed, what effect to database side
>|||In article <FDC1C8B0-7FA6-44B7-ABA7-D26B52E48CF3@.microsoft.com>,
jullie@.discussions.microsoft.com says...
> hi all,
> how to change the password for sql server authenication.. the user
> password.. if the password changed, what effect to database side
>
>
In 2K the recommendation was to make the changes through the server
manager. This will change the ACL's to the new account and delete the
old ones. Doing it after the fact will set them, but not delete the old
permissions which will gave to be handled manuallyfor best security.
Anybody know if this is still true w/ SSMS in 2005?
--
Graham (Pete) Berry
PeteBerry@.Caltech.edu|||Hi Pete
I believe you are thinking of the service account rather than the SQL logins
that the OP was asking about.
For SQL 2005, Configuration manager is the recommended method of changing
the accounts see http://msdn2.microsoft.com/en-us/library/ms143746.aspx
John
"Pete Berry" wrote:
> In article <FDC1C8B0-7FA6-44B7-ABA7-D26B52E48CF3@.microsoft.com>,
> jullie@.discussions.microsoft.com says...
> > hi all,
> >
> > how to change the password for sql server authenication.. the user
> > password.. if the password changed, what effect to database side
> >
> >
> >
> In 2K the recommendation was to make the changes through the server
> manager. This will change the ACL's to the new account and delete the
> old ones. Doing it after the fact will set them, but not delete the old
> permissions which will gave to be handled manuallyfor best security.
> Anybody know if this is still true w/ SSMS in 2005?
> --
> Graham (Pete) Berry
> PeteBerry@.Caltech.edu
>|||In article <CF98DC23-1896-4019-B98C-D2490E7B5E85@.microsoft.com>,
jbellnewsposts@.hotmail.com says...
> Hi Pete
> I believe you are thinking of the service account rather than the SQL logins
> that the OP was asking about.
> For SQL 2005, Configuration manager is the recommended method of changing
> the accounts see http://msdn2.microsoft.com/en-us/library/ms143746.aspx
> John
> "Pete Berry" wrote:
> > In article <FDC1C8B0-7FA6-44B7-ABA7-D26B52E48CF3@.microsoft.com>,
> > jullie@.discussions.microsoft.com says...
> > > hi all,
> > >
> > > how to change the password for sql server authenication.. the user
> > > password.. if the password changed, what effect to database side
> > >
> > >
> > >
> > In 2K the recommendation was to make the changes through the server
> > manager. This will change the ACL's to the new account and delete the
> > old ones. Doing it after the fact will set them, but not delete the old
> > permissions which will gave to be handled manuallyfor best security.
> >
> > Anybody know if this is still true w/ SSMS in 2005?
> > --
> > Graham (Pete) Berry
> > PeteBerry@.Caltech.edu
> >
>
yup -- my bad!
--
Graham (Pete) Berry
PeteBerry@.Caltech.edu
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment