Hi,
I've systems with merge replication setup. On publisher i 've duplicate
sa and distributor_admin login names in sysxlogins.
Can i delete them ?
why are there duplicate login names?
Regds,
amit
Hi,
The sid for all the multiple entries is that for distributor_admin
login.
??
Can i delete them ?
Regds,
Amit
|||I could understand one thing replication creates remote servers and
there it maps remote login distributor_admin to local logins
distributor_admin and sa logins . But what could be the risk for these
entries?
Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts
Thursday, March 29, 2012
duplicate sa login names in sysxlogins
Labels:
database,
delete,
distributor_admin,
duplicate,
duplicatesa,
ive,
login,
merge,
microsoft,
mysql,
names,
oracle,
publisher,
replication,
server,
setup,
sql,
systems,
sysxlogins
Thursday, March 22, 2012
Duplicate an existing SQL Login Account
How does one create a copy of an existing SQL login account. I have a
database that has a single login with everything setup. I just want to be
able to copy/duplicate the existing account to a new user so I can set a
different
password.
Thanks!You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:F0AEB5FA-2AFD-4785-9217-184B22E3CFE0@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy/duplicate the existing account to a new user so I can set a
> different
> password.
> Thanks!|||Scripting it out will work, the only downside would be remebering to
propogate all changes from user to user as things change. And things
always do change...
I'd recommend setting the permissions that are on user account to a
role instead. Then you can assign the role to the users that need
those permissions.
If needed you can deny access to objects on a user by user basis if
necessary or create another role that has those denied permissions and
assign that to the users.
HTH
Jason Strate
database that has a single login with everything setup. I just want to be
able to copy/duplicate the existing account to a new user so I can set a
different
password.
Thanks!You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:F0AEB5FA-2AFD-4785-9217-184B22E3CFE0@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy/duplicate the existing account to a new user so I can set a
> different
> password.
> Thanks!|||Scripting it out will work, the only downside would be remebering to
propogate all changes from user to user as things change. And things
always do change...
I'd recommend setting the permissions that are on user account to a
role instead. Then you can assign the role to the users that need
those permissions.
If needed you can deny access to objects on a user by user basis if
necessary or create another role that has those denied permissions and
assign that to the users.
HTH
Jason Strate
Duplicate an existing SQL Login Account
How does one create a copy of an existing SQL login account. I have a
database that has a single login with everything setup. I just want to be
able to copy/duplicate the existing account to a new user so I can set a
different
password.
Thanks!
You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:F0AEB5FA-2AFD-4785-9217-184B22E3CFE0@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy/duplicate the existing account to a new user so I can set a
> different
> password.
> Thanks!
|||Scripting it out will work, the only downside would be remebering to
propogate all changes from user to user as things change. And things
always do change...
I'd recommend setting the permissions that are on user account to a
role instead. Then you can assign the role to the users that need
those permissions.
If needed you can deny access to objects on a user by user basis if
necessary or create another role that has those denied permissions and
assign that to the users.
HTH
Jason Strate
database that has a single login with everything setup. I just want to be
able to copy/duplicate the existing account to a new user so I can set a
different
password.
Thanks!
You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:F0AEB5FA-2AFD-4785-9217-184B22E3CFE0@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy/duplicate the existing account to a new user so I can set a
> different
> password.
> Thanks!
|||Scripting it out will work, the only downside would be remebering to
propogate all changes from user to user as things change. And things
always do change...
I'd recommend setting the permissions that are on user account to a
role instead. Then you can assign the role to the users that need
those permissions.
If needed you can deny access to objects on a user by user basis if
necessary or create another role that has those denied permissions and
assign that to the users.
HTH
Jason Strate
Duplicate an existing SQL Login Account
How does one create a copy of an existing SQL login account. I have a
database that has a single login with everything setup. I just want to be
able to copy/duplicate the existing account to a new user so I can set a
different
password.
Thanks!You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:F0AEB5FA-2AFD-4785-9217-184B22E3CFE0@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy/duplicate the existing account to a new user so I can set a
> different
> password.
> Thanks!|||Scripting it out will work, the only downside would be remebering to
propogate all changes from user to user as things change. And things
always do change...
I'd recommend setting the permissions that are on user account to a
role instead. Then you can assign the role to the users that need
those permissions.
If needed you can deny access to objects on a user by user basis if
necessary or create another role that has those denied permissions and
assign that to the users.
HTH
Jason Strate
database that has a single login with everything setup. I just want to be
able to copy/duplicate the existing account to a new user so I can set a
different
password.
Thanks!You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:F0AEB5FA-2AFD-4785-9217-184B22E3CFE0@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy/duplicate the existing account to a new user so I can set a
> different
> password.
> Thanks!|||Scripting it out will work, the only downside would be remebering to
propogate all changes from user to user as things change. And things
always do change...
I'd recommend setting the permissions that are on user account to a
role instead. Then you can assign the role to the users that need
those permissions.
If needed you can deny access to objects on a user by user basis if
necessary or create another role that has those denied permissions and
assign that to the users.
HTH
Jason Strate
Duplicate an existig SQL user login account
How does one create a copy of an existing SQL login account. I have a
database that has a single login with everything setup. I just want to be
able to copy the existing account to a new user so I can set a different
password.
Thanks!You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:5EA1D83E-15E9-44B9-9707-C4AAB5C9CDB6@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy the existing account to a new user so I can set a different
> password.
> Thanks!sql
database that has a single login with everything setup. I just want to be
able to copy the existing account to a new user so I can set a different
password.
Thanks!You might be able to get what you want by "Generating SQL Script" from
the right-click context menu on the database you want to add the user
to. Place the checkmarks on the first tab to create all types of
objects, uncheck the options to create the CREATE and DROP statements on
the second tab, and go to the 3rd tab and check "Script object-level
permissions".
When you build the script, it should include commands that grant the
permissions to the current account that holds the permissions. You will
have to manually pick through the script commands to find the
appropriate ones and change the name of the user to replace the old
user's username with the new one to build an entirely new script.
While not the answer you're looking for, I think you should consider
creating one or more roles configured to grant permissions that match
the account that is configured properly now, then create the new account
and add the both user accounts to the role you created.
Good luck,
Tony Sebion
"John Williams" <JohnWilliams@.discussions.microsoft.com> wrote in
message news:5EA1D83E-15E9-44B9-9707-C4AAB5C9CDB6@.microsoft.com:
> How does one create a copy of an existing SQL login account. I have a
> database that has a single login with everything setup. I just want to be
> able to copy the existing account to a new user so I can set a different
> password.
> Thanks!sql
Friday, March 9, 2012
Dual CPU install
We have a new server with 2 CPU's but our SQL Server 2005 license is for a
single CPU. Do I have to buy a 2nd license or can I disable the setup to
only use 1 CPU? Any help on this is appreciated. Thank you.
DavidThe license states that if the edition is capable of using all the procs
then you need a license for it regardless of if you intend on using it or
not. However dual cores only count as 1 proc not two.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"David C" <dlchase@.lifetimeinc.com> wrote in message
news:%239UjrtYeIHA.288@.TK2MSFTNGP02.phx.gbl...
> We have a new server with 2 CPU's but our SQL Server 2005 license is for a
> single CPU. Do I have to buy a 2nd license or can I disable the setup to
> only use 1 CPU? Any help on this is appreciated. Thank you.
> David
>
single CPU. Do I have to buy a 2nd license or can I disable the setup to
only use 1 CPU? Any help on this is appreciated. Thank you.
DavidThe license states that if the edition is capable of using all the procs
then you need a license for it regardless of if you intend on using it or
not. However dual cores only count as 1 proc not two.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"David C" <dlchase@.lifetimeinc.com> wrote in message
news:%239UjrtYeIHA.288@.TK2MSFTNGP02.phx.gbl...
> We have a new server with 2 CPU's but our SQL Server 2005 license is for a
> single CPU. Do I have to buy a 2nd license or can I disable the setup to
> only use 1 CPU? Any help on this is appreciated. Thank you.
> David
>
Dual CPU install
We have a new server with 2 CPU's but our SQL Server 2005 license is for a
single CPU. Do I have to buy a 2nd license or can I disable the setup to
only use 1 CPU? Any help on this is appreciated. Thank you.
David
The license states that if the edition is capable of using all the procs
then you need a license for it regardless of if you intend on using it or
not. However dual cores only count as 1 proc not two.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"David C" <dlchase@.lifetimeinc.com> wrote in message
news:%239UjrtYeIHA.288@.TK2MSFTNGP02.phx.gbl...
> We have a new server with 2 CPU's but our SQL Server 2005 license is for a
> single CPU. Do I have to buy a 2nd license or can I disable the setup to
> only use 1 CPU? Any help on this is appreciated. Thank you.
> David
>
single CPU. Do I have to buy a 2nd license or can I disable the setup to
only use 1 CPU? Any help on this is appreciated. Thank you.
David
The license states that if the edition is capable of using all the procs
then you need a license for it regardless of if you intend on using it or
not. However dual cores only count as 1 proc not two.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"David C" <dlchase@.lifetimeinc.com> wrote in message
news:%239UjrtYeIHA.288@.TK2MSFTNGP02.phx.gbl...
> We have a new server with 2 CPU's but our SQL Server 2005 license is for a
> single CPU. Do I have to buy a 2nd license or can I disable the setup to
> only use 1 CPU? Any help on this is appreciated. Thank you.
> David
>
Subscribe to:
Posts (Atom)