Skip to content

Conversation

@emil-eklund
Copy link
Contributor

Fixes spacing used in examples for the "-V" (severity) command.
Incorrect usage will cause the command to fail.

See earlier discussion: Azure/sql-action#235

Fixes spacing used in examples
@prmerger-automator
Copy link
Contributor

@emil-eklund : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 9a30ea2:

✅ Validation status: passed

File Status Preview URL Details
docs/tools/sqlcmd/sqlcmd-utility.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@emil-eklund
Copy link
Contributor Author

I think this passage is incorrect too, but I've not had the time to verify for all parameters:

Currently, sqlcmd doesn't require a space between the command-line option and the value. However, in a future release, a space may be required between the command-line option and the value.

@Court72
Copy link
Contributor

Court72 commented Jul 9, 2024

@dlevy-msft

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jul 9, 2024
@dlevy-msft
Copy link
Contributor

This appears to be an issue with the tool. Will need some time to investigate.

@emil-eklund
Copy link
Contributor Author

This appears to be an issue with the tool. Will need some time to investigate.

I agree. But I do also think the documentation should be updated if the following statement is true:

Currently, sqlcmd doesn't require a space between the command-line option and the value. However, in a future release, a space may be required between the command-line option and the value.

@rwestMSFT
Copy link
Contributor

@emil-eklund Thanks for your patience. We are updating the sqlcmd article in the next business day or so, with the following note.

Note

If you use the -i option followed by one or more additional parameters, you must use a space between the parameter and the value. This is a known issue in sqlcmd (Go).

You will still receive contributor credit.

@rwestMSFT rwestMSFT closed this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants