Passing credentials to SQL connection string

fweymouth 

You can't specify alternate Windows credentials in a connection string. When you leverage the integrated authentication option, the credentials of the host process are used.

Which brings me to some simple alternatives to worrying about the connection string:

1. Launch a new PowerShell shell using "run as a different user" and use the appropriate credentials from the remote forest (assuming the forest trusts facilitate doing this);
2. Use Invoke-Command, New-PSSession, Start-Process, etc. with the -Credential parameter to run the script under the context of the account from the remote forest;
3. Use an SQL account, not a Windows account, in the connection string.

I'd probably go with the first option if I was going to do a few things against the server. If it was just running the one command, I'd probably go with Invoke-Command, but to each their own.

I mention point 3 for completeness, but really, it's a rubbish solution. There really shouldn't be common SQL-defined logins across multiple SQL hosts.

Cheers,

Lain