|
|
|
Keeper of the Duck
Group: Moderators
Last Login: Yesterday @ 1:55 PM
Points: 6,584,
Visits: 1,789
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, February 11, 2009 12:05 PM
Points: 137,
Visits: 3
|
|
Great article!!
I was wondering, what security setup do you put in place for your development environments? I have been trying to set up a development environment without giving the developers sysadmin rights, but most of our developers create DTS packages which make it hard to share development. I do not want to use SQL logins to get around this.
Thanks
Dean Christie
Edited by - dmc-co on 11/04/2003 12:35:31 PM
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Wednesday, January 25, 2012 1:31 AM
Points: 29,
Visits: 12
|
|
That is indeed a good article, in future looking forward to read some more on same topic
Kindest Regards, Jaiprakash M Bankolli My Blog Suggestions for me
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 4:22 PM
Points: 66,
Visits: 483
|
|
| why did you republished 2003 article?
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Yesterday @ 3:26 PM
Points: 31,425,
Visits: 13,738
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Monday, July 30, 2012 10:42 AM
Points: 3,434,
Visits: 519
|
|
Yah. I set an sp as a startup, created a login Hacker with access to Master as db_datawriter, db_datareader and db_ddladmin. Connected as Hacker user in Management Studio I was able to modify the stored procedure to add a line for adding this Hacker to Sysadmin role. I did re-check that the Hacker person did not have ANY server roles. I was able to restart the SQL Server from Management Studio connected to SQL Server as Hacker. After I restarted the service the Hacker person was a sysadmin. While I can find the explanation that I was able to restart the service (Management Studio is run under the logged in user process that is a Windows login and my Windows login has admin rights) I find the whole thing sort of ... you know. I will re-test it Monday just to make sure. My SQL Server is 2005 RTM. I will re-test on SP 1 and SP2.
Regards, Yelena Varshal
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Tuesday, October 27, 2009 4:03 PM
Points: 68,
Visits: 44
|
|
It would be nice to put links in this old article to articles you published (later)which deal with SS 2005. And links to articles about fixed database roles and server logins - because all these go in a package ... Or I'm wrong?
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Friday, May 28, 2010 9:56 AM
Points: 77,
Visits: 248
|
|
| I actually just ran into a "problem" involving the server roles in SQL Server 2000 (and I believe 2005). We have a VB application used in house, and users have a SQL Server login. Logging in the application uses the user_name() function. Some of our users also belong to server roles. We've found that for those users, user_name() returns "dbo" instead of their user name. Instead, we apparently need to use something like system_user to return their actual user name. This seems stupid really, but apparently is a known issue? It was news to us, and now we need to change a good number of our stored procedures. Bah!
|
|
|
|