I get deadlocks and the wiki states, that one has to SET IMPLICIT_TRANSACTIONS ON: https://confluence.atlassian.com/display/JIRAKB/Deadlock+when+running+JIRA+with+SQL+Server
But it seems this doesn't persist. How can I make that setting permanent in SQLServer?
EDIT: It is impossible to set that option at db level. It's only possible to set it as defaults for all users of the whole instance (i.e. server):
No, that's the point - it's a database server setting, NOT the application.
The application could do it with the session, but then it would need more rights over the database than it needs for day-to-day running, and you'd have to do database specific coding. (i.e. bad security practice and bad coding practice)
I would agree with you, if it was possible to set that option permanently.
But sadly this isn't possible. Even Atlassian support got this wrong and replied with this article:
Which clearly says:
"5. [...] from now onwards all the new connections opened through Management Studio/Workbench starts an implicit transactions"
I edited the question to include my new findings. Is shows that it's impossible to set that option permanently on a db level.
That's why I say, that it's Atlassians responsibility to set that option at connection time or otherwise remove SQL-Server from the list of supported databases. Alternatively, Atlassian should require customers to use a dedicated instance for JIRA.
(I agree that SQL-Server is the worst db-alike shit in this universe, but in the current universe I have no choice).
Ok, it's not a database setting, it's a user one. http://msdn.microsoft.com/en-us/library/ms176031.aspx
I still don't think it's an Atlassian issue directly, even if you don't do it at a user level. If it needs to be set permanently, then it feels like it should be a driver setting.
I also wonder why only there's only one question about it in Answers - that implies your setup is pretty rare and there's something very different about what you've got compared with everyone else using Jira and SQL-Server - if that's the case, then having Atlassian implement somthing that could break all the other users is probably going to be a complete non-starter.
How could it break any other installations?
If you're still afraid then make it configurable => zero risk => another satisfied customer :-)
I guess other users either
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG