SQL Server Errors or Failures from Error: 10056 to Error: 10103

SQLServerF1

 

Error: 10056, Severity: 16, The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
Error: 10057, Severity: 16, Cannot create the row. Would exceed the total number of active rows supported by the rowset.
Error: 10058, Severity: 16, The consumer cannot insert a new row before releasing previously-retrieved row handles.
Error: 10062, Severity: 16, The change was canceled by the provider during notification.
Error: 10063, Severity: 16, Could not convert the data value due to reasons other than sign mismatch or overflow.

Error: 10064, Severity: 16, The data value for one or more columns overflowed the type used by the provider.
Error: 10065, Severity: 16, The data violated the integrity constraints for one or more columns.
Error: 10066, Severity: 16, The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
Error: 10067, Severity: 16, The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
Error: 10068, Severity: 16, The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
Error: 10069, Severity: 16, The consumer could not delete the row. The insertion has been transmitted to the data source.

Error: 10081, Severity: 16, The rowset uses integrated indexes and there is no current index.
Error: 10085, Severity: 16, RestartPosition on the table was canceled during notification.
Error: 10086, Severity: 16, The table was built over a live data stream and the position cannot be restarted.
Error: 10087, Severity: 16, The provider did not release some of the existing rows.
Error: 10088, Severity: 16, The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed.
Error: 10100, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains the DISTINCT keyword. Consider removing DISTINCT from the view or not indexing the view. Alternatively, consider replacing DISTINCT with GROUP BY or COUNT_BIG(*) to simulate DISTINCT on grouping col
Error: 10101, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains the TOP or OFFSET keyword. Consider removing the TOP or OFFSET or not indexing the view.
Error: 10102, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view.
Error: 10103, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OPENQUERY, OPENROWSET, and OPENDATASOURCE.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *