Re: Windows service

Tech-Archive recommends: Fix windows errors by optimizing your registry

"Mr. Arnold" <MR. Arnold@xxxxxxxxxx> wrote

[SQL Auth vs Windows Auth]

It's only good for a solution that's running in a domain. It's not good
for a solution that the users are not in a NT domain environment.

I've seen many Production SQL Databases & Apps not joined to a domain that
did this. The SQL Server just configured "WebServer1\NETWORK SERVICE" as the
user name, and granted it acccess to the database. Took about 30 seconds to
have it running.

(We can debate the wisdom of having the database & the SQL Server on the
same network, but that's a completly different argument, and still ends up
with the same solutions working just fine)

I have not seen NT Authenticated user used for a means of connecting to a
SQL Server database by any application, even in a domain.

We have very different expereinces in that regard. I see Windows Auth almost
exclusivly. When I do see SQL Auth used, it's confessed to me in hushed
tones, with downcast eyes, and usually followed with a "but we're fixing
it!" said in an urgent voice!

That seems to be a PITA for a DBA, and I think they avoid it, at least the
ones I have worked with.

Again, we have compeltly different expereince in this regard. The DBA's I
know all much prefer it....

Some DBA's have a special sequence of characters to kind of encrypt the
psw a kind of their own blend or take on the psw.

I would be very concerened about that. Custom Encryption schemes are
notoriously unsecure, and likely used more for Job Security purposes than
anything else. The right tools for the job all exist, and there's no reason
not to use them...

--
Chris Mullins


.

Relevant Pages

  • Re: CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to
    ... Go to the Database tab and click on the browse button next to the connection string. ... In the New Database Reference dialog, enter the details for the database where you want to deploy the assembly and create the user defined aggregate. ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)
  • CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to meth
    ... Now register the assembly and the aggregate in the SQL Server database you want ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... But SQL does not have a pointer data type or the ... > being told to design a database. ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)
  • Re: DBMS and lisp, etc.
    ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database. ... (eq (order-customer orderA) ...
    (comp.lang.lisp)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... a surrogate key should support the primary key. ... But SQL does not have a pointer data type or the ... > being told to design a database. ...
    (comp.databases.theory)