LogoLogo
ReleasesHomepageBlogSlack
3.0
3.0
  • Welcome
  • Concept
  • SQLWATCH Database
    • Requirements
      • Permissions
      • Performance Overhead
      • Storage Utilisation
    • Installation
      • Install with dbatools
      • Install with SqlPackage
      • Install with SSMS
      • Deploy from source code
      • Optional Components
      • Upgrade
      • Removal
      • Downgrade
    • Configuration
    • Known Issues
      • Collation conflict
      • Database drift
      • Login failed error when running disk logger
      • Deadlock when creating database
    • Notifications
      • Checks
      • Actions
      • Reports
      • How To
        • Add or modify check
        • Add or modify action
        • Add or modify report
      • Process Flow
    • Large Environments
  • Central Repository
    • Requirements
      • Performance overhead on the remote instance
      • Permissions
    • Installation
      • Removal
      • Upgrade
    • Configuration
    • Known Issues
  • Power BI Dashboard
    • Requirements
      • Permissions
    • Installation
    • Configuration
    • Known Issues
      • Power BI Load Errors
    • Performance
  • Grafana Dashboard
    • Requirements
    • Installation
    • Configuration
  • Azure Log Analytics Dashboard
    • Concept
    • Requirements
    • Installation
    • Configuration
  • Design Decision
    • Relations
    • Trend Tables
    • Data Types
      • Real Type
    • Primary Keys
    • Data Compression
    • Configuration Items
    • Using Apply instead of Join
  • Reference
    • Data-Tier Application Package
  • Integrations
    • Send notifications to Slack and Teams
    • dbachecks
  • FAQ
    • How do I check if SQLWATCH is running OK?
    • I am not seeing any data in Power BI
    • Can I modify default checks?
    • The app_log is growing fast
Powered by GitBook
On this page
  • SQL Database
  • Remote Data Collection
  • Linked Server
  • SQL Integration Service (SSIS)

Was this helpful?

  1. Central Repository

Requirements

Minimum requirements to host Central Repository

PreviousLarge EnvironmentsNextPerformance overhead on the remote instance

Last updated 5 years ago

Was this helpful?

SQL Database

Central Repository is just another SQLWATCH database, the same requirements and principles apply. Although any existing SQLWATCH database can become central repository at any point in time it is recommended to have it on a dedicated host due to the potential workload and performance overhead as it will be downloading data from the remote SQLWATCH databases into the central location.

The Central Repository Server will also be monitored locally, in the same way as any other SQLWATCH deployment.

Remote Data Collection

Data collection from remote instances can be done with SSIS or by using Linked Server.

Linked Server

No additional components are requied when using Linked Server.

SQL Integration Service (SSIS)

SSIS Package is used to download data from remote SQLWATCH databases.

SQL Server Integration Services 2012 and higher

The Central Repository database does not have to be hosted on the SSIS server, in other words, there can be dedicated SQL Server hosting the central repository and one or more dedicated SSIS Servers.

LogoSQL Server Integration Services - SQL Server Integration Services (SSIS)docsmsft