igo | Intermediate GoLang source representation | Parser library

To robustly parse your input into batches, you need a language parser that can reliably identify syntactic elements - regexes are not sophisticated enough to model the grammar of your input.

In the absence of a T-SQL parser,^[1] you can probably get away with PowerShell's own language parser, [System.Management.Automation.Language.Parser], given that there are high-level commonalities between the two languages, so it should be able to identify isolated, non-@-prefixed GO tokens in your input:

Caveat re commment support:

• Because T-SQL's comment constructs differ from PowerShell, using the PowerShell parser would yield false positives for (isolated) GO substrings inside comments.

• The solution below therefore uses regex-based preprocessing that removes all comments (with additional effort involving a post-processing step, the comments could be preserved), but this isn't fully robust and relies on the following assumptions:

  • No comment-like constructs appear inside quoted strings.
  • Block quotes (/* ... */) aren't nested.
    (With a more sophisticated regex using balancing group definitions you may be able to overcomes this particular limitation).

And one more thing your pdf not shown because some links is secure that's why they not access the link data pdf

And all the data store into fileURL Variable and put fileUrl Varibale in pdf-viewer like this

HTML