guest2013-1
guest
- Joined
- Aug 22, 2003
- Messages
- 19,800
- Reaction score
- 13
I have a console application that I wrote which is triggered by MSMQ whenever a new message lands in the queue.
The issue now is, and I assume this is because MSMQ is fired via Network Service, is that the connection string within the Console Application appears to be unnecessary since it ignores the User ID/Password I specify it should use, and insists on running as Network Service (which means I need to add it to SQL Server as a user)
Now before I go impersonate and what not and try to get away from it, WHY. HOW. WHEN. Surely the connection string is used exclusively when connecting to SQL Server? Why does it get overridden and suddenly the user executing the program is the one that requires the login on SQL? And not the one I specified?
The issue now is, and I assume this is because MSMQ is fired via Network Service, is that the connection string within the Console Application appears to be unnecessary since it ignores the User ID/Password I specify it should use, and insists on running as Network Service (which means I need to add it to SQL Server as a user)
Now before I go impersonate and what not and try to get away from it, WHY. HOW. WHEN. Surely the connection string is used exclusively when connecting to SQL Server? Why does it get overridden and suddenly the user executing the program is the one that requires the login on SQL? And not the one I specified?