I have had 2 occasions where a batch, using SQLCMD on a SS2014 box has failed because the -U<username> does not have a -P. The password is null, and must remain as such for now. It is a read only login. This has been running through a scheduler system (Tidal) for quite awhile and today started failing for password.I have tried, as MS says, to place the -P at the end of the string without a password. This is supposed to use a default of NULL. Still no success.Has anyone had this issue, and solved it? If so, what was your solution. For now I have set this to a trusted connection. But there are others where this will not work.Thanks.:w00t:
↧