Can I ask, if say you had an asp.net app, with sql 2005 instance that was the backend database for this basic payroll web application... and users need to login to the app with username/password.... are the users passwords typically hashed in the same table as those where you get the default sql accounts password hash like sa.
Also, what type of query is executed against the backend database when a user tries to login to such a web app, is it a a SELECT query against the password hash table? Or something different? Would there be a field in the table that has a default page to grant access to if username and password match a pair in the table, or a link to an error page if the username/password was wrong? How does the authentication query work and proceed based on if its a valid password or not?
The thing I was wondering about was if we find say a weak password against the default ms-sql "sa" account, for arguments sake, could that weak password associated with sa potentially grant an outsider access to an application from the web. Say the password for the sa account is "password" and as users credentials are hashed in the same table, if someone tried to login to the app with user "sa" password "password" could it potentially allow them access to the application, or will their likely be something in the hash table against the sa account that stops it for application login, its just for database admin/management etc?