I'm trying to use the ODBC User Experience Monitor to duplicate an ODBC DSN that uses a Windows cred to authenticate to a SQL database. The domain credential is making my connection string difficult to accomplish. According to my research you cannot specify a Windows cred within a connection string. If a credential is specified it must be a SQL cred, not a domain cred. To use Windows authentication you must used integrated authentication to pass through the creds. If I am wrong about this please let me know. I've used the ODBC help file which directs me to connectionstrings.com. I cannot find a single example of a connection string that specifies a Windows cred, only a SQL cred. The Data Link Properties method has also been a dead end for me.
I realize I can simply use a SQL cred but my intention is to monitor the same connection using the same credential as the application to test the full stack.
As an alternative to this can't I use the existing DSN on the target application server? I found examples of connection strings using DSNs but it appears the ODBC User Experience Monitor attempts to find that DSN locally instead of the target sever that the application monitor is assigned to.
