Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: sp_Blitz stored procedure cannot be parsed (SQL Server) #3316

Closed
Demivan opened this issue Jan 15, 2025 · 6 comments
Closed

Bug: sp_Blitz stored procedure cannot be parsed (SQL Server) #3316

Demivan opened this issue Jan 15, 2025 · 6 comments
Assignees
Labels

Comments

@Demivan
Copy link

Demivan commented Jan 15, 2025

Stored procedure generated by the script https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/blob/dev/sp_Blitz.sql cannot be parsed

Error: mssql: parse proc definition: expecting an identifier at position 455010, got ");

@giautm giautm self-assigned this Jan 31, 2025
@giautm
Copy link
Member

giautm commented Jan 31, 2025

Hey, can you please try again with the latest version. And let me know if it work?. Btw, please share the commands (or steps) used to load this schema. It will help me a lot in debug.

@giautm giautm added the MSSQL label Jan 31, 2025
@Demivan
Copy link
Author

Demivan commented Jan 31, 2025

I can still reproduce this on latest version.

Steps to reproduce:

  1. Create empty DB
  2. Run the script https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/blob/dev/sp_Blitz.sql
  3. Try running atlas schema inspect
  4. Get Error: mssql: parse proc definition: expecting an identifier at position 607068, got ");' error

@giautm
Copy link
Member

giautm commented Jan 31, 2025

Thank you, I'll take a look soon.

@giautm
Copy link
Member

giautm commented Feb 1, 2025

Hey, it was fixed in the last version. Please re-install and give a try. Thanks.

@giautm
Copy link
Member

giautm commented Feb 1, 2025

Please let me know if this issue still exists, closing now.

@giautm giautm closed this as completed Feb 1, 2025
@Demivan
Copy link
Author

Demivan commented Feb 1, 2025

It works now, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants