Go statement doesn't recognize numerical execution count parameter #42
Assignees
Labels
Enhancement
Request for new features or functionality
Comments
|
I think this is a bug,since it works on ssms and doesn't work only on ops studio |
|
@sateeshmachineni this is a SSMS's feature but not T-SQL feature, hence a suggestion :) |
|
I may have an implementation for this, will update if correct. |
|
The fix works - will have this out for review shortly. Thanks for the feedback! The feature will be available in the next public release (and will also be supported in the VSCode-MSSQL extension). |
This was referenced Nov 22, 2017
Closed
anthonydresser
pushed a commit
that referenced
this issue
Dec 18, 2017
* Initial VS Code port from release/1.8 to commit 172f9b4beaf684d6e39bfed4132144d5a4012ff1 * Remove unused UI elements. * Remove unused extensions from VS Code port. * Initial vscode-mssql integration * Merge build break fixes. (#2) * Remove vscode-api extension tests due to build break * Set execute bit on .sh files * Stage changes to move to different machine * Clean-up Windows build * Fix build scripts on Linux * Reset to VS Code 1.8 * Remove vscode-api-tests which break the build * Remove unused UI elements. * Add initial vscode-mssql integration * Update product.json * Integrate initial SQL UI placeholders. * Remove vscode-mssql submodule * Add vscode-mssql extension * Misc UI updates. (#3) * Reorder activity bar items * Update the menu items to remove editor-specific items * Clean-up connection viewlet * Add connectionList renderer * Minor updates * Merge initial query edit changes (#4) * Wire up queryEditor window with blank content * Remove unused extensions * Fix .vscode launch file * Merge dataprotocol initial integration (#15) * Add Registered Server menu item * Update registered servers icon * Initial mssql extension placeholder * Rename files in mssql extension. * Port dataprotocol code repo * Try to get dataprotocol building * Fix build break in dataprotocol * Include files to fix break * Fix npm postinstall order (#16) * Add json files to fix npm modules * Hook-up trivial Node IPC messages as simple example (#19) * Initial Data Management Node IPC classes * Update product.json to carbon code name * Wire up simple node IPC connection events * Update README.md * Hook up vscode-mssql extension into carbon. (#24) * List connections command * Remove unneeded extensions * Move out vscode-mssql extension * Move changes to other machine * Port over more vscode-mssql in carbon * Move changes to other machine * Hook-up connection and intellisense notifications * Hook up connection events into DMP (#34) * Shelve to move to other machien * Move back to other machine * Link to vscode.d.ts * Hook in a basic connection callback in DMP * Improve connection event routing hookups (#35) * Staging of changes to wire up connection info request. * Improve connection event routing hookups * Wire up list connection events through DMP client (#38) * Initial docfx content (#40) * Initial docfx content * Some additional design notes * Update documentation (#41) * Additional documentation for Connection feature area. * Update documentation content.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to Reproduce:
Execute and it will only run once
Run the same query within SSMS or SQLCMD and it will execute multiple times.
This probably isn't a production type feature but handy with demonstrations, automation, and development work to provide a multi execution of a single batch
I know that this is not strictly a TSQL language but has been in our other client tools and very useful in the field.
The text was updated successfully, but these errors were encountered: