• About Me
  • #SQLHelp
  • SQLTools
  • AutoMon
  • jDBA
  • Tuning
  • Training
  • Oracle
  • Forum
  • Disclaimer and copyright
Sql server Blog Forum

Helping SQL server DBAs and Developers

  • About Me
  • #SQLHelp
  • SQLTools
  • AutoMon
  • jDBA
  • Tuning
  • Training
  • Oracle
  • Forum
  • Disclaimer and copyright
  • About Me
  • #SQLHelp
  • SQLTools
  • AutoMon
  • jDBA
  • Tuning
  • Training
  • Oracle
  • Forum
  • Disclaimer and copyright
  • DBA,  Performance

    Perfmon Data collection – Integrate SSRS with Perfmon – Dashboard performance of database graph using SSRS Collect perfMon and automate it load to SQL database and generate reports

    October 9, 2019

    DBA wants to collect metrics and analysis them and present them to management to get something done by using the data (to check performance issue, benchmark for migration etc) and it is all about data and metric nowadays. How to collect them and show as a presentation. Two parts are there: 1. You can setup Perfmon, T-SQL and use excel 2. Setup perfmon, T-SQL and configure SSRS. Tools needed: SSRS, Perfmon.msc, Relog.Exe, database engine, power shell & CMD. Steps: Create two notepad and save it any drive (performance.lst, server.lst) and one CMD file createlogs.cmd – The performance notepad will have counter details and server notepad will have serve name and…

    Read More
    Muthukkumaran Kaliyamoorthy 2 Comments

Search box

Categories

  • AlwaysON
  • AutoMon
  • Azure
  • Backup/Restore
  • Basics for freshers
  • DBA
  • Docker
  • DR/HA
  • Indexes
  • Internals
  • Junior DBA
  • Microsoft
  • Oracle
  • Performance
  • PowerShell
  • Questions
  • Scripts
  • SQL party
  • T-SQL
  • VLDB

Archives

Top SQL server blogs

  • Adam Machanic
  • Amit Banerjee
  • Brent Ozar
  • Gail Shaw
  • Grant Fritchey
  • Paul White
  • Pinal Dave
  • SimpleTalk
  • Sqlblog
  • SQLskills

Top Posts & Pages

  • AlwaysON database NOT SYNCHRONIZED and RECOVERY PENDING
    AlwaysON database NOT SYNCHRONIZED and RECOVERY PENDING
  • TempDB database is Full and Optimization
    TempDB database is Full and Optimization
  • Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. There is insufficient system memory in resource pool 'internal' to run this query.
    Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. There is insufficient system memory in resource pool 'internal' to run this query.
  • Login failed for [SQLSTATE 28000] (Error 18456) the step failed
    Login failed for [SQLSTATE 28000] (Error 18456) the step failed
  • AlwaysON database not synchronizing suspect mode
    AlwaysON database not synchronizing suspect mode
  • Test connection failed because of an error in initializing provider. Oracle client and networking components were not found
    Test connection failed because of an error in initializing provider. Oracle client and networking components were not found
  • The Cluster service failed to bring clustered service or application completely online or offline. One or more resources may be in a failed state.
    The Cluster service failed to bring clustered service or application completely online or offline. One or more resources may be in a failed state.
  • Patch Update apply and automate SQL server patch for multiple servers patching compliance by DBATools Powershell
    Patch Update apply and automate SQL server patch for multiple servers patching compliance by DBATools Powershell
  • How to solve the LSN mismatch issue in alwayson mirror SQL server The mirror database has insufficient transaction log data to preserve the log backup chain of the principal database.  This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database
    How to solve the LSN mismatch issue in alwayson mirror SQL server The mirror database has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database
  • Microsoft SQL Server Migration plan and steps
    Microsoft SQL Server Migration plan and steps
Savona Theme by Optima Themes