Re: Windows service
- From: "Mr. Arnold" <MR. Arnold@xxxxxxxxxx>
- Date: Fri, 26 Oct 2007 14:25:36 -0400
"Chris Mullins [MVP - C#]" <cmullins@xxxxxxxxx> wrote in message news:eiaWX%23%23FIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
"Mr. Arnold" <MR. Arnold@xxxxxxxxxx> wroteYes you should do that with NT Integrated security if the account being used on the running machine is established on SQL 2005 server and SQL 2005 express.
However, most would just use a generic user-id and psw for the logins one
for Server and one for Express and make two entries in AppSettings for
connections strings.
The recommend practice is to use Windows Auth from the service to SQL Server. It's easier to configure, less maintentance, and much more secure. In general, you should not use SQL Auth for much of anything these days.
There would be 2 connection strings in the AppConfig, one for each DB. Each of these connection strings is marked to use Integrated Authentication.
You might convince me on the little more secure, but not the less maintenance part of just having a generic user-id and psw that an app uses.
.
- Follow-Ups:
- Re: Windows service
- From: Chris Mullins [MVP - C#]
- Re: Windows service
- References:
- Windows service
- From: Rotsey
- Re: Windows service
- From: Rotsey
- Re: Windows service
- From: Mr. Arnold
- Re: Windows service
- From: Chris Mullins [MVP - C#]
- Windows service
- Prev by Date: Re: Windows service
- Next by Date: Iterating through Global Assembly Cache on Mono
- Previous by thread: Re: Windows service
- Next by thread: Re: Windows service
- Index(es):
Relevant Pages
|
