Comments
Sort by recent activity
Your synopsis is accurate.
Seems to be happening to all functions and stored procedures. Will test triggers to see if it is working. I am not willing to say that it is NOT intermittent, as we were running RedGate for a week or two before I noticed this behavior.
Began looking at the login we use to access our local copies. It appears that the user tied to the database had become unlinked from the login for the instance. After deleting the user, and then recreating it from the login, everything seems to be working.
It still bothers me that there were no errors. There should have been a message or something that said the drop was not allowed or something.
Thanks,
--Glenn. / comments
Your synopsis is accurate.
Seems to be happening to all functions and stored procedures. Will test triggers to see if it is working. I am not willing to say that it is NOT intermittent, as we wer...
After more testing, it appears that the drop from "get latest" is not actually happening. There is no error reported.
We have tested this with two of us several times. Whom ever does the drop propagates out the drop, and the other WILL see the drop when doing "get latest", but the drop doesn't fire. When "Commit changes" is selected by the second person, the stored procedure gets added back in. / comments
After more testing, it appears that the drop from "get latest" is not actually happening. There is no error reported.
We have tested this with two of us several times. Whom ever does the drop pro...
Confirmed. We are getting the "drop" on the "Get Latest", and after the "Get Latest" button is pressed, all shows clear, however, the SP or FN still exists. Tried this with several different FN/SP. / comments
Confirmed. We are getting the "drop" on the "Get Latest", and after the "Get Latest" button is pressed, all shows clear, however, the SP or FN still exists. Tried this with several different FN/SP.