There have been a few cases where customers would report being not able to perform various operations pertaining to really long ticket.
Upon investigating, Support identified that most of these issues stem from a known MS limitation where by a single procedure can not handle more than 2100 parameters:
https://docs.microsoft.com/en-us/sql/relational-databases/stored-procedures/specify-parameters?view=sql-server-ver15

A procedure can have a maximum of 2100 parameters; each assigned a name, data type, and direction. Optionally, parameters can be assigned default values.

We have a couple of bugs stemming from this limitation:
https://jira.atlassian.com/browse/JRASERVER-65961
https://jira.atlassian.com/browse/JRASERVER-63290

In plain terms, a use case would be an issue in JIRA with more than 2000 comments; Affected customers would need to trim such issues before they can delete it

It would be great to include this limitation to our 'Connecting to MS SQL' JIRA guides so that customers are aware in advance that they may run into a limitation like this:
https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-a-database-938846850.html