Performance across all installations of your software.
Customer A reports a slow module in March, customer B in June, customer C in September. Is it the same problem? QX Fleet makes patterns across installations and releases visible so that development and support can start in the right place.
Don't investigate every installation individually. Improve once in the product and verify the effect everywhere.
Product, environment or individual case?
The first and most important question in support. QX Fleet provides an evidence-based starting hypothesis for it.
Many installations, the same pattern.
Indicates a shared product or code problem: involve development, fix once, verify everywhere.
Only under certain conditions.
Version, data volume or configuration make the difference: system requirements, guidelines or targeted adjustment.
One installation, one cause.
Investigate local data distribution, extensions, infrastructure or configuration in a targeted way.
Frequency is an indication, not proof. We check the cause against the evidence each time.
A product context for support, development and release management.
- Hotspots across installations
Which queries and paths of your product burden many customers at the same time? - Release assessment
What has improved or worsened in production with a new release? - Unstable query families
Where do plans change depending on the environment or the data? - Influence of the environment
SQL Server version, compatibility level, data volume and configuration in comparison. - Impact after rollout
Has the product improvement actually worked at the customers' sites?
The few measures that achieve the most in the product.
At a fixed cadence, our engineers review the product-wide picture with your support and development teams and prioritize a few effective product measures.
pattern New plan shape of a central procedure since the last release. spread Several installations, concentrated among large data volumes. class Environment-specific – hypothesis, still to be verified. open Influence of local extensions not ruled out. measure Coordinate a change in the product with development. check Compare the effect after rollout across the same installations.
Start small, decide on solid ground.
- 01
Understand the product
Architecture, critical paths and the support cases that take the most effort today.
- 02
Select installations
A few deliberately different installations, agreed with you and your customers.
- 03
One release cycle
Capture before and after, locally and traceably.
- 04
Joint evaluation
Patterns, classes and prioritized product measures.
- 05
Decide
Whether and in what form the product-wide view continues permanently.
Data & trust
The evidence is generated locally in the installations. Which data leaves them and which does not, we define together with you and your customers.
For your development
Performance Driven Development and Repository Driven Design help ensure that improvements stay in the code and new problems arise less often.
With PSG QX
The Query Store analysis that we also use in individual environments forms the basis of the product-wide view.
Short answers.
Is QX Fleet a SaaS platform?
QX Fleet is a guided program: our engineers work with PSG QX and your development team. Which parts run permanently as software with you or your customers, we define together.
How many installations does the start require?
A few deliberately different installations and one release cycle are enough to start. After that, you decide how to continue on the basis of real findings.
Which data leaves the installations?
We define this together with you and your customers. The evidence is generated locally; only what has been agreed for the product-wide view is brought together.
Does QX Fleet replace our support?
No. QX Fleet gives your support and development teams a shared product context. Responsibility for your product and your customers stays with you.
And individual critical customers?
PSG MX can additionally be agreed for them: continuous performance engineering for the specific installation, aligned with the product-wide view.
Let's take a look at your product.
In the first conversation, we clarify which support cases occupy you most and whether a product-wide view helps.