Windows Authentication means SQL will use the Windows Login info, correct?
If it's set that way already, then why the error?
I'm not sure how to get past this problem.
>Kevin,
>
>
>I'm creating connections to 2 databases, each on different servers.
>>
>>The first connection works. The second errors with:
>>Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
>>Reason: Not associated with a trusted SQL Server connection.
>>
>The error means that SQL Server is set to Windows Authentication only.
>
>>
>
>When I look at login 'sa' in the Enterprise Manager, the password is filled in
>>with a 10 character string.
>>
>>I did not set it, so I'm not sure whats going on.>
>For security reason the Enterprise Manager will always show password this way regardless what's actual length of it.
>
>
>I'd like it to take the Windows login info.>
>I'm not sure what you mean. You can either use SQL Server login or use WIndows Authentication.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people