4 Comments

  1. Jonathan Allen
    Posted October 13, 2009 at 9:34 am | Permalink

    We have dedicated AD accounts that is are domain admin and SQL Server admin that noone uses without authorised agreement. All necessary services run under these accounts and physical logins are logged and alerted at the network level as the accounts gives anonymity to whoever is using it. I have them set accordingly up for SQL Response and SQL Backup. When we get a new server to build or a new license to apply I simply use the relevant account credentials to get the application working.

    • I. R,
      Posted October 20, 2009 at 9:48 pm | Permalink

      Very similar setup to the one above – AD admin account specific for server login. Problem every time the password expires on the domain/SQL server admin account… should it be set to not expire?
      I also have a 2nd domain login, which is just a power user, cannot log on at the Windows server. To run SSMS from my workstation, I have to RUNAS the server acct and enter the admin acct password…

  2. Posted April 13, 2010 at 4:40 pm | Permalink

    We use a specific Domain account for SQL Server Services that only has the rights needed for SQL Server to run. DBA’s at my company do not have Domain Admin accounts, although we, well I, am granted local administrator rights on the SQL Server Servers.

    • Adam
      Posted April 21, 2010 at 9:18 am | Permalink

      Jack,

      Thanks for your comment. We think we’ve made this much simpler in v2 and I’ve sent you an email detailing the exact permissions that will be required (these will be available publically very soon).

      We look forward to hearing what you think.

      Thanks again,
      Adam

Post a Comment

Required fields are marked *

Add an Image

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>