Post reply

SQL 2000 and the Domain controller

  • September 19, 2005 at 10:19 am

    #168512

    In setting up a new Microsoft SQL 2000 server, does that server need do be added to the domain? Can it just be a standalone server?

  • September 19, 2005 at 1:21 pm

    #591107

    Can be a standalone server without a domain.

    For windows authentication it needs a domain except if you run the application on the server itself.

    See the books online (sql server help ) for more info.

  • September 20, 2005 at 8:41 am

    #591360

    Thanks for the info!

  • September 20, 2005 at 11:14 am

    #591435

    Why would you not want to join the domain ?

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • September 21, 2005 at 12:28 am

    #591589

    SQL Server should be added to the Domain as a member server not a Domain Controller because the only users who should be using the server SQL Server is installed are the database user.  Hope this helps.

    Kind regards,

    Gift Peddie

    Kind regards,
    Gift Peddie

  • September 21, 2005 at 12:26 pm

    #591954

    The reason for not joining the domain is the dependency. If my domain controller goes down then nobody can access the SQL server. This SQL server is also serving the Web. Does this make sense?

  • September 21, 2005 at 1:05 pm

    #591975

    Don't your users log into the domain ? Don't your users computers use WINS and DNS as opposed to 'raw' IP addresses ? So the argument of not having a SQL Server in the domain for fear of the domain controller being down and it affecting SQL Server user connectivity just does not make sense. When you add the web into the picture things do not change much.

     

    My suggestion to you is to put the server in the domain <period>

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply