Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
Danish-Norwegian, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
Data access failed because the .NET Framework routine is not marked with "DataAccessKind.Read" or "SystemDataAccessKind.Read". ...
Data access is not allowed in this context. Either the context is a function or method not marked with DataAccessKind.Read ...
Data associated with the key value, '%{name/}', was not used during training and because this, the value is not a valid key. ...
Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. ...
Data conversion failed while converting column "%1!s!" (%2!d!) to column "%3!s!" (%4!d!). The conversion returned status ...
Data could not be retrieved for the subreport, '{0}', located at: {1}. Data is only retrieved during the initial request ...
Data has changed since the Results pane was last retrieved. Do you want to save your changes now? (Optimistic Concurrency ...
Data in filegroup %1!s! is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup ...