Search the Community

Showing results for tags 'sql'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • From LogicMonitor
    • Product Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 8 results

  1. Hello, I have recently seen a few of these tickets com across the board and was wondering if anyone would be able to give me a quick breakdown as to what this actually is and what the benefits would be to add this into the instance. SQL Server Troubleshooter-MSSQLSERVER Missing JDBC connection string. Manually add one to mssql.mssqlserver.mssql_url or check login informations exitCode A Microsoft SQL server has configuration problems or a logon error. MSSQLSERVER Missing JDBC connection string. Manually add one to mssql.mssqlserver.mssql_url or check login informations Thanks in Advance!
  2. A hack of the Microsoft_SQLServer_SystemJobs datasource that will alert you in the event that the available credentials cannot gather SQL System Jobs. In brief, it attempts the same SQL query that the original DataSource runs, but creates no instances on a success - in the event of a failure, it will generate one instance whose description will be the error message, and one datapoint will be applied that will trigger a warning alert after a couple of minutes. It'll look a bit like this where the SQL query fails: Note this *only* tries the query for System Jobs ('select * from msdb.dbo.sysjobs') and I created this only when I noticed we were getting SQL database data, but not system jobs, from some customer devices. v1.1.0: 33H94M
  3. We have a unique SQL setup that is using mirroring. How can we configure LM to not show the databases that are in (Mirror, Sychronized/Restoring...) mode as not 'down'.
  4. Hello all! I just recently created a monitor to track the amount of time in seconds the secondary replicas are behind the primary and I figured I would share my solution. This will display the span of time in which past transactions could be lost in the event of a fail over. This assumes the secondaries are asynchronous. We are using SQL 2016, I do not know if this will work on earlier versions of SQL. I created a datasource and set the "Applies to" to the server in question. I set the collector to "SCRIPT" and I set the datasource to multi-instance and enabled active discovery. I used JDBC as the discovery method and Instance List as the discovery type. The details are as follows: Connection String: jdbc:sqlserver://##HOSTNAME##;IntegratedSecurity=true; SQL Statement: (This query gets the name of each secondary replica) SELECT CS.replica_server_name FROM sys.availability_groups_cluster AS C INNER JOIN sys.dm_hadr_availability_replica_cluster_states AS CSON CS.group_id = C.group_id INNER JOIN sys.dm_hadr_availability_replica_states AS RS ON RS.replica_id = CS.replica_id WHERE RS.Role_desc <> 'PRIMARY' I wrote a script in Powershell that actually pulls the data that I need from the server itself. Powershell Script: [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | Out-Null $SqlServer = New-Object Microsoft.SqlServer.Management.Smo.Server("##HOSTNAME##") $SqlServer.AvailabilityGroups["your ag name here"].DatabaseReplicaStates | Where-Object {$_.IsLocal -eq $false -and $_.AvailabilityReplicaServerName -eq "##WILDVALUE##" -and $_.AvailabilityDatabaseName -eq "your server name here"} | Select -ExpandProperty EstimatedDataLoss In our environment there is only one database on the server that we are concerned with for tracking this information so I have not explored monitoring multiple databases. This method pulls the same data that is in the Estimated Data Loss(seconds) column in the Availability Groups dashboard in SQL Management Studio. In the event you wanted to track multiple databases on the secondaries, you will likely have to create a separate datasource for each secondary server you want to track. Additionally you would have to adjust the JDBC query to enumerate the databases on the server and the powershell script accordingly. I hope this helps someone. Thanks, Kyle
  5. Is there a good datasource out there to monitor the size on disk of a specific file or folder? I would love the Microsoft Exchange datasource (or other) to be able to deliver and track the total size of the database. Thoughts? Will
  6. Datasource with powershell script to monitor the Sync status of a specific database in a SQL 2016 High Availability instance. I noticed databases can fall into NotSynchronizing status on secondary nodes often without much alerting around it. The datasource monitors per database. If someone has a better way that will take in the status of all databases on the instance I am open to suggestions LM Locator: 6YD2C9
  7. Hi guys, hope you are doing well? This is my first post on here so forgive me if this is a double post ( have searched but didn't find anything ) Is there a way to monitor the free space inside a DB with logicmonitor? I am trying to use this rather than the disk space monitor to help us proactively manage the databases. Kind regards, Johan
  8. DESCRIPTION: This will alert you via LogicMonitor when a MS-SQL ‘job’ fails INSTRUCTIONS: Create a LogicMonitor “EventSource”. Named “SQL job failures” or similar. I suggest that you clone the default “SQL eventsource”. Set these settings: LogName = “Application” SourceName = “SQLSERVERAGENT” Level more urgent than “Information” Use Microsoft’s SQL Management Studio to set each job on each of your SQL servers so that when a job fails, it will write a message to the Windows Application event log (screenshot below) Right click on job and click “Properties” Click on “Notifications” on left pane Click on “Write to Windows event logs” checkbox and click “When the job fails” Test. I suggest you create a job with a bogus query and run it. Look in the Windows Event viewer and you should notice an EventID 208 at “warning” severity. Optional: In LogicMonitor you can create an Alert rule that notifies a specific person or team. Do this by selecting the datasource name of the eventSource you named above Note: I developed this and tested it with SQL version 2008-R2 but it will probably also work with newer versions. Below is screenshot showing how to create/clone a LogicMonitor EventSource Below shows how to set “Write to event log” on each SQL Job Below shows what the alert looks like in LogicMonitor.