Assessment workspace

Upload collector evidence and generate the independent decision.

The automated analysis returns a clear result for each server (optimized, as is, or more data needed), the checks behind it, and exportable evidence.

Start the assessment

Download Collector

One download, one starter script -- it asks which evidence to collect and walks you through it, then you upload the result below.

Download Collector

How long to collect: Run the SQL Server collector for 7 days. For a server with more than about 40 databases, or to cover more than 7 days, use the CloudWatch collector. Under 2 days, Savio asks for a new collection; 3 to 7 days gives only a preliminary result. Each upload uses one assessment run. If every server was collected for less than 2 days, the upload does not use an assessment run.

Run the assessment

Upload the completed collector package

The analysis returns the optimization outcome, confidence, evidence checks, and exportable business evidence.

Before you run the collector

SQL Server collector (most complete evidence)

  • A Windows computer that can connect to your RDS SQL Server endpoint (the security group must allow it).
  • Windows PowerShell with the SqlServer module. If it is missing, the collector shows the one-line command to install it.
  • An empty database on the server for the collector's temporary tables (the collector asks for its name).
  • A SQL login that can create tables in that database and create a SQL Server Agent job. Preferably use the RDS master (admin) login, which can do both.
  • The collection runs as a SQL Server Agent job on the server. Check its progress with Refresh status, export when it finishes, then select Cleanup to remove the collector's tables and job. Logins and passwords are never exported.

CloudWatch collector (if you prefer not to give SQL Server access)

  • A Windows computer with AWS CLI v2 set up (aws configure) using a read-only AWS identity.
  • Read-only AWS permissions. The exact list is in SavioCW_README.txt in the collector download. Enhanced Monitoring and Database Insights add detail where enabled.
  • Your AWS credentials stay on your computer and are never sent to Savio.

Savio does not collect, save or use your database passwords. The collector uses them only on your computer and never puts them in the files you upload.

Not sure which one to use? See what each collector can and cannot see.

Start the collector by double-clicking SavioCollector.bat. If Windows shows a "Security warning" for a collector script, choose R (Run once): it is Savio's own collector. If your company blocks scripts that are not digitally signed, ask your IT team to allow the collector folder.

Safeguards

  • Cost Optimization diagnostics must be explicitly enabled in the Savio Collector.
  • Passwords are collector-only and must not appear in normalized reports.
  • Results show every workload check and, for servers that can move, the saving in dollars and percent at AWS's public on-demand list price.
  • Optimized targets must pass memory, instance IOPS, instance throughput, tempdb, edition, orderability, and independent verification checks.
  • Compute and storage provisioning are assessed separately. Storage changes remain planning guidance only.

Need help? Email [email protected]. Never send database passwords or AWS credentials.