William Assaf MSFT comments

Results 36 comments of


                                            William Assaf MSFT

What do you mean by "covering" and "non-covering" cache in Azure SQL Hyperscale?

#assign:WilliamDAssafMSFT

What do you mean by "covering" and "non-covering" cache in Azure SQL Hyperscale?

#assign:dimitri-furman

What do you mean by "covering" and "non-covering" cache in Azure SQL Hyperscale?

Thanks @Ray-Eldath for contacting Microsoft with feedback about our product documentation. It could take from a few business days to a few weeks to look further into this with the...

known issue with collation Latin1_General_BIN2

Looks good to me. #sign-off

Directions for install location for client agent contradict Best Practices guide

Thanks @jbogard for contacting Microsoft with feedback about our product documentation. As you can see from this delay in responding, it could take a bit to look further into this...

Directions for install location for client agent contradict Best Practices guide

Thanks again @jbogard for contacting Microsoft to point out this contradiction. Nice catch! A doc fix is in flight. In short, you should install the client agent on a machine...

Add AAD graph to workspace management requirements

@Ciil Thanks for taking the time to create this submission. We will be incorporating this commit into another effort. Your commit will be merged and this article update is in...

What do you mean by "covering" and "non-covering" cache in Azure SQL Hyperscale?

Thanks again @Ray-Eldath for taking the time to provide this documentation feedback. After a conversation with the PG I think we can make this more clear, a doc update is...

Azure permission "Microsoft.Resources/subscriptions/resources/write" cannot be located

Thanks very much @Thilig for taking the time to create a GitHub issue and point this out. This does appear to be a bug in the doc. Meanwhile, you should...

The depoly failed since the links are broken. Even download the repository doesn't help since the references to the BLOB storage are wrong.

Thanks @AssafFraenkel for pointing this out. We are aware of the issue and are rehousing the files. Will update.