Allow configurable parameter limit above 999 for stored procedure calls

[Pedro-Laurenti]

Is your feature request related to a problem? Please describe.

mssql-python enforces a hard limit of 999 parameters per query. This is a library-imposed constraint — SQL Server itself supports up to 2100. pyodbc, the previously recommended Microsoft driver, respected the server's limit and did not impose a lower one. This is a regression for anyone migrating from pyodbc.

Describe the solution you'd like

Either raise the default limit to match the SQL Server ceiling (~2100), or expose a configurable option (e.g. a connection/cursor attribute) so users can set it themselves.

Describe alternatives you've considered

Splitting calls into batches of <999 parameters, or using TVPs and JSON parameters — but these require refactoring code that worked fine under pyodbc with no changes.

Additional context

• SQL Server max capacity spec: https://learn.microsoft.com/en-us/sql/sql-server/maximum-capacity-specifications-for-sql-server
• pyodbc discussion confirming no library-side limit: Can pyodbc handle more than 2100 parameters like mxodbc does? mkleehammer/pyodbc#1332

[github-actions]

Hi @Pedro-Laurenti, thank you for opening this issue!

Our team will review it shortly. We aim to triage all new issues within 24-48 hours and get back to you.

If you have additional information to share, please feel free to update the issue.

Thank you for your patience!

[jahnvi480]

@Pedro-Laurenti Thanks for filing this issue!

We investigated the mssql-python codebase and can confirm that the driver does not impose a client-side limit of 999 parameters (or any other library-side cap). Parameters are bound directly via ODBC's SQLBindParameter with no count validation on our end, so the effective ceiling is SQL Server's own ~2,100 parameter maximum per query (reference)
This means mssql-python behaves the same as pyodbc in this regard - neither driver enforces a limit below the server's.

Could you provide:

• A minimal reproducible example (using mssql-python directly, without an ORM)?
• The exact error message you're receiving?
• The version of mssql-python you're using?

This will help us determine where the 999 limit is actually being enforced. If it turns out the error message from the server side is confusing, we're happy to look into adding a clearer client-side validation message when parameter counts approach the ~2,100 server limit.