Re: Domain or Workgroup

What is your current infrastructure setup? Are there specific Domain
Administrators or would you be administering the domain? How many SQL
Servers are there - are they joined to the domain or part of the
workgroup?

You will need to consider the value of migrating your users and
workstations to the domain. The initial setup of the migration may be
a lot of work, but after it has been set up and moves to maintenance
mode, it may be easier to maintain than your current setup if you have
the expertise to do so in-house. There are some methods and tools that
can assist you with this migration should you decide to do so.

As far as the error message (should read SSPI) that is likely a DNS or
name resolution issue. Seeing as your infrastructure seems disparate,
this could be for any number of reasons.


Mernick wrote:
Thank you so much for the quick reply.

I was hoping to keep the users in the workgroup rather than as domain
members because this is a fairly mature system and they have two years worth
of work under there current user name setup. Contacts, word processor
documents, etc.. Moving everything over seems like quite a job.

Also during our testing I was getting a fair amount of sporatic system type
error messages if we went a couple of hours without using a work station.
Something like "Could not generate a SPSI context". It required rebooting to
reconnect to the domain.

I have a friend who has a system with 120 users, and he strongly recommends
staying away from enrolling everyone in the domain, since it will add so much
complexity to the system.

You thoughts would be greatly appreciated.

Thanks again,

Robert Mernick

"Arnie Rowland" wrote:

As far as SQL Server 2000 is concerned, Domain users are the way to go.
Windows authentication provides better security, better password control,
less 'user' maintenance for the DBA, etc..

It really is a 'no-brainer'.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"Mernick" <Mernick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A762C88-472D-4094-B560-14C5D6C972D3@xxxxxxxxxxxxxxxx
We recently moved our main application from a work group environment, to a
server environment.

What are the trade offs in having our users becoming part of our new
domain
or to remain in their work group and access SQL Server through Server
Authentication?

Hope to hear from you soon

Robert Mernick






.

Relevant Pages

  • SQL Server 2005 CTP Installation
    ... nachdem ich mich vor einer Weile schon einmal mit der Installation der SQL ... Refer to server error logs and setup logs for more information. ...
    (microsoft.public.de.sqlserver)
  • Re: SQL Server Developer Edtn 2005 - WMI Error during installation - Error:2147500034 (0x800
    ... Here is some information from the Log files that are created from the SQL ... Server setup (C:\Program Files\Microsoft SQL Server\90\Setup ... Condition "Setup is running locally." ... Windows Error Text: Source File Name: sqlchaining\sqlchainingactions.cpp ...
    (microsoft.public.sqlserver.setup)
  • RE: migrating from wmsde to sql server
    ... but should I not be able to see a compnayweb instance in SQL ... I understand that the SQL Server 2000 Setup Control ... > Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: How to configure for Two different IP subnets
    ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
    (microsoft.public.windows.server.networking)
  • Best Configuration for a 3 Node SQL 2000 Cluster on Windows 2003?
    ... Ok, I've got the cluster setup and running, but having never done this, ... I'm not sure if I'm setting up SQL right... ... Virtual Servers, ...
    (microsoft.public.sqlserver.clustering)
Loading