I have a client that's having an issue where after changing the SA
account password the SQL server is throwing a security error stating
that the SA account doesn't have access to view XYZ. The application
calls a stored procedure that builds a query string that is run
against a fully qualified view name
(ServerName.DatabaseName.Owner.ViewName). The application was running
fine until they changed the password for the SA account. The SQL
server box is on a single node in a cluster and the web application
server is on a seperate box as well. I have a hunch there's something
cached internally in SQL server and it's trying to access the
sysobjects using an old password. I don't believe the box has been

It's a .Net application and the web.config file has a different user
associated with the application. The application doesn't have the sa
account specified anywhere. The sa account is the server admin account
has access to everything, but for soem reason when the application calls
a fully qualified view name the security context changes and the sa
account is denied access to thw view.

*** Sent via Developersdex http://www.developersdex.com ***

If an ASP is using the sa account to connect to the SQL Server, hae they
changed the password for the sa account in the connection string on the ASP
page? If this is not it what is the exact error that they are getting?

SQL Server does not cache standard login passwords locally so this cannot
be it.

Rand
This posting is provided "as is" with no warranties and confers no rights.

This was the case. For some reason the SQL box had a linked server
referencing itself. When you do a query to a fully qualified view name
it was using the linked server to login through. The account information
was changed and it now works. The linked server will be removed since
it's not needed in this setup. Thanks for the help.



*** Sent via Developersdex http://www.developersdex.com ***

By chance, is the view accessing any linked server information? If so, you
may need to update the linked server login information or it can fail with
an incorrect password.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

[quoted text, click to view]