We are going to change our administrator password... I have several
instances of SQL that are using this account. I know I will need to restart
SQL for the new settings to take effect.
However, this is the same account that people use to log into the console. I
made the suggestion that at the same time we change the password, we also
create another account for SQL to use. The idea was shot down because it's
looked at as too drastic. That while changing the password the current
account is using will potentially cause it's own set of problems, changing
the account that SQL uses altogether would cause even more problems. My take
is that as long as this new account has the same permissions as the old
account, theres no greater risk? Is that correct? Is it a greater risk
provided the permissions are same for the new acount as the old?
TIA, ChrisRFrom your post its looks like changing the login account or keeping the
system admin account potentially causes problem in some way or the other. In
such you need to take step-by-step approach.
--> Identify the group of users, applications. Categorize them.
--> Identify the type of permissions that needs to be assigned to each user
--> Add a role and assign that role to the group of users.
--> Now move onto the other group of users
During each of these process, discuss/inform your users about this change.
The idea is to go through these steps for each user group, till all of them
are removed from system admin account. Ideally no user should use sa account
for security reasons.
--
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restart
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console. I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My take
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>|||Oops, I didn't realize that you meant changing sql service account. Please
ignore my previous post.
I thought you wanted users to stay away from sa account.
--
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restart
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console. I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My take
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>sql
Showing posts with label password. Show all posts
Showing posts with label password. Show all posts
Thursday, March 22, 2012
changing admin password/ sql service account
We are going to change our administrator password... I have several
instances of SQL that are using this account. I know I will need to restart
SQL for the new settings to take effect.
However, this is the same account that people use to log into the console. I
made the suggestion that at the same time we change the password, we also
create another account for SQL to use. The idea was shot down because it's
looked at as too drastic. That while changing the password the current
account is using will potentially cause it's own set of problems, changing
the account that SQL uses altogether would cause even more problems. My take
is that as long as this new account has the same permissions as the old
account, theres no greater risk? Is that correct? Is it a greater risk
provided the permissions are same for the new acount as the old?
TIA, ChrisR
From your post its looks like changing the login account or keeping the
system admin account potentially causes problem in some way or the other. In
such you need to take step-by-step approach.
--> Identify the group of users, applications. Categorize them.
--> Identify the type of permissions that needs to be assigned to each user
--> Add a role and assign that role to the group of users.
--> Now move onto the other group of users
During each of these process, discuss/inform your users about this change.
The idea is to go through these steps for each user group, till all of them
are removed from system admin account. Ideally no user should use sa account
for security reasons.
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restart
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console. I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My take
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>
|||Oops, I didn't realize that you meant changing sql service account. Please
ignore my previous post.
I thought you wanted users to stay away from sa account.
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restart
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console. I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My take
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>
instances of SQL that are using this account. I know I will need to restart
SQL for the new settings to take effect.
However, this is the same account that people use to log into the console. I
made the suggestion that at the same time we change the password, we also
create another account for SQL to use. The idea was shot down because it's
looked at as too drastic. That while changing the password the current
account is using will potentially cause it's own set of problems, changing
the account that SQL uses altogether would cause even more problems. My take
is that as long as this new account has the same permissions as the old
account, theres no greater risk? Is that correct? Is it a greater risk
provided the permissions are same for the new acount as the old?
TIA, ChrisR
From your post its looks like changing the login account or keeping the
system admin account potentially causes problem in some way or the other. In
such you need to take step-by-step approach.
--> Identify the group of users, applications. Categorize them.
--> Identify the type of permissions that needs to be assigned to each user
--> Add a role and assign that role to the group of users.
--> Now move onto the other group of users
During each of these process, discuss/inform your users about this change.
The idea is to go through these steps for each user group, till all of them
are removed from system admin account. Ideally no user should use sa account
for security reasons.
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restart
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console. I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My take
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>
|||Oops, I didn't realize that you meant changing sql service account. Please
ignore my previous post.
I thought you wanted users to stay away from sa account.
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restart
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console. I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My take
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>
changing admin password/ sql service account
We are going to change our administrator password... I have several
instances of SQL that are using this account. I know I will need to restart
SQL for the new settings to take effect.
However, this is the same account that people use to log into the console. I
made the suggestion that at the same time we change the password, we also
create another account for SQL to use. The idea was shot down because it's
looked at as too drastic. That while changing the password the current
account is using will potentially cause it's own set of problems, changing
the account that SQL uses altogether would cause even more problems. My take
is that as long as this new account has the same permissions as the old
account, theres no greater risk? Is that correct? Is it a greater risk
provided the permissions are same for the new acount as the old?
TIA, ChrisRFrom your post its looks like changing the login account or keeping the
system admin account potentially causes problem in some way or the other. In
such you need to take step-by-step approach.
--> Identify the group of users, applications. Categorize them.
--> Identify the type of permissions that needs to be assigned to each user
--> Add a role and assign that role to the group of users.
--> Now move onto the other group of users
During each of these process, discuss/inform your users about this change.
The idea is to go through these steps for each user group, till all of them
are removed from system admin account. Ideally no user should use sa account
for security reasons.
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restar
t
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console.
I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My ta
ke
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>|||Oops, I didn't realize that you meant changing sql service account. Please
ignore my previous post.
I thought you wanted users to stay away from sa account.
--
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restar
t
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console.
I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My ta
ke
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>
instances of SQL that are using this account. I know I will need to restart
SQL for the new settings to take effect.
However, this is the same account that people use to log into the console. I
made the suggestion that at the same time we change the password, we also
create another account for SQL to use. The idea was shot down because it's
looked at as too drastic. That while changing the password the current
account is using will potentially cause it's own set of problems, changing
the account that SQL uses altogether would cause even more problems. My take
is that as long as this new account has the same permissions as the old
account, theres no greater risk? Is that correct? Is it a greater risk
provided the permissions are same for the new acount as the old?
TIA, ChrisRFrom your post its looks like changing the login account or keeping the
system admin account potentially causes problem in some way or the other. In
such you need to take step-by-step approach.
--> Identify the group of users, applications. Categorize them.
--> Identify the type of permissions that needs to be assigned to each user
--> Add a role and assign that role to the group of users.
--> Now move onto the other group of users
During each of these process, discuss/inform your users about this change.
The idea is to go through these steps for each user group, till all of them
are removed from system admin account. Ideally no user should use sa account
for security reasons.
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restar
t
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console.
I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My ta
ke
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>|||Oops, I didn't realize that you meant changing sql service account. Please
ignore my previous post.
I thought you wanted users to stay away from sa account.
--
- - - - - - - - -
Thanks
Yogish
"ChrisR" wrote:
> We are going to change our administrator password... I have several
> instances of SQL that are using this account. I know I will need to restar
t
> SQL for the new settings to take effect.
> However, this is the same account that people use to log into the console.
I
> made the suggestion that at the same time we change the password, we also
> create another account for SQL to use. The idea was shot down because it's
> looked at as too drastic. That while changing the password the current
> account is using will potentially cause it's own set of problems, changing
> the account that SQL uses altogether would cause even more problems. My ta
ke
> is that as long as this new account has the same permissions as the old
> account, theres no greater risk? Is that correct? Is it a greater risk
> provided the permissions are same for the new acount as the old?
> TIA, ChrisR
>
>
changing admin passwd
There is something seems strange to me that when i change the administrator password of the machine, sql server is not starting due to the problems of network.Anf forcing me to use the password that i give at the setup of win2000.Why does it occur and what do I have to do?By going to Control Pannel--->Adminsitrative Tool-->Services-->MSSQL SERVER..Double click on that and enter the new password.It should work then.
Monday, March 19, 2012
Changed sa password, db maint plan not working
Our in-house developer changed the "sa" password on the Sql 2000 server and now the database maintenance plan that I created for backups to disk isn't working. The day it stopped I received the following errors in the log:
"2003-02-13 09:20:41.37 spid58 Error: 15457, Severity: 0, State: 1
2003-02-13 09:20:41.37 spid58 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2003-02-13 09:20:41.48 spid58 Using 'xplog70.dll' version '2000.80.194' to execute extended stored procedure 'xp_msver'.
2003-02-13 15:54:25.59 spid53 Error: 15457, Severity: 0, State: 1
2003-02-13 15:54:25.59 spid53 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..:"I don't think that changing the sa password has got anything to do with the DBMaintenance plan unless you are using DTS for running the DB Backup etc etc.
"2003-02-13 09:20:41.37 spid58 Error: 15457, Severity: 0, State: 1
2003-02-13 09:20:41.37 spid58 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2003-02-13 09:20:41.48 spid58 Using 'xplog70.dll' version '2000.80.194' to execute extended stored procedure 'xp_msver'.
2003-02-13 15:54:25.59 spid53 Error: 15457, Severity: 0, State: 1
2003-02-13 15:54:25.59 spid53 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..:"I don't think that changing the sa password has got anything to do with the DBMaintenance plan unless you are using DTS for running the DB Backup etc etc.
Changed sa password - can't connect via Enterprise Manager now
A client of mine changed his SA password "because it hadn't been changed in
a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.Change the server registration to use Windows Auth instead of SQL Auth?
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed i
n a
> while". Now nobody can get into the server via Enterprise Manager trying t
o
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without promptin
g
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed i
n a
> while". Now nobody can get into the server via Enterprise Manager trying t
o
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without promptin
g
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.Change the server registration to use Windows Auth instead of SQL Auth?
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed i
n a
> while". Now nobody can get into the server via Enterprise Manager trying t
o
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without promptin
g
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed i
n a
> while". Now nobody can get into the server via Enterprise Manager trying t
o
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without promptin
g
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
Changed sa password - can't connect via Enterprise Manager now
A client of mine changed his SA password "because it hadn't been changed in a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.Change the server registration to use Windows Auth instead of SQL Auth?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.Change the server registration to use Windows Auth instead of SQL Auth?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
Changed sa password - can't connect via Enterprise Manager now
A client of mine changed his SA password "because it hadn't been changed in a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.
Change the server registration to use Windows Auth instead of SQL Auth?
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.
Change the server registration to use Windows Auth instead of SQL Auth?
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
changed password by accident. what now?
Hello,
I've changed password to the sql login wwNet we created for our intranet
application.
I expected our intranet site will fail, but it is working ok. I started a
trace on a server and I see call were made under login name wwNet.
Now I am confuse. Did this wwNet controled intranet login at all?
Or will the password change take effect only after server reboot?
Please help!
thank you
JanOn Wed, 12 Jul 2006 09:01:02 -0700, Jan wrote:
>Hello,
>I've changed password to the sql login wwNet we created for our intranet
>application.
>I expected our intranet site will fail, but it is working ok. I started a
>trace on a server and I see call were made under login name wwNet.
>Now I am confuse. Did this wwNet controled intranet login at all?
>Or will the password change take effect only after server reboot?
>Please help!
Hi Jan,
AFAIK, the passwoord change takes effect immediately for new login
attempts, but existing connections remain open.
Hugo Kornelis, SQL Server MVP
I've changed password to the sql login wwNet we created for our intranet
application.
I expected our intranet site will fail, but it is working ok. I started a
trace on a server and I see call were made under login name wwNet.
Now I am confuse. Did this wwNet controled intranet login at all?
Or will the password change take effect only after server reboot?
Please help!
thank you
JanOn Wed, 12 Jul 2006 09:01:02 -0700, Jan wrote:
>Hello,
>I've changed password to the sql login wwNet we created for our intranet
>application.
>I expected our intranet site will fail, but it is working ok. I started a
>trace on a server and I see call were made under login name wwNet.
>Now I am confuse. Did this wwNet controled intranet login at all?
>Or will the password change take effect only after server reboot?
>Please help!
Hi Jan,
AFAIK, the passwoord change takes effect immediately for new login
attempts, but existing connections remain open.
Hugo Kornelis, SQL Server MVP
changed my login password??
I changed my login password to my computer, now I can't start my SQL
services. It says it can't start because of login falure?
Nevermind. I figured it out
|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>
services. It says it can't start because of login falure?
Nevermind. I figured it out
|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>
changed my login password??
I changed my login password to my computer, now I can't start my SQL
services. It says it can't start because of login falure?
--Nevermind. I figured it out
--|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>
services. It says it can't start because of login falure?
--Nevermind. I figured it out
--|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>
changed my login password??
I changed my login password to my computer, now I can't start my SQL
services. It says it can't start because of login falure?Nevermind. I figured it out|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>
services. It says it can't start because of login falure?Nevermind. I figured it out|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>
Sunday, March 11, 2012
Changed Administrator Password
Hi There!
I have changed the Administrator password on my Windows 2003 SBS server, and
now each time I reboot the server, the SQL Server Service fails to start.
I have to change the password back to the previous one, manually start the
service, and then change the password back to what I want it to be.
Does anyone know how to get round this?
TIA
Gareth Sharp
Hi Gareth
If the SQL Services are running on a specified account then you will need to
change the password for the service account too.
In case the SQL Services are running on the Local System account then there
should be no problem in the service starting up.
Thanks
Amer M J
MCP
"Gareth Sharp" wrote:
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server, and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
>
|||Hello,
Go to the Administrative Tools/Services and find the MSSQLSERVER service.
Click for it's properties and check if the user that starts the service is
Administrator. Change the password for the new password there.
Eduardo Sicouret
American Call Center
"Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server,
> and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
|||Hi Eduardo
Thanks for the help - I have made the change, and shall check it next time
the server is rebooted.
Does it matter if it is set to Local System account or Administrator? Could
I avoid the problem in the future by changing the option to Local System
account?
Thanks In Advance
Gareth
"Eduardo Sicouret" <esicouret@.americancallcenter.com> wrote in message
news:OavZ218BGHA.1676@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hello,
> Go to the Administrative Tools/Services and find the MSSQLSERVER service.
> Click for it's properties and check if the user that starts the service is
> Administrator. Change the password for the new password there.
> Eduardo Sicouret
> American Call Center
> "Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
> news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
start.[vbcol=seagreen]
the
>
I have changed the Administrator password on my Windows 2003 SBS server, and
now each time I reboot the server, the SQL Server Service fails to start.
I have to change the password back to the previous one, manually start the
service, and then change the password back to what I want it to be.
Does anyone know how to get round this?
TIA
Gareth Sharp
Hi Gareth
If the SQL Services are running on a specified account then you will need to
change the password for the service account too.
In case the SQL Services are running on the Local System account then there
should be no problem in the service starting up.
Thanks
Amer M J
MCP
"Gareth Sharp" wrote:
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server, and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
>
|||Hello,
Go to the Administrative Tools/Services and find the MSSQLSERVER service.
Click for it's properties and check if the user that starts the service is
Administrator. Change the password for the new password there.
Eduardo Sicouret
American Call Center
"Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server,
> and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
|||Hi Eduardo
Thanks for the help - I have made the change, and shall check it next time
the server is rebooted.
Does it matter if it is set to Local System account or Administrator? Could
I avoid the problem in the future by changing the option to Local System
account?
Thanks In Advance
Gareth
"Eduardo Sicouret" <esicouret@.americancallcenter.com> wrote in message
news:OavZ218BGHA.1676@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hello,
> Go to the Administrative Tools/Services and find the MSSQLSERVER service.
> Click for it's properties and check if the user that starts the service is
> Administrator. Change the password for the new password there.
> Eduardo Sicouret
> American Call Center
> "Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
> news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
start.[vbcol=seagreen]
the
>
Changed Administrator Password
Hi There!
I have changed the Administrator password on my Windows 2003 SBS server, and
now each time I reboot the server, the SQL Server Service fails to start.
I have to change the password back to the previous one, manually start the
service, and then change the password back to what I want it to be.
Does anyone know how to get round this?
TIA
Gareth SharpHi Gareth
If the SQL Services are running on a specified account then you will need to
change the password for the service account too.
In case the SQL Services are running on the Local System account then there
should be no problem in the service starting up.
Thanks
Amer M J
MCP
"Gareth Sharp" wrote:
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server, and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
>|||Hello,
Go to the Administrative Tools/Services and find the MSSQLSERVER service.
Click for it's properties and check if the user that starts the service is
Administrator. Change the password for the new password there.
Eduardo Sicouret
American Call Center
"Gareth Sharp" <gs@.paxsoft.co.uk> escribió en el mensaje
news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server,
> and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>|||Hi Eduardo
Thanks for the help - I have made the change, and shall check it next time
the server is rebooted.
Does it matter if it is set to Local System account or Administrator? Could
I avoid the problem in the future by changing the option to Local System
account?
Thanks In Advance
Gareth
"Eduardo Sicouret" <esicouret@.americancallcenter.com> wrote in message
news:OavZ218BGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Hello,
> Go to the Administrative Tools/Services and find the MSSQLSERVER service.
> Click for it's properties and check if the user that starts the service is
> Administrator. Change the password for the new password there.
> Eduardo Sicouret
> American Call Center
> "Gareth Sharp" <gs@.paxsoft.co.uk> escribió en el mensaje
> news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> > Hi There!
> >
> > I have changed the Administrator password on my Windows 2003 SBS server,
> > and
> > now each time I reboot the server, the SQL Server Service fails to
start.
> >
> > I have to change the password back to the previous one, manually start
the
> > service, and then change the password back to what I want it to be.
> >
> > Does anyone know how to get round this?
> >
> > TIA
> >
> > Gareth Sharp
> >
> >
>
I have changed the Administrator password on my Windows 2003 SBS server, and
now each time I reboot the server, the SQL Server Service fails to start.
I have to change the password back to the previous one, manually start the
service, and then change the password back to what I want it to be.
Does anyone know how to get round this?
TIA
Gareth SharpHi Gareth
If the SQL Services are running on a specified account then you will need to
change the password for the service account too.
In case the SQL Services are running on the Local System account then there
should be no problem in the service starting up.
Thanks
Amer M J
MCP
"Gareth Sharp" wrote:
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server, and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
>|||Hello,
Go to the Administrative Tools/Services and find the MSSQLSERVER service.
Click for it's properties and check if the user that starts the service is
Administrator. Change the password for the new password there.
Eduardo Sicouret
American Call Center
"Gareth Sharp" <gs@.paxsoft.co.uk> escribió en el mensaje
news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server,
> and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>|||Hi Eduardo
Thanks for the help - I have made the change, and shall check it next time
the server is rebooted.
Does it matter if it is set to Local System account or Administrator? Could
I avoid the problem in the future by changing the option to Local System
account?
Thanks In Advance
Gareth
"Eduardo Sicouret" <esicouret@.americancallcenter.com> wrote in message
news:OavZ218BGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Hello,
> Go to the Administrative Tools/Services and find the MSSQLSERVER service.
> Click for it's properties and check if the user that starts the service is
> Administrator. Change the password for the new password there.
> Eduardo Sicouret
> American Call Center
> "Gareth Sharp" <gs@.paxsoft.co.uk> escribió en el mensaje
> news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> > Hi There!
> >
> > I have changed the Administrator password on my Windows 2003 SBS server,
> > and
> > now each time I reboot the server, the SQL Server Service fails to
start.
> >
> > I have to change the password back to the previous one, manually start
the
> > service, and then change the password back to what I want it to be.
> >
> > Does anyone know how to get round this?
> >
> > TIA
> >
> > Gareth Sharp
> >
> >
>
Changed Administrator Password
Hi There!
I have changed the Administrator password on my Windows 2003 SBS server, and
now each time I reboot the server, the SQL Server Service fails to start.
I have to change the password back to the previous one, manually start the
service, and then change the password back to what I want it to be.
Does anyone know how to get round this?
TIA
Gareth SharpHi Gareth
If the SQL Services are running on a specified account then you will need to
change the password for the service account too.
In case the SQL Services are running on the Local System account then there
should be no problem in the service starting up.
Thanks
Amer M J
MCP
"Gareth Sharp" wrote:
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server, a
nd
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
>|||Hello,
Go to the Administrative Tools/Services and find the MSSQLSERVER service.
Click for it's properties and check if the user that starts the service is
Administrator. Change the password for the new password there.
Eduardo Sicouret
American Call Center
"Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server,
> and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>|||Hi Eduardo
Thanks for the help - I have made the change, and shall check it next time
the server is rebooted.
Does it matter if it is set to Local System account or Administrator? Could
I avoid the problem in the future by changing the option to Local System
account?
Thanks In Advance
Gareth
"Eduardo Sicouret" <esicouret@.americancallcenter.com> wrote in message
news:OavZ218BGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Hello,
> Go to the Administrative Tools/Services and find the MSSQLSERVER service.
> Click for it's properties and check if the user that starts the service is
> Administrator. Change the password for the new password there.
> Eduardo Sicouret
> American Call Center
> "Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
> news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
start.[vbcol=seagreen]
the[vbcol=seagreen]
>
I have changed the Administrator password on my Windows 2003 SBS server, and
now each time I reboot the server, the SQL Server Service fails to start.
I have to change the password back to the previous one, manually start the
service, and then change the password back to what I want it to be.
Does anyone know how to get round this?
TIA
Gareth SharpHi Gareth
If the SQL Services are running on a specified account then you will need to
change the password for the service account too.
In case the SQL Services are running on the Local System account then there
should be no problem in the service starting up.
Thanks
Amer M J
MCP
"Gareth Sharp" wrote:
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server, a
nd
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>
>|||Hello,
Go to the Administrative Tools/Services and find the MSSQLSERVER service.
Click for it's properties and check if the user that starts the service is
Administrator. Change the password for the new password there.
Eduardo Sicouret
American Call Center
"Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
> Hi There!
> I have changed the Administrator password on my Windows 2003 SBS server,
> and
> now each time I reboot the server, the SQL Server Service fails to start.
> I have to change the password back to the previous one, manually start the
> service, and then change the password back to what I want it to be.
> Does anyone know how to get round this?
> TIA
> Gareth Sharp
>|||Hi Eduardo
Thanks for the help - I have made the change, and shall check it next time
the server is rebooted.
Does it matter if it is set to Local System account or Administrator? Could
I avoid the problem in the future by changing the option to Local System
account?
Thanks In Advance
Gareth
"Eduardo Sicouret" <esicouret@.americancallcenter.com> wrote in message
news:OavZ218BGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Hello,
> Go to the Administrative Tools/Services and find the MSSQLSERVER service.
> Click for it's properties and check if the user that starts the service is
> Administrator. Change the password for the new password there.
> Eduardo Sicouret
> American Call Center
> "Gareth Sharp" <gs@.paxsoft.co.uk> escribi en el mensaje
> news:doghmm$deo$1$8300dec7@.news.demon.co.uk...
start.[vbcol=seagreen]
the[vbcol=seagreen]
>
changed admin password (was "help reqd")
hi all,
i have installed mssql2k in win2000 server. since it was for my personal use, i did not give a password for the 'administrator' user in win2k. later on i cahnged the admin password,but my sqlserver did not start due to login failure.
is ther any solutions to tackle this?What account did you change the password for?hi all,
i have installed mssql2k in win2000 server. since it was for my personal use, i did not give a password for the 'administrator' user in win2k. later on i cahnged the admin password,but my sqlserver did not start due to login failure.
is ther any solutions to tackle this?|||hi
i changed the password 4 Administrator User of win2k server|||hi
i changed the password 4 Administrator User of win2k server
what is ur service log on account?
I believe u are using administrator account..... if so then u need to to update the password here too.
if it is for personal use u can use the option local system account.|||you need to change the password in the services
start->settings->control panel->administrative tools->services
find mssql( & sqlagent if your automatically starting that one as well for backups etc...). Double click... go on the log on tab, and change the password on the "this account" to the new password.|||thanks for the information
:-)
i have installed mssql2k in win2000 server. since it was for my personal use, i did not give a password for the 'administrator' user in win2k. later on i cahnged the admin password,but my sqlserver did not start due to login failure.
is ther any solutions to tackle this?What account did you change the password for?hi all,
i have installed mssql2k in win2000 server. since it was for my personal use, i did not give a password for the 'administrator' user in win2k. later on i cahnged the admin password,but my sqlserver did not start due to login failure.
is ther any solutions to tackle this?|||hi
i changed the password 4 Administrator User of win2k server|||hi
i changed the password 4 Administrator User of win2k server
what is ur service log on account?
I believe u are using administrator account..... if so then u need to to update the password here too.
if it is for personal use u can use the option local system account.|||you need to change the password in the services
start->settings->control panel->administrative tools->services
find mssql( & sqlagent if your automatically starting that one as well for backups etc...). Double click... go on the log on tab, and change the password on the "this account" to the new password.|||thanks for the information
:-)
Change W2000 Admin password, SQL serve does not authenticate
I changed myW2000 Admin password and SQL server doesn't start anymore due to
login failure. When I change it to the old password it works fine. What's
the solution? The Edit Registration Properties of my SQL server are set to
Use Windows Authentication..
Hi,
Check the SQL Server service account on Administrative Tools - Services.
If it's using administrator account that you mentioned change the password
from there as well.
(Also same for SQL Agent Service Account.)
"patrick delifer" wrote:
> I changed myW2000 Admin password and SQL server doesn't start anymore due to
> login failure. When I change it to the old password it works fine. What's
> the solution? The Edit Registration Properties of my SQL server are set to
> Use Windows Authentication..
>
>
login failure. When I change it to the old password it works fine. What's
the solution? The Edit Registration Properties of my SQL server are set to
Use Windows Authentication..
Hi,
Check the SQL Server service account on Administrative Tools - Services.
If it's using administrator account that you mentioned change the password
from there as well.
(Also same for SQL Agent Service Account.)
"patrick delifer" wrote:
> I changed myW2000 Admin password and SQL server doesn't start anymore due to
> login failure. When I change it to the old password it works fine. What's
> the solution? The Edit Registration Properties of my SQL server are set to
> Use Windows Authentication..
>
>
Change W2000 Admin password, SQL serve does not authenticate
I changed myW2000 Admin password and SQL server doesn't start anymore due to
login failure. When I change it to the old password it works fine. What's
the solution? The Edit Registration Properties of my SQL server are set to
Use Windows Authentication..Hi,
Check the SQL Server service account on Administrative Tools - Services.
If it's using administrator account that you mentioned change the password
from there as well.
(Also same for SQL Agent Service Account.)
"patrick delifer" wrote:
> I changed myW2000 Admin password and SQL server doesn't start anymore due to
> login failure. When I change it to the old password it works fine. What's
> the solution? The Edit Registration Properties of my SQL server are set to
> Use Windows Authentication..
>
>
login failure. When I change it to the old password it works fine. What's
the solution? The Edit Registration Properties of my SQL server are set to
Use Windows Authentication..Hi,
Check the SQL Server service account on Administrative Tools - Services.
If it's using administrator account that you mentioned change the password
from there as well.
(Also same for SQL Agent Service Account.)
"patrick delifer" wrote:
> I changed myW2000 Admin password and SQL server doesn't start anymore due to
> login failure. When I change it to the old password it works fine. What's
> the solution? The Edit Registration Properties of my SQL server are set to
> Use Windows Authentication..
>
>
Change Username/password
The login for our sql server is the default sa with a password.
I would like to remove the password but cant find where I can actually do
this.
Can someone help ?
TIASetting a blank SA password is not a good idea, it can leave your machine
open to virus attacks. You'd be better off setting the SA password to
something nobody knows and create a new account for people to use with only
the permissions they require.
A. Change the password of a login without a former password
This example changes the password for the login Victoria from a NULL
password to "B3r12-36".
EXEC sp_password NULL, 'B3r12-36', 'Victoria'
--
HTH
Ryan Waight, MCDBA, MCSE
"Poppy" <paul.diamond@.NOSPAMthemedialounge.com> wrote in message
news:OQjbrDEqDHA.2964@.tk2msftngp13.phx.gbl...
> The login for our sql server is the default sa with a password.
> I would like to remove the password but cant find where I can actually do
> this.
> Can someone help ?
> TIA
>|||Poppy wrote:
> The login for our sql server is the default sa with a password.
> I would like to remove the password but cant find where I can
> actually do this.
> Can someone help ?
> TIA
you really dont want to do this. the sa login is the 'system
administrator' to sql and having no password on it will open a massive
hole in your security. You should ideally only use the sa on the server
itself (to prevent sniffer attacks). You should create a seperate login
for day to day activities.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Hi,
You can login to Sql Query analyzer using NT
Administrator ( Provider this has permission to access
sql) and you can reset/change the password using
sp_password - stored procedure.
Pls try this out . Hope this will do the needful.
Raghu
>--Original Message--
>The login for our sql server is the default sa with a
password.
>I would like to remove the password but cant find where I
can actually do
>this.
>Can someone help ?
>TIA
>
>.
>|||>--Original Message--
>Poppy wrote:
>> The login for our sql server is the default sa with a
password.
>> I would like to remove the password but cant find where
I can
>> actually do this.
>> Can someone help ?
>> TIA
>you really dont want to do this. the sa login is
the 'system
>administrator' to sql and having no password on it will
open a massive
>hole in your security. You should ideally only use the sa
on the server
>itself (to prevent sniffer attacks). You should create a
seperate login
>for day to day activities.
>--
>Br,
>Mark Broadbent
>mcdba , mcse+i
>=============>.
>Yes .. you are right ! and If Mr.Poppy had forgotten the
sa password , then change with above step and set the
right password for security reasons.
Raghu
I would like to remove the password but cant find where I can actually do
this.
Can someone help ?
TIASetting a blank SA password is not a good idea, it can leave your machine
open to virus attacks. You'd be better off setting the SA password to
something nobody knows and create a new account for people to use with only
the permissions they require.
A. Change the password of a login without a former password
This example changes the password for the login Victoria from a NULL
password to "B3r12-36".
EXEC sp_password NULL, 'B3r12-36', 'Victoria'
--
HTH
Ryan Waight, MCDBA, MCSE
"Poppy" <paul.diamond@.NOSPAMthemedialounge.com> wrote in message
news:OQjbrDEqDHA.2964@.tk2msftngp13.phx.gbl...
> The login for our sql server is the default sa with a password.
> I would like to remove the password but cant find where I can actually do
> this.
> Can someone help ?
> TIA
>|||Poppy wrote:
> The login for our sql server is the default sa with a password.
> I would like to remove the password but cant find where I can
> actually do this.
> Can someone help ?
> TIA
you really dont want to do this. the sa login is the 'system
administrator' to sql and having no password on it will open a massive
hole in your security. You should ideally only use the sa on the server
itself (to prevent sniffer attacks). You should create a seperate login
for day to day activities.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Hi,
You can login to Sql Query analyzer using NT
Administrator ( Provider this has permission to access
sql) and you can reset/change the password using
sp_password - stored procedure.
Pls try this out . Hope this will do the needful.
Raghu
>--Original Message--
>The login for our sql server is the default sa with a
password.
>I would like to remove the password but cant find where I
can actually do
>this.
>Can someone help ?
>TIA
>
>.
>|||>--Original Message--
>Poppy wrote:
>> The login for our sql server is the default sa with a
password.
>> I would like to remove the password but cant find where
I can
>> actually do this.
>> Can someone help ?
>> TIA
>you really dont want to do this. the sa login is
the 'system
>administrator' to sql and having no password on it will
open a massive
>hole in your security. You should ideally only use the sa
on the server
>itself (to prevent sniffer attacks). You should create a
seperate login
>for day to day activities.
>--
>Br,
>Mark Broadbent
>mcdba , mcse+i
>=============>.
>Yes .. you are right ! and If Mr.Poppy had forgotten the
sa password , then change with above step and set the
right password for security reasons.
Raghu
change user password
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
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:
Posts (Atom)