Domain or Workgroup

#11

Quote:

People come to this group for guidance and suggestions. Adding
comments which contradict others' suggestions or material in a
demeaning manner will make you unpopular very quickly.

Who did that? When? Where? Instead of making vague insinuations, why
don't you spell out your beef?

Since we're here, what was the point of your comment, "Must be a huge
consulting firm that you run out of your home address."? Is attempted
mockery supposed to make you popular very quickly? Or are you just deciding
not to follow your own advice ("Treat others as you expect to be treated")?

#12

"10001110101" <G10001110101 (AT) gmail (DOT) com> wrote

Quote:

Much like many of your other comments in this newsgroup. Treat others
as you expect to be treated and you won't have that problem.

People come to this group for guidance and suggestions. Adding
comments which contradict others' suggestions or material in a
demeaning manner will make you unpopular very quickly.

I just reviewed all of Arnie's comments for the last month.

All seems proper and respectful to me.
I don't see the issue.

--
Thanks,
Brad.

#13

x
"Arnie Rowland" <arnie (AT) 1568 (DOT) com> wrote

Quote:

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 (AT) discussions (DOT) microsoft.com> wrote in message
news:7A762C88-472D-4094-B560-14C5D6C972D3 (AT) microsoft (DOT) com...
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

#14

For ease of admin, both DBA and Sys Admin I would go for a Domain as the DC
and SQL Sever work together.

Rich

"Arnie Rowland" <arnie (AT) 1568 (DOT) com> wrote

Quote:

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 (AT) discussions (DOT) microsoft.com> wrote in message
news:7A762C88-472D-4094-B560-14C5D6C972D3 (AT) microsoft (DOT) com...
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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Domain or Workgroup

microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients

Re: Domain or Workgroup - 07-27-2006 , 12:16 PM

Re: Domain or Workgroup - 07-27-2006 , 05:46 PM

Re: Domain or Workgroup - 01-14-2007 , 02:11 PM

Re: Domain or Workgroup - 01-14-2007 , 02:13 PM