jira service desk scalability - design

[j]

The scenario, generate ServiceDesk project for multiple countries (min 4 countries), 200 issues per day and per country

What are the best practices and considerations for Service Desk design:

• Multiple service desk projects? each per country? or only one is enough?
• What about database? is there a way to generate historical issue database?
• what is the limit number for issues
• how about the queues, it will get slowly over the time

thanks in advanced

[Meck · Accepted solution]

Hi jaguilar*,

Lemme try help you a little.

• Multiple service desk projects? You should setup as Atlassian Help Center - https://support.atlassian.com/customer/servicedesk-portal per products / service
• What about database? I think you looking for this https://answers.atlassian.com/questions/38841285
• What i s the limit number for issues?There is no limit. You can have any number of issues but you will see performance related issues when it grows to millions.
• About queues you need setup right, and you should use JIRA Software to generate releases for your project.

I hope it helped you.

Regards,
Lameck. 

[j]

Hi Lameck,

Thanks for your answer,

I would like to be more specific

• Multiple service desk projects?
• What about database? Actually we use SQL Server, the question is about large databases, if there are recommendations or best practices, because in one year all will work ok but in 5 years the performance will decrease, so what can i do now for avoid this "future" problem.
  this is the reason why i asked about multiple service desk projects too and not to use only one project
• What i s the limit number for issues?
  About your answer, that is the scenary that i would like to manage, what do i have to do if we have millions of issues; can we divide the database? create historic tables? 
• About queues
  we only have JIRA service desk, so we need to know and investigate about the "setup right" that you mention.

thanks in advanced