August 16, 2023 at 5:02 pm
I have several tables and stored procedures that have an user ID of a person that is no longer with the company that is listed in the Grantor Column under schema properties permissions window. We ran into an issue with a stored procedure executing until we change the Grantor (the user Id) Column to a persons ID that is still with the company. What is the Grantor column actually used for and should it be tied to an actual user id or should it be a service account, database id, etc. ?
I'm not a DBA, just trying to understand how the Grantor column is used due to this ID of the person that is no longer here is listed in multiple tables, stored procedures, etc. and I want to make sure we have it set correctly so we don't run into more issues down the road.
August 17, 2023 at 5:46 am
This was removed by the editor as SPAM
August 17, 2023 at 7:57 am
As Grantor is a column which is specific to your database, no one here is going to be able to help in any detail without additional information.
But, my assumption is that there is some sort of validation on that column to ensure it contains only an Id of someone who is still employed. This validation has kicked in because a user who was previously employed is no longer employed, and the consequent system updates required to ensure data integrity did not happen.
If you could let us know the following, it would be useful in tracking this down:
a) Give an example of when one of the procs fails. What is it doing at point of failure? (Updating the row? Deleting the row?)
b) Please post the text of the error message which you receive when the proc fails.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
August 17, 2023 at 10:01 am
This was removed by the editor as SPAM
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply