How can we help you today? How can we help you today?
Dan B
Activity overview Badges (0) Posts (0) Comments (287)

Comments

Sort by recent activity
Hi jchorlton, Thanks very much for your post in the Redgate forums. I have let the Product Manager know about this post to further its views within Redgate. / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. UserVoice Post: Save Analysis Favorites!
Hi jchorlton, Thanks very much for your post in the Redgate forums. I have let the Product Manager know about this post to further its views within Redgate.
0 votes
Jolin, Thanks for posting on the Redgate forums. The link in your post is to the new SQL monitor 5 documentation due out for release shortly. Here is a link to the SQL Monitor 4 page. http://documentation.red-gate.com/display/SM4/Adding+servers+to+monitor You should be able to try [clustername][standaloneinstancename] The integration isn't going to be as good as the new V5 though as a lot of work has gone into upgrading this. Let me know if you still can't get the standalone instance added. / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. How to show standalone instance on cluster node
Jolin, Thanks for posting on the Redgate forums. The link in your post is to the new SQL monitor 5 documentation due out for release shortly. Here is a link to the SQL Monitor 4 page. http://docume...
0 votes
RofL, Thanks for using the Redgate forums. I have attached a script which might get you some of what you want. You can add a line at the bottom WHERE Cluster_SqlServer_Error_Text LIKE '%objectname%' to filter only the lines containing the object name. The object names are held within the full message so it would require further manipulation to get what you need I think. Let me know if you need any further assistance. USE RedGateMonitor GO WITH CteDeadlockHeads AS (SELECT TOP 100000 IdCollectionDate , Cluster_SqlServer_Error_ProcessInfo , CollectionDate , Cluster_Name , Cluster_SqlServer_Name , Cluster_SqlServer_Error_LogDate FROM [data].[Cluster_SqlServer_Error_Instances_View] WHERE Cluster_SqlServer_Error_Text LIKE 'deadlock-list%' OR Cluster_SqlServer_Error_Text LIKE 'Deadlock encountered%') SELECT b.Id , b.IdCollectionDate , b.Cluster_SqlServer_Error_ProcessInfo , b.Cluster_SqlServer_Error_Text , b.CollectionDate , b.CollectionDate_DateTime , b.Cluster_Name , b.Cluster_SqlServer_Name , b.Cluster_SqlServer_Error_LogDate , b.Cluster_SqlServer_Error_LogDate_DateTime , b.Cluster_SqlServer_Error_SequenceNumber FROM CteDeadlockHeads a INNER JOIN [data].[Cluster_SqlServer_Error_Instances_View] b ON b.Cluster_Name = a.Cluster_Name AND b.Cluster_SqlServer_Error_LogDate = a.Cluster_SqlServer_Error_LogDate AND b.IdCollectionDate = a.IdCollectionDate AND b.Cluster_SqlServer_Error_ProcessInfo = a.Cluster_SqlServer_Error_ProcessInfo / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Find Objects with Most deadlocks
RofL, Thanks for using the Redgate forums. I have attached a script which might get you some of what you want. You can add a line at the bottom WHERE Cluster_SqlServer_Error_Text LIKE '%objectname%...
0 votes
PDinCA, Thanks for your forum post. The current release of SQL Backup (v7.7) should work with CTP 2.4. Are you attempting to install across the network? Are you able to run the server component installer on the machine locally? To do a local install navigate to the install directory of SQL Backup where the UI is installed and copy the file SQBServerSetup.exe onto the server running SQL. You can then run this on the server where needed. Let me know how you get on with this and whether you are still having issues / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL2016CTP Support?
PDinCA, Thanks for your forum post. The current release of SQL Backup (v7.7) should work with CTP 2.4. Are you attempting to install across the network? Are you able to run the server component in...
0 votes
DJ Wilson, Thanks for contacting Redgate. You can find further information on your specific SQL Monitor error at the following link. http://documentation.red-gate.com/display/SM4/Monitoring+status+explained As for the general uptime, this would really depend on the company and any contract's in place. When I was DBA'ing we had contracts with customers specifying 99.989% uptime. This would give you a 45-minute maintenance window each month. So you're probably correct that you want to be near 100% without maintenance or disaster recovery. If you need further assistance diagnosing the SQL monitor issues please let me know. / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. "Machine unreachable" Alerts
DJ Wilson, Thanks for contacting Redgate. You can find further information on your specific SQL Monitor error at the following link. http://documentation.red-gate.com/display/SM4/Monitoring+status+...
0 votes
wullsy, I believe what you require can be implemented using the below script. Please try it out and let me know if you need anything further. The uptime is based on SQL Monitor's ability to connect to the monitored entity, and also to collect data. The percentage and downtime measures are based on the times that SQL Monitor was attempting to connect, so the percentages and minutes will be accurate, but only cover the times SQL Monitor was instructed to monitor the server. Eg: You monitor an instance for an hour, and it is online throughout this hour. If you then ask: "What is the uptime for this instance for the last week?", this script will report 100%, with 0 minutes uptime, even if there has been downtime the day before. DECLARE @startDateUtc BIGINT; DECLARE @endDateUtc BIGINT; -- SET THESE THINGS -- SET @startDateUtc = utils.DateTimeToTicks('2014-01-06'); SET @endDateUtc = utils.DateTimeToTicks('2014-01-07'); -- END SET THESE THINGS -- ;WITH CteData AS ( SELECT 'Cluster' [Level] , ROW_NUMBER() OVER (PARTITION BY Id ORDER BY CollectionDate ASC) [row], [Id] , [Cluster_Name] [Cluster Name], '' [Node/SQL Server Instance Name], [Cluster_MonitoredEntityState] [MonitoredEntityState], [Cluster_MonitoringStatusCategory] [MonitoringStatusCategory] , [CollectionDate] FROM [data].[Cluster_StableSamples_View] UNION ALL SELECT 'Node' , ROW_NUMBER() OVER (PARTITION BY Id ORDER BY CollectionDate ASC) [row], Id , Cluster_Name , Cluster_Machine_Name , Cluster_Machine_MonitoredEntityState , Cluster_Machine_MonitoringStatusCategory , CollectionDate FROM [data].[Cluster_Machine_StableSamples_View] WHERE Cluster_Machine_Name <> '' UNION ALL SELECT 'SqlServer' , ROW_NUMBER() OVER (PARTITION BY Id ORDER BY CollectionDate ASC) [row], Id , Cluster_Name , Cluster_SqlServer_Name , Cluster_SqlServer_MonitoredEntityState , Cluster_SqlServer_MonitoringStatusCategory , CollectionDate FROM data.Cluster_SqlServer_StableSamples_View ), CteTicks AS ( SELECT aft.[Id] , aft.[Level] , aft.[Cluster Name] , aft.[Node/SQL Server Instance Name] , CASE WHEN aft.CollectionDate < @startDateUtc THEN 0 WHEN aft.CollectionDate < @endDateUtc AND bef.CollectionDate IS NULL THEN aft.CollectionDate - @startDateUtc WHEN aft.CollectionDate < @endDateUtc AND bef.CollectionDate < @startDateUtc THEN aft.CollectionDate - @startDateUtc WHEN aft.CollectionDate < @endDateUtc THEN aft.CollectionDate - bef.CollectionDate WHEN bef.CollectionDate IS NULL THEN @endDateUtc - @startDateUtc WHEN bef.CollectionDate < @startDateUtc THEN @endDateUtc - @startDateUtc WHEN bef.CollectionDate < @endDateUtc THEN @endDateUtc - bef.CollectionDate ELSE 0 END [ticks], aft.[MonitoredEntityState] , aft.[MonitoringStatusCategory] FROM CteData aft LEFT OUTER JOIN CteData bef ON aft.Id = bef.Id AND aft.row = bef.row + 1 ) SELECT [Level], [Cluster Name], [Node/SQL Server Instance Name] , 100.0 * SUM(CASE WHEN [MonitoringStatusCategory] IS NULL OR [MonitoringStatusCategory] < 300 THEN ticks ELSE 0 END)/SUM(ticks) [% Uptime], 1.0/600000000 * SUM(CASE WHEN [MonitoringStatusCategory] IS NOT NULL AND [MonitoringStatusCategory] >= 300 THEN ticks ELSE 0 END) [Monitored Downtime (minutes)] FROM CteTicks WHERE [MonitoredEntityState] = 3 GROUP BY Id, [Level], [Cluster Name], [Node/SQL Server Instance Name] HAVING SUM(ticks) > 0 ORDER BY [Cluster Name], [Level], [Node/SQL Server Instance Name] / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Query for SQL uptime?
wullsy, I believe what you require can be implemented using the below script. Please try it out and let me know if you need anything further. The uptime is based on SQL Monitor's ability to connect...
0 votes
wullsy, Did you edit the date range at the top of the script? -- SET THESE THINGS -- SET @startDateUtc = utils.DateTimeToTicks('2014-01-06'); SET @endDateUtc = utils.DateTimeToTicks('2014-01-07'); -- END SET THESE THINGS -- This should be edited to show the date range you would like to report on. This should be accurate to 5 seconds. Let me know how you get on when you try this. Regards Dan Bainbridge / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Query for SQL uptime?
wullsy, Did you edit the date range at the top of the script?-- SET THESE THINGS -- SET @startDateUtc = utils.DateTimeToTicks('2014-01-06'); SET @endDateUtc = utils.DateTimeToTicks('2014-01-07'); -...
0 votes
Hi RVO, I have passed on some troubleshooting steps via email. Please let me know if you don't receive this. / comments
  1. Community
  2. SQL Search
  3. MDAC components MSI Error: 1603
Hi RVO, I have passed on some troubleshooting steps via email. Please let me know if you don't receive this.
0 votes
Hi mlukas, This issue has been resolved since version 3.1.2.765 which was released this week. This can be downloaded from the below link ftp://support.red-gate.com/patches/SQLD ... .2.765.zip / comments
  1. Community
  2. SQL Doc
  3. Problems with formatting
Hi mlukas, This issue has been resolved since version 3.1.2.765 which was released this week. This can be downloaded from the below link ftp://support.red-gate.com/patches/SQLD ... .2.765.zip
0 votes
Hi Blambers, Whilst we did create a feature request for this we have taken the decision not add this feature to the product. Work is continuing on issues but the decision has been made that this issue is not a necessary addition at this time and there isn't enough demand to add it.The feature request remains open so this can be reviewed in the future. / comments
  1. Community
  2. SQL Dependency Tracker
  3. dependencies for a table created within a stored procedure
Hi Blambers,Whilst we did create a feature request for this we have taken the decision not add this feature to the product. Work is continuing on issues but the decision has been made that this iss...
0 votes
Total activity
485
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
198