The print effect execution of the stored procedure? run into a problem, today didn't meet, yesterday the system lock table problems, check the stored procedure has been found that lock table stored procedure running not over, just added the print debugging, solve the problem of lock table after the print didn't remove the feel is not influence, today found stored procedure ran an error or have a problem, remove the print later no error??????? Is the print problem?

CodePudding user response:

If not to the output parameter or return an integer or well statement returns records set, then print won't have influence,
If there are three of the above said conditions, can use the SET NOCOUNT ON,

 
SET NOCOUNT ON 
- the order has been successfully completed, 
SET NOCOUNT OFF 
(100 rows affected) 

CodePudding user response:

reference 1/f, Yole response:

if not to the output parameter or return an integer or well statement returns recordset, then add the print won't have influence,
If there are three of the above said conditions, can use the SET NOCOUNT ON,

 
SET NOCOUNT ON 
- the order has been successfully completed, 
SET NOCOUNT OFF 
(100 rows affected) 

How does this work? On the stored procedure on it?

CodePudding user response:

refer to the second floor u014480075 response:

Quote: refer to 1st floor Yole response:

If not to the output parameter or return an integer or well statement returns records set, then print won't have influence,
If there are three of the above said conditions, can use the SET NOCOUNT ON,

 
SET NOCOUNT ON 
- the order has been successfully completed, 
SET NOCOUNT OFF 
(100 rows affected) 

How does this work? On the stored procedure on it?

Yes ~ process SET NOCOUNT ON start last in the SET NOCOUNT OFF
But the print the performance impact of feeble and micro ~