Collectors

Which collector should I use?

Savio has two collectors. Both run on your own Windows computer, change nothing in your data, and produce a ZIP file that you upload. They see different things.

WhatSQL Server collectorCloudWatch collector
ReadsSQL Server directlyAWS only: RDS settings, CloudWatch, Enhanced Monitoring, Database Insights
You needEach server's master user login and password, and a small collection database on each serverAWS CLI v2 with a read-only AWS identity (the policy is in SavioCW_README.txt)
Creates on your serverOne SQL Agent job and its own tables in the collection databaseNothing
Days coveredThe days ahead. It collects for the length you choose: 7 days; for many databases or longer periods, use CloudWatchThe days already past: 14 by default, 30 at most. You can upload the same day
CPU and disk activityYesYes
MemorySQL Server's own memory readings and page life expectancyPage life expectancy from Database Insights, only where it is turned on and only for the days it keeps (7 by default). Without it, Savio does not lower memory
tempdbChecked against the smaller sizeShown for information only. CloudWatch does not report tempdb's size
Busiest databasesYesNo
Enterprise-to-Standard checkYesNo
RDS size and storage settingsFrom your server list (SavioServers.csv)Read from AWS
Your sign-in detailsNever exportedAWS credentials stay on your computer

Choose the SQL Server collector for the most complete result.

Choose the CloudWatch collector if you cannot give the collector access to SQL Server, or if you want a result from past days now.

What the SQL Server collector does on your server

What it creates

  • One SQL Server Agent job named SQL_IOCollection, which takes a reading every minute.
  • Its own tables, only in the collection database you give it. Nothing is added to your application databases.

What it reads

Only SQL Server's own system views, the same ones monitoring tools use: activity and memory counters including page life expectancy, processor use over time, memory use, disk activity for each database file, what SQL Server waits on, database names, file sizes and server settings, and the Enterprise features in use (for the Enterprise-to-Standard check).

What it never reads

Your application tables or rows, SQL text, query plans, Query Store or traces.

At the end

Export copies the readings into your files. Clean up deletes the collector's tables and the job.

The CloudWatch collector creates nothing on your servers and reads only from AWS.

Effect on your server

In our September 2026 test on Amazon RDS for SQL Server, the collector caused no measurable CPU or memory increase and only a small, expected increase in disk reads. The test application completed about 6.6% fewer transactions in most runs while the collector ran; we are still investigating why. The Security and data page has the full results and how to run a careful first collection.

Your database passwords stay with you

Savio does not collect, save or use your database passwords.

  • The collector uses them only on your computer, to connect to your servers.
  • They never go into the files you upload. Before the collector makes the ZIP file, it checks it and stops if a login or password is inside.
  • The collector's support log hides them.
  • Savio never asks you for a database password. You sign in to Savio with a link sent to your email.

When you have finished, delete the passwords from your server list.

Ready to collect?

Download the collector. It includes both the SQL Server and the CloudWatch collector.

Start Assessment