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

Can you remove the word "PolyBase" from the description section? It should just be "queries" not "PolyBase queries".

@EricBuMSFT was this intended to be documented? What's the CS that introduced these?

@EricBuMSFT - This looks good. You can sign-off by doing #sign-off.

@pmasl - Best to search internally if you are interested in the actual change. This was done long time back. The update was not done to the T-SQL reference but documented earlier in "What's New in BDC".

@uc-msft: I'm sorry - only the author of this article, @pmasl, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@EricBuMSFT: I'm sorry - only the author of this article, @pmasl, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

I can, sure. Why wasn't this change done in the private repo? FYI sql-docs-pr is the right place for MS folks to do docs changes.

#sign-off

@EricBuMSFT - as @pmasl mentioned, you should use the private repo for making edits in the future. thanks. (I've gone ahead and reviewed this and we'll merge it here).

here's some additional information about working in the private repo, for reference.

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.

After you review staging and fix all validation issues, you can tag an author for review or add the sign-off comment to let PR reviewers know that the updates are ready to be merged.

Read about authors working in the public repo for more information.

If you need help getting set up to work in the private repo, see How to get to the private repo. You can also take a look at the GitHub account setup page for additional details on making sure you're set up.

@Jak-MS SQL Server 2019 Big Data Cluster is a product name, hence capitalized, as seen here: https://docs.microsoft.com/en-us/sql/big-data-cluster/big-data-cluster-overview?view=sql-server-ver15

@pmasl - I see... I checked that but didn't find it... I will edit this page again to fix the capitalization shortly. thanks!

@EricBuMSFT: I'm sorry - only the author of this article, @pmasl, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.