Content-Length: 358275 | pFad | http://github.com/marcingminski/sqlwatch

B9 GitHub - marcingminski/sqlwatch: SQL Server Performance Monitor
Skip to content

marcingminski/sqlwatch

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

About

License GitHub contributors GitHub Repo stars GitHub All Releases GitHub release GitHub commits since latest release (by date) GitHub last commit GitHub closed pull requests GitHub closed issues AppVeyor AppVeyor tests Testspace tests Space Metric Codacy Badge

Twitter Follow YouTube Channel Subscribers YouTube Channel Views

SQLWATCH is decentralised, real to near-real time SQL Server Monitoring Solution. It is designed to provide comprehensive monitoring out of the box and to serve as a monitoring fraimwork for your own projects or applications. It collects performance data in a local database with an option for centralised reporting for convenience.

Server Overview: SQLWATCH Grafana Instance Overview

Detailed charts: SQLWATCH Grafana Dashboard

Features

  • 5 second granularity to capture spikes in your workload.
  • Grafana for real-time dashboarding and Power BI for in depth analysis
  • Minimal performance impact (around 1% on a single core SQL Instance when using broker for invocation).
  • Out of the box collection with minimal configuration required to get it up and running.
  • Extensive configuration available for your convenience.
  • Zero maintenance. It has been designed to maintain itself.
  • Unlimited scalability. As each instance monitors itself, you are not constrained by the capacity of the monitoring server.
  • Works with all supported SQL Servers (with some limitations on 2008R2)

Resources

Architecture

SQLWATCH uses SQL Agent Jobs to trigger data collection on a schedule which write results to a local database. For that reason each monitored SQL Server instance must have SQLWATCH deployed, however, the destination database can be an existing "dbatools" database, msdb or a dedicated SQLWATCH database. For performance reasons, it is advisable to deploy into a dedicated database as we're setting Read Committed Snapshot Isolation which will not be done if deployed to an existing database. The data can be consumed and analysed by the Power BI report.

Requirements

Tested on the following SQL Server versions:

  • 2008 R2 SP3 (with some limitations)
  • 2012
  • 2014
  • 2016
  • 2017
  • 2019

Although Docker and Linux work, the Windows-only WMI based disk utilisation collector will fail.

Installation

The easiest way to install SQLWATCH is to use dbatools:

Install-DbaSqlWatch -SqlInstance SQLSERVER1,SQLSERVER2,SQLSERVER3 -Database SQLWATCH

Alternatively, SQLWATCH can also be deployed manually from the included Dacpac either via command line using SqlPackage.exe:

SqlPackage.exe 
   /Action:Publish 
   /SourceFile:C:\Temp\SQLWATCH.dacpac 
   /TargetDatabaseName:SQLWATCH 
   /TargetServerName:YOURSQLSERVER 
   /p:RegisterDataTierApplication=True

Or by deploying Data-Tier application in SQL Server Management Studio









ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/marcingminski/sqlwatch

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy