Atitit. Troubleshooting---A critical error has occurred with the current command. Any results that might result in SQL Server 2008 should be discarded

Atitit. Trouble Shooting ---  A critical error has occurred with the current command. You should discard any results that might result from SQL Server

1. Phenomenon 1

2. Reason :: SQL Server bug or limit , query when using too much resources than the operating system / Firewall / security software restrictions ... 2

2.1. Firewall/ security software reason: automatic shutdown of long-time connections and resources for many connections .. 2

2.2. The number of concurrent connections exceeds its load capacity, and the server will drop Some of the connections ;2

3. Solution :: 2

3.1. Patching SP 2

3.2. Use top n/where to reduce the number of queries (attialx verify OK) 2

3.3. Improve the Computer Configuration ( recommended ,, verify OK) 2

3.4. Query field Add index 2

3.5. Reduce The field query for select Large . only Select small Field 2

3.6. Modifying the length of a field may be the result of this : 3

3.7. strSQL and Param are too many to cause errors. 3

3.8. No detailed data types are specified in the calling stored procedure . ( according Google the result says SP4 just appeared. , I don't know about that. )3

4. Reference 3

1. Phenomena

this error when executing an SQL statement: Code Korean manager blackheads are all in one ..

Resolve "A critical error has occurred in the current command. Any results that may result should be discarded. "The question

A transport-level error occurred while receiving results from the server. (provider: named pipe provider , error:0- No process on the other end of the pipeline.) )

A critical error has occurred with the current command. Any results that may be produced should be discarded

There are often conn Auto-closing things ... . Socket CLOSE:

Org.springframework.transaction.TransactionSystemException:Could not roll back Hibernate transaction; Nested exception is Org.hibernate.TransactionException:rollback failed

Org.springframework.transaction.CannotCreateTransactionException:Could not open Hibernate Session for transaction; Nested exception is Org.hibernate.service.UnknownServiceException:Unknown service requested [ Org.hibernate.service.jdbc.connections.spi.ConnectionProvider]

caused by:com.microsoft.sqlserver.jdbc.SQLServerException:Connection reset by Peer:socket write error

Caused by:com.microsoft.sqlserver.jdbc.SQLServerException: the connection is closed.

Org.springframework.transaction.TransactionSystemException:Could not commit Hibernate transaction; Nested exception is Org.hibernate.TransactionException:commit failed

Author:: Old Wow's paw attilax Ayron, email:[email protected]

Reprint please indicate source: Http://blog.csdn.net/attilax

2.cause :: SQL Server bug or limit , query when using too much resources than the operating system / Firewall/Security softwareThe restrictions ...

Data only 75w, the time of the query is also this error .....

Probably query when the memory use too many ...

But MySQL has no problem with the same amount of data on the same computer .

2.1. Firewall/Security software reason: Automatic shutdown of long-time connection andMultiple connections for resources : 2.2. The number of concurrent connections exceeds its capacity, and the server will drop some of the connections;

3. The solution:: 3.1. Patching sp3.2. Use top n/where to reduce the number of queries (Attialx verify OK) 3.3. Upgrade the Computer Configuration (recommended, verify OK) 3.4. Query field Add index 3.5. Reduce the field query for select Large. Select only the small field 3.6. Modifying the length of a field may be the result of this:

It is estimated that the length of the article is too long to be caused, so find the code db. Addinparameter (DbCommand, "Content", dbtype.ansistring, model. Content);

Change it to

Db. Addinparameter (DbCommand, "Content", dbtype.string, model. Content);

3.7. strSQL and Param are too many to cause errors.

The Param for Loop is an error 2092 the first time .

3.8. No detailed data types are specified in the calling stored procedure. (according to the Google results said hit SP4 only appeared, this does not know)

4. Reference

2014/11/25 11:23 22,212 Exception ask: The current command has a serious error. Any results that may be produced should be discarded . htm

2014/11/25 11:20 113,357 The current command has a fatal error. Any results that may be produced should be discarded . htm

2014/11/25 11:23 12,669 resolved "A critical error occurred in the current command. Any results that may result should be discarded. "The problem -Sam Lin- Blog Park . htm

2014/11/25 11:20 42,875 Fix the problem the current command has a fatal error. Should discard any possible results -wthorse 's Column - Blog channel -CSDN.NET.htm

Atitit. Troubleshooting---A critical error has occurred with the current command. Any results that might result in SQL Server 2008 should be discarded