Every query to your SQL Server passes through Quentra first

SELECT *
FROM Orders
WHERE YEAR(OrderDate) = 2026;

Quentra does not step in; the query goes to SQL Server untouched.

SELECT TOP 10 ProductName, Price
FROM Catalog.Products
WHERE IsActive = 1
ORDER BY PopularityScore DESC;

The query reaches the database and the answer is cached.

Nested Loops (Inner Join)
  ├─ Index Seek  · Customers
  └─ Table Scan  · Orders  ← 94%

The plan is split into operators and cost is attributed.

Missing-index suggestions · 412
Queries that actually run · 38

Not SQL Server's raw suggestions; the queries that actually run on your system.

SELECT *
FROM Users
WHERE name = 'admin' OR 1=1 --';

The condition is always true; the comment discards the rest.

LOGIN user='sa'    ✗
LOGIN user='admin' ✗
LOGIN user='test'  ✗
… 200 attempts / 40 s

Repeated failed logins from a single source in a short window.

SELECT FullName, NationalId, Phone
FROM Customers;

Quentra does not touch the query; SQL Server returns the result as usual.

14:32:07  app_user  SELECT … Orders   1,240 ms
14:32:07  bi_user   SELECT … Invoices     38 ms

Who queried what, when, and how long it took.

No rule to switch on; logging runs by default.

Why did the system slow down last night?

No SQL required.

Which metric, which range, who receives it.