Activity overview
Latest activity by PhilJax
Error 918: Failed to retrieve restore history id.
Hi, Whilst restoring some database backups (using the partial restore method), I encounter an issue whilst restoring the differential database backups: -
Error 918: Failed to retrieve restore histo...
Error code reference documentation
Hi,
I may have found a slight issue with the error code reference documentation. In the documentation, SQL Backup error code 560 is listed as error 'File does not exist', however; the extended stor...
No problem, I'm happy to help [image]
There is 1 more thing that I noticed whilst investigating this, when all instances had been deleted from monitoring, I noticed that SQL Monitor continued to add data to the _UnstableSample tables. Is this behaviour by design?
Thanks,
PhilJax / comments
No problem, I'm happy to help
There is 1 more thing that I noticed whilst investigating this, when all instances had been deleted from monitoring, I noticed that SQL Monitor continued to add data...
Hi,
The earliest collection date in the table is 2010-12-01 10:33:37.207. / comments
Hi,
The earliest collection date in the table is 2010-12-01 10:33:37.207.
Hi, I'm currently using version 2.1 (the newest version available for download).
After having a look at the code used to delete the records, I can see why 3/4 days would not be sufficient to clear down some of these tables after deleting the instances from monitoring (delete top (50000)).
The row count for the table I am looking at is 199,311,349 (Cluster_SqlServer_Sqlprocess_UnstableSamples).
The data purge settings were set to 1 week. / comments
Hi, I'm currently using version 2.1 (the newest version available for download).
After having a look at the code used to delete the records, I can see why 3/4 days would not be sufficient to clear ...
Data Purge Issue
Hi, the data purge options in SQL Monitor do not seem to do exactly as stated. Although the data is deleted for the instances and alerts etc, it does not seem to clean up the tables whose name ends...
P.S. Instance names all appear to be correct for the registry keys. / comments
P.S. Instance names all appear to be correct for the registry keys.
Hi RBA,
Sorry, yes, you are correct. I made an assumption based on the error in the cluster log. One thing I have noticed is that for some clusters, the data path key points to the clustered drive and in others, it's a local path to the C drive. / comments
Hi RBA,
Sorry, yes, you are correct. I made an assumption based on the error in the cluster log. One thing I have noticed is that for some clusters, the data path key points to the clustered drive ...
I think I may know the cause of this, the RedGate registry keys are not specific to an instance of SQL Server, therefore running multiple clustered instances and/or active active clusters gets the cluster service very confused.
Having removed the registry keys from replication in 1 clustered instance and then attempting to remove it from the next instance either resulted in a message telling me that it wasn't there or when the dialog box was opened, no registry keys were present.
That's what I think it is based on my own experience so far and would probably explain why testing in an attempt to replicate the issue may have failed, the testing was attempted on 1 clustered instance of SQL Server rather than multiple instances. / comments
I think I may know the cause of this, the RedGate registry keys are not specific to an instance of SQL Server, therefore running multiple clustered instances and/or active active clusters gets the ...