Otis,
The app makes two connections to SQL Server. One is a standard ADO.Net
connection where you can use SQL Logins. The second connection
receives the stream of bytes to save and only authenticates using
Windows Authentication. It is possible to authenticate differently
with the two connections, but I'd want to hear why this would be
useful as it could lead to a brittle application that might only
partitially connect to SQL Server.
Another option is to change the app to install a Windows Service
running as a Windows user that has high SQL Server permissions to make
the second connection and receive the data, however this connection
would be responsible for writing the data and this service user may
not have the rights to write to the file especially if the file is on
a network share.
In general, I'd prefer the permissions to be simple as possible: only
one Windows user is involved and this user must have the appropriate
rights in both SQL Server and the filesystem, though I'm open to hear
how this restriction might cause problems for people.
Cheers,
Clay
On Tuesday, December 8, 2009, Otis Loomgard <oti...@go...> wrote:
> Hi there,
> is it possible to make a connection (and backup) with a special User and Password to connect to the database?
>
> I have tried several Versions but the commandline throws an error that the UserCredentials (it takes my Windows - logincredentials)have not the special rights to connect to the database.
>
>
> Thank you and best regards!Otis Loomgard
> Some Examples would be fine.
>
>
|