Arvind Shyamsundar

Hello @wrosenuance - thanks for the great work on this. We have a use case where the changes enabled by this PR would greatly simplify the handling of Managed Identity...

Here's a more detailed reproduction, # Environment * SQL Server 2019 and Microsoft Visual Studio Enterprise 2022 * VS 2019 17.1.4 and SQL Server Data Tools 17.0.62203.25080 # Steps 1....

> To clarify, the sample T-SQL is incorrect syntax, the correct syntax is > > ```tsql > SELECT value FROM GENERATE_SERIES(1, 5); > SELECT value FROM GENERATE_SERIES(1, 32, 7); >...

@kisantia @dzsquared this should be labeled with the `scriptdom` label to help track it. And it reproduces in C# and on Windows, so it is not a F# issue by...

@taspeotis - ScriptDom is not exclusively for BACPAC operations. Conceptually, we should be supporting this syntax in ScriptDom. CC: @yualan @dzsquared

As an experiment, I attempted to construct an unofficial, best-effort, [change log](https://deep.data.blog/2022/06/03/unofficial-sql-scriptdom-change-log/) for ScriptDom alone. There are limits to publicly derived guesswork such as what went into this blog post,...

Many customers are using [Always Encrypted with web apps](https://blogs.msdn.microsoft.com/sqlcat/2016/09/15/using-sql-always-encrypted-with-azure-web-app-service/). Node.js support has been asked as well. It would be great if tedious can support Always Encrypted.

With current (August 2021) versions of ansible-lint, these obscure numeric codes are deprecated in favor of text labels which more clearly indicate the purpose of the exclusion. Due to behavior...

> I managed to reproduce the error. Can you share the repro conditions? I'm really curious about this issue. Is it occurring for a specific state and area?

Many thanks for the clarification @jawalonoski.