Скачать или смотреть Troubleshooting Commands Completed Successfully Message in SQL Server

Discover how to resolve the issue where SQL Server Management Studio shows only "Commands completed successfully" without displaying results from stored procedures.
---
This video is based on the question https://stackoverflow.com/q/68739223/ asked by the user 'jambajuice' ( https://stackoverflow.com/u/10487484/ ) and on the answer https://stackoverflow.com/a/68739258/ provided by the user 'Marko Ivkovic' ( https://stackoverflow.com/u/4594961/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Results are not showing, only says "Commands completed successfully"

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Commands Completed Successfully Message in SQL Server

When diving into the world of SQL Server and TSQL, encountering issues can be quite frustrating, especially for beginners. One common problem that users face is when executing a stored procedure, and instead of seeing the results, they only receive the message "Commands completed successfully." This guide aims to help you understand why this happens and how to effectively resolve it.

Understanding the Problem

You’ve built your first stored procedure, executed it, and while it seemed to run without error, you were left wondering why the expected results weren’t displayed. It’s a common issue, particularly when working with SQL Server Management Studio (SSMS). The key part of the message you receive is “Commands completed successfully,” which indicates that your command executed without any syntax errors. However, not seeing the results is a sign that something needs adjusting in your SQL code.

Analyzing the Code

When analyzing the code provided, you can see that a stored procedure is created to perform a SELECT operation. The usual steps were followed correctly: dropping the existing procedure (if any) and creating a new one. Here’s a quick rundown of your code:

[[See Video to Reveal this Text or Code Snippet]]

Problematic Areas

The absence of a GO keyword after the CREATE PROCEDURE block.

The execution command (EXECUTE dbo.practice) should be placed after its creation block in a separate batch.

The Solution: Adding the GO Keyword

The simple solution to this issue involves adding a GO statement right after the CREATE PROCEDURE block. By doing this, you tell SSMS to treat the commands before the GO as a complete batch. This is crucial because the execution context for the procedure is clearly defined only after it's been created.

Here’s the corrected version of your code:

[[See Video to Reveal this Text or Code Snippet]]

Step-by-Step Breakdown

Use the Correct Database: The USE ALEX_DB directive ensures that you are working with the correct database context.

Check for Existing Procedure: The check with IF OBJECT_ID ensures you don’t run into name conflicts when creating the procedure.

Creating the Procedure: Define what data your procedure will return.

Add the GO Statement: This crucial step tells SSMS to finish executing the create statement.

Execute the Procedure: Now that the procedure is properly created, executing it should yield the desired results displayed in the results grid.

Conclusion

By following the steps outlined above and adding a GO statement to your stored procedure code, you should be able to avoid the problem of receiving the “Commands completed successfully” message without results. Always remember that understanding the batch execution in SQL is fundamental for successful workflows in SQL Server Management Studio. Happy coding!