<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
Security (SS2K8)
»
working with sa account
working with sa account
Rate Topic
Display Mode
Topic Options
Author
Message
sej2008
sej2008
Posted Thursday, March 14, 2013 12:53 PM
SSC Journeyman
Group: General Forum Members
Last Login: Today @ 7:49 AM
Points: 78,
Visits: 122
I am working with sql 2008 and using all features of security but not able to understand the need and usage of "sa" account can anyone throw light on it
and also the actual use of "public" role which exists in all databases in sql?
Thanks
Post #1431195
opc.three
opc.three
Posted Thursday, March 14, 2013 3:54 PM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 6,737,
Visits: 11,791
sa is like the Windows "Administrator" account for the instance. When logged in as sa you can do any action on the instance. Lots of people, including myself, like to disable the Login since it is a well known attack vector. If your instance is in Mixed Security Mode (most are), the sa Login is enabled and someone can crack the password they can gain control of the instance.
The public Database Role is a role all Users are a member of. Think of it as the "Everyone" group you see in Windows. It has limited privileges but all Users are a member of it and they cannot be removed from the Role.
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1431284
sej2008
sej2008
Posted Thursday, March 14, 2013 11:19 PM
SSC Journeyman
Group: General Forum Members
Last Login: Today @ 7:49 AM
Points: 78,
Visits: 122
yes I got your answer but still why public role exists when we have fixed database roles and user defined roles.what are the permission given to this role.
and regarding "sa" account when it is best to use this account.
Post #1431357
opc.three
opc.three
Posted Friday, March 15, 2013 9:29 AM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 6,737,
Visits: 11,791
sej2008 (3/14/2013)
yes I got your answer but still why public role exists when we have fixed database roles and user defined roles.what are the permission given to this role.
It's like the "Everyone" Windows group. Members of public (i.e. everyone) inherits a base set of permissions all users need in order to work within the database. Things like SELECT on the Catalog View sys.tables.
The public Role can be used to also grant everyone a permission to a User-defined Object. Say you had a Stored Procedure you wanted everyone to be able to execute. You have the option of granting EXEC on that Stored Procedure to public, although that practice is discouraged in favor or creating a User-defined Database Role, granting EXEC on the Stored Procedure to the new Role, and then adding public as a member of the new Role, i.e. do not change the set of permissions granted directly to the public Role.
and regarding "sa" account when it is best to use this account.
You would use the sa Login when you needed to access the database instance as an "Administrator." Ideally though, I recommend adding specific Windows Domain Logins to the sysadmin Fixed Server Role and disabling the sa Login for the reasons previously mentioned.
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1431594
sej2008
sej2008
Posted Friday, March 15, 2013 11:24 AM
SSC Journeyman
Group: General Forum Members
Last Login: Today @ 7:49 AM
Points: 78,
Visits: 122
Thanks so much
Post #1431652
kevaburg
kevaburg
Posted Wednesday, March 20, 2013 3:53 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Yesterday @ 5:56 AM
Points: 159,
Visits: 193
Just to clarify: When you change to mixed-mode authentication from Integrated Security the 'sa' account is by default disabled. If it is enabled then it is because a SYSADMIN has enabled it.....
Post #1433104
kevaburg
kevaburg
Posted Wednesday, March 20, 2013 3:54 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Yesterday @ 5:56 AM
Points: 159,
Visits: 193
opc.three (3/14/2013)
sa is like the Windows "Administrator" account for the instance. When logged in as sa you can do any action on the instance. Lots of people, including myself, like to disable the Login since it is a well known attack vector. If your instance is in Mixed Security Mode (most are), the sa Login is enabled and someone can crack the password they can gain control of the instance.
The public Database Role is a role all Users are a member of. Think of it as the "Everyone" group you see in Windows. It has limited privileges but all Users are a member of it and they cannot be removed from the Role.
Just to clarify: When you change to mixed-mode authentication from Integrated Security the 'sa' account is by default disabled. If it is enabled then it is because a SYSADMIN has enabled it.....
Post #1433105
opc.three
opc.three
Posted Wednesday, March 20, 2013 1:04 PM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 6,737,
Visits: 11,791
kevaburg (3/20/2013)
opc.three (3/14/2013)
sa is like the Windows "Administrator" account for the instance. When logged in as sa you can do any action on the instance. Lots of people, including myself, like to disable the Login since it is a well known attack vector. If your instance is in Mixed Security Mode (most are), the sa Login is enabled and someone can crack the password they can gain control of the instance.
The public Database Role is a role all Users are a member of. Think of it as the "Everyone" group you see in Windows. It has limited privileges but all Users are a member of it and they cannot be removed from the Role.
Just to clarify: When you change to mixed-mode authentication from Integrated Security the 'sa' account is by default disabled. If it is enabled then it is because a SYSADMIN has enabled it.....
That is not my experience but I waited to respond so I could verify. When switching from Windows Authentication Mode to Mixed Mode the status of the sa Login is
not
changed. If it was enabled before the change it stays enabled.
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1433433
kevaburg
kevaburg
Posted Thursday, March 21, 2013 3:40 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Yesterday @ 5:56 AM
Points: 159,
Visits: 193
Good point. I actually just wanted to say that if was disabled in Windows authentication it would remain disabled in mixed-mode. You have cleared that point up!
Post #1433663
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
