Update T-SQL to be better formatted and also output better-formatted code itself #1573
Conversation
much T-SQL formatting, both of the code for the 2 stored procedures, and for the T-SQL code they output, to make the resulting login scripts as readable as possible for end-users and SQL Server Admins.
…ns-passwords-between-instances.md Update transfer-logins-passwords-between-instances.md
|
#sign-off |
|
@microsoft-github-policy-service agree |
|
@MisterZeus : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit c5e7ded:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/sql/database-engine/security/transfer-logins-passwords-between-instances.md | Details |
support/sql/database-engine/security/transfer-logins-passwords-between-instances.md
- Line 384, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Swap tabs for 4 spaces as used in original code, unindent Note block as it messed up MSoft's auto format checks.
|
Learn Build status updates of commit 1f82489: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
fix code to work for sysname (a.k.a. nvarchar(128)) logins
|
Learn Build status updates of commit b7c5ff3: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit 18b89dd: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit 8daba47: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit b8c06af: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit fc99b2c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
merge this article as per tech reviewer. |
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:
We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.
After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.