Comments
Sort by recent activity
I have granted view definition to the role assigned to the login and it still fails. When the was that big sql injection scare, we revoked the select against sysobjects to the public to prevent unauthorized. I believe that is the issue, so I granted select to sysobjects to the role and it worked / comments
I have granted view definition to the role assigned to the login and it still fails. When the was that big sql injection scare, we revoked the select against sysobjects to the public to prevent una...
We found the issue. It appears that after applying the cu12 service pack, the machine was failed over. The other server was not running the 5.4.0.55 version. We suspect that the original redgate cluster upgrade did not work properly.
We are now running on version 5.4.0.55 / comments
We found the issue. It appears that after applying the cu12 service pack, the machine was failed over. The other server was not running the 5.4.0.55 version. We suspect that the original redgate cl...
Yes, that is what we thought. I guess we will have to wait for the next maintenance window. / comments
Yes, that is what we thought. I guess we will have to wait for the next maintenance window.
Upgraded from Version v5.3.0.178 to 5.4.0.55
The issue went away for 9 months, but has come back in the last week or so.
The only difference is we applied SP2 CU12 service pack to SQL 2005 this past december
Do we have any solutions for this problem?
:?: / comments
Upgraded from Version v5.3.0.178 to 5.4.0.55
The issue went away for 9 months, but has come back in the last week or so.
The only difference is we applied SP2 CU12 service pack to SQL 2005 this pas...
Yes, that is good to hear. But, how do you get rid of the processes that still show in sp_who2. They cannot be killed and I am trying to avoid restrting the sql server. / comments
Yes, that is good to hear. But, how do you get rid of the processes that still show in sp_who2. They cannot be killed and I am trying to avoid restrting the sql server.
We have also encountered the same issue. I recently created a job to email us when it has detected that a job has been running longer than the max time + 20% in the past week.
Upon implementation, I discovered two processes that are runnable. When I perform an dbcc inputbuffer on these tasks, they show up as the execute sqlbackup command. Both of these processes have been in the system for over 30 days.
I attempted to kill the process, but it did nothing, now it appears as killed/rolledback. I restarted both the sql agent and the redgate and neither one helped.
It looks like only the restarting of the server will be my last alternative which I will wait for some scheduled downtime. Does anybody have any ideas? / comments
We have also encountered the same issue. I recently created a job to email us when it has detected that a job has been running longer than the max time + 20% in the past week.
Upon implementation, ...
Version v5.3.0.178 same as previous post. I received version upgrade to 5.4.
My issues is with the processes that appear when you run sp_who2. They are not running, they can't be killed [it appears as killed\rollback]. / comments
Version v5.3.0.178 same as previous post. I received version upgrade to 5.4.
My issues is with the processes that appear when you run sp_who2. They are not running, they can't be killed [it appears...