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 admin. Show all posts
Showing posts with label admin. 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.
Sunday, March 11, 2012
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..
>
>
Subscribe to:
Posts (Atom)