Can a partner tell me if the issue below is resolved in a hotfix?
My client logged into an instance of SOM and tried to run the Item Movement and Item Movement History reports. He got a SQL error whenever he tried either report stating the the source view, VIEWITEMMOVEMENT(HISTORY), didn't exist. I recreated the issue and the error is part of a piece of SQL code that drops the source view each time the report is run. The view is then recreated for the current report.
I logged into SOA and the view did exist but the owner of the view was not dbo but the utility account that I set up for day to day operations. The POS terminals use this account to access the SO database and someone on one of those terminals had run the Item Movement reports, thus, recreating then views under the utility account.
Interesting, I and my client were logged in as sa and the system didn't allow us to complete that drop.
So, this seems to me to be a bug since it's a common security practise with Sql Server to create and use accounts that are not the sa account for databse access. The Sql code should realize this and prepend the appropriate owner on objects.
Thanks :)