[princejain756]

Two MsSqlDialect AST nodes serialized into SQL their own dialect cannot parse back:

// DECLARE with a comma-separated variable list:
Parser::parse_sql(&MsSqlDialect {}, "DECLARE @a INT, @b INT")
    .unwrap()[0].to_string()
// -> "DECLARE @a INT; @b INT"  (the tail fails to reparse)

// ALTER ROLE rename:
Parser::parse_sql(&MsSqlDialect {}, "ALTER ROLE x WITH NAME = y")
    .unwrap()[0].to_string()
// -> "ALTER ROLE x RENAME TO y"  (MsSql only accepts WITH NAME =)

Statement::Declare now carries a DeclareDelimiter: Comma for the MsSql, BigQuery and PostgreSQL declaration forms, Semicolon for Snowflake's DECLARE a; b blocks. The T-SQL rename maps to a new AlterRoleOperation::RenameRoleWithName variant that emits WITH NAME =, matching how AddMember/DropMember already keep their T-SQL spellings.

Verified against the T-SQL docs for DECLARE and ALTER ROLE.

AI assistance disclosure: this change was developed with AI coding assistance.

[princejain756]

Closing this: the DECLARE half landed upstream via #2671 (comma preservation in displayed DECLARE lists), and the ALTER ROLE half is now #2709, which carries the same fix as a focused atomic PR using a use_with_name flag on RenameRole rather than a dedicated variant.