Narrowing down slow performance in portier Vision on SQL Server

This guide covers installations that run on Microsoft SQL Server. If Vision runs on Firebird, skip section 3. Every other step stays the same.

Collect the data while the system is slow, not afterwards. A screenshot taken during normal operation tells us nothing.

1. System resources

Task Manager

• Open Task Manager with Ctrl + Shift + Esc.

• Watch CPU, memory and disk during the slow periods.

• Note spikes or sustained high usage, above all on the SQL Server process (sqlservr.exe) and the Vision client (PortierVision.exe).

Resource Monitor

• Open Resource Monitor from Task Manager, Performance tab, then Open Resource Monitor.

• Check the detailed resource usage there.

What to send us

• Screenshots or logs from Task Manager and Resource Monitor, captured during the slow period.

• Details of any process consuming an unusual amount.

2. Network

Ping

• Open Command Prompt.

• Start a continuous ping to the SQL Server: ping -t [SQLServerIPAddress]

• Note high latency and lost packets.

Traceroute

• Open Command Prompt.

• Run tracert [SQLServerIPAddress]. This shows the network hops and where a bottleneck sits.

What to send us

• The continuous ping result with latency and packet loss.

• The full traceroute output.

3. SQL Server

This section needs SQL Server Management Studio (SSMS).

Activity Monitor

• Open SSMS and connect to the SQL Server.

• Check CPU, memory and I/O waits in Activity Monitor.

• Look for blocking sessions and long-running queries.

Execution plan

• In the Query menu, switch on Include Actual Execution Plan (Ctrl + M).

• Run the slow query again and save the plan.

What to send us

• Screenshots or logs from Activity Monitor.

• Details of blocking sessions and long-running queries.

• The execution plans for the slow queries.

4. Event logs

Event Viewer

• Open Event Viewer and go to Windows Logs, then Application and System.

• Look for SQL Server errors and warnings.

What to send us

• The matching Event Viewer entries, above all errors and warnings about SQL Server or the network.

5. Performance counters

Performance Monitor (PerfMon)

• Open Performance Monitor. Type perfmon in the Run dialog.

• Set up a data collector set for these SQL Server counters:

• SQLServer:SQL Statistics

• SQLServer:Buffer Manager

• SQLServer:General Statistics

• Include Network Interface and PhysicalDisk.

What to send us

• Logs or screenshots of the counter data.

• Any spikes or sustained high values you noticed.

Summary

These five measurements usually let your IT team pin down the cause on their own. If they do not, send the collected data to our support team. We will work through it with you.