能否限制SQL Server仅执行选中代码或执行前弹出确认提示？

Oh man, I feel your pain—accidentally running an entire script and dropping tables is the worst kind of oops moment. The good news is you absolutely can tweak your setup to prevent this from happening again. Let’s cover both your requested solutions:

Option 1: Force SSMS to Only Execute Selected Code (No Accidental Full Script Runs) #

By default, SSMS runs the entire query window if you don’t have any text selected when hitting Execute (F5/Ctrl+E). You can change this so it only ever runs selected text—if nothing’s selected, it’ll throw a warning instead of executing everything:

• Open SSMS and go to Tools → Options
• Expand Environment → Keyboard in the left pane
• In the "Show commands containing" box, type Query.Execute
• Select the existing shortcuts (F5 and Ctrl+E) for Query.Execute and click Remove
• Now search for Query.ExecuteSelection in the same command list
• Highlight Query.ExecuteSelection, click Press shortcut keys, hit F5 (and/or Ctrl+E), then click Assign
• Click OK to save changes

From now on, pressing F5/Ctrl+E will only run the code you’ve highlighted. If you forget to select anything, SSMS will show a "No text is selected" error instead of executing the entire script.

Option 2: Add a Confirmation Prompt Before Execution #

If you still want the option to run full scripts but want a safety check first, you can create a custom macro in SSMS that prompts for confirmation:

• Go to Tools → Macros → Record Macro
• Name your macro something like ExecuteWithConfirmation and click Start Recording
• Immediately go to Tools → Macros → Stop Recording (we’ll edit the macro manually instead of recording actions)
• Open the macro editor via Tools → Macros → Macros IDE
• Replace the default macro code with this:

Sub ExecuteWithConfirmation()
    Dim userChoice As Integer
    userChoice = MsgBox("Are you sure you want to run this query?", vbYesNo, "Confirm Execution")
    If userChoice = vbYes Then
        DTE.ExecuteCommand("Query.Execute")
    End If
End Sub

• Save the macro, then go back to Tools → Options → Environment → Keyboard
• Search for Macros.MyMacros.ExecuteWithConfirmation (or whatever path your macro is under)
• Assign it to F5/Ctrl+E (replacing the default Query.Execute shortcuts)
• Click OK

Now every time you hit Execute, a pop-up will ask you to confirm before running the code—no more accidental full script executions.

Bonus Pro Tip #

Even with these safeguards, it’s smart to get in the habit of:

• Using GO to split your script into logical batches (so you can run sections one at a time)
• Taking quick backups of tables before running destructive commands:

  SELECT * INTO dbo.YourTable_Backup_20240520 FROM dbo.YourTable;
  

• Using transactions for risky operations (so you can roll back if something goes wrong):

  BEGIN TRANSACTION;
  -- Your DELETE/UPDATE/DROP code here
  -- If everything looks good: COMMIT TRANSACTION;
  -- If you need to undo: ROLLBACK TRANSACTION;
  

内容的提问来源于stack exchange，提问作者sachin01663