What are the risks of having more than 1 schema in a JIRA database?

[Doods Perea]

Hi all - asking for guidance here on the pitfalls of creating 2 schema in 1 JIRA database.

Thank you.

[Joe Pitt · Accepted solution]

When you install JIRA it builds the tables, fields, etc. it needs in the empty schema. If you point a new instance of JIRA at the same database I expect you'll overwrite the current one. 

[Moses Thomas]

@Doods PereaWhat does  it mean? the risks of have more than one scheme ?  Jira  does the population of all tables  base on  its scheme and we have  lots of relationship  btw tables.

so  what are you  hoping  to  achieve here ?

[Doods Perea]

@Moses Thomas - in this Atlassian documentation, https://confluence.atlassian.com/adminjiraserver077/connecting-jira-applications-to-sql-server-2012-945532535.html, item #3 says "Create an empty 'schema' in the database for the JIRA tables  (e.g. jiraschema)".  What could be the potential problem, if any, if I happen to create another schema, say "jiradbschema" for the same database?

I am just wondering about the possibility of applications that push and pull data from JIRA using a connection to the JIRA database and using the 2nd schema when the 1st one is the correct schema to use.

Thanks,

Doods

[Moses Thomas]

@Doods PereaAs it's  written in  documentation  Jira requires only  one database to  run  and  then  create all  tables in  database  then  it will  populate all  objects on  the scheme, which you have defined, Jira will  use only  one( the one you  have define)  if

you  create  more than  one scheme in  your   database  server,  it will  be there empty,   i suppose and it  post  no risk .   This mechanism  you  have in  your mind ,  i have never implemented it so  i  cannot  explicitly  say  is  not do-able