Sql-server – VDI errors but backups are successful

backupsql server

Our monitoring tools are showing SQLVDI errors, I think they're coming from the Event Viewer only. But the backups are showing successful in the SQL Server log files and we've successfully restored the backups.

The events look like this:

Event Log Module Status: 0 
The Last Record Number of the eventlog type that current event entry belongs to: 0 
# of duplicate events: 20.00 
Events Source: SQLVDI 
Category: None 
Event ID: 1 
User (If Applicable): N/A 
Event Description: SQLVDI: 
Loc=TriggerAbort. 
Desc=invoked. 
ErrorCode=(0). 
Process=3056. 
Thread=7460. 
Server. Instance=MSSQLSERVER. 
VD=Global\{08771828-3181-438B-A554-E02DA96EB3F2}7_SQLVDIMemoryName_0. 
Event Log Name: Application 
Event Log Type: error 
Event Log Date Time: 2018-05-11 09:04:06 
Notification Generated By: *0 Minute Delay - Priority 4 The Windows Event Log - SQL 2008 service transitioned from a Normal state to a Failed state at 2018-05-11 09:16:21 .

Can I safely stop monitoring SQLVDI errors?

Thank you for your time,

Thomas

Best Answer

This is just me, but no, I wouldn't ignore an event that said:

SQL 2008 service transitioned from a Normal state to a Failed state at 2018-05-11 09:16:21

That would be the kind of event I'd pay a little deeper attention to. If you Google for text involved in that error, you get KB articles like 2615182, suggesting that it's a Windows backup failing, not a SQL Server one.

Related Solutions

Sql-server – Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed

The error 9245 message appears to be directly connected to the 'The query notification dialog on conversation handle...' message in that SQL Server 2012 SP1 appears to only show that error a maximum of 10 times (with the same timestamp) in the error log, the rest are aggregated into a single error message:

During the last time interval 257 query notification errors were suppressed.

Which is preceded by the message:

Error: 9245, Severity: 16, State: 1.

Prior to SQL 2012 I do not believe the error notifications were aggregated at all, and did not result in a severity 16 error.

Sql-server – High write latancy in temp db

Rather than picking random metrics and trying to tune them, what you want to do is step back and ask SQL Server, "What have you been waiting on?"

My favorite way to do that is with the open source tool sp_Blitz (because, uh, I wrote it.) You can download it from FirstResponderKit.org, run the sp_Blitz.sql script to install it in the database of your choice.

When you run it with just plain old:

EXEC sp_Blitz @CheckServerInfo = 1

It gives you a prioritized list of issues to check out that will impact performance.

Around priority 240, you'll find a section on Wait Stats (around priority 240) that tell you what SQL Server has been waiting on. That's what I'd focus on first to figure out what metrics to examine more deeply. For example, if your biggest wait type is PAGEIOLATCH, that means you're waiting to read data pages from a data file - and the TempDB storage speed isn't really going to matter. (Don't worry, you don't have to know what those cryptic wait types mean - just click on the more-info links in the output.)

If you'd like help from the Stack folks interpreting the results, you can also run it like this:

EXEC sp_Blitz @OutputType = 'markdown'

That'll export the results in Markdown, a text format that you can copy/paste into your StackOverflow question.

Best Answer

Related Solutions

Sql-server – Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed

Sql-server – High write latancy in temp db

Related Question