Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-33769

Add a database collation checker on the initial setup.

XMLWordPrintable

    • 9

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      We notice that a lot of our customer have troubles upgrading Confluence when their collation (MSSQL) or charter encoding /Colation/Engine (mysql).

      Because of that they end up creating support cases to address this miss behaviours during the upgrade.

      We indeed added a collation checker for both MySQL and MSSQL but what we would like is to add that check in the initial setup as well, so we will get new users unable to setup Confluence due the above error (L3/L4) instead of clients with odd errors or production outages due the wrong collation in an failed upgrade attempt (L1/L2).

      Fix those settings is stressful to our customers since they only find this out months after installing Confluence (during an upgrade) and most of them do not have an allocated DBA to address these problems.

      Work Around:

      In case you already have a Confluence installed check the set of steps on below KB to fix the database inconsistencies:

      https://confluence.atlassian.com/display/CONFKB/How+to+fix+the+collation+and+character+set+of+a+Microsoft+SQL+Server+database

            [CONFCLOUD-33769] Add a database collation checker on the initial setup.

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3428193 ] New: JAC Suggestion Workflow 3 [ 3611116 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2240364 ] New: JAC Suggestion Workflow [ 3428193 ]
            Status Original: Needs Verification [ 10004 ] New: Gathering Interest [ 11772 ]
            SET Analytics Bot made changes -
            Support reference count New: 9
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2135579 ] New: Confluence Workflow - Public Facing v3 [ 2240364 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1892644 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2135579 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1801864 ] New: Confluence Workflow - Public Facing v3 [ 1892644 ]
            jonah (Inactive) made changes -
            Description Original: We notice that a lot of our customer have troubles upgrading Confluence when their collation (MSSQL) or charter encoding /Colation/Engine (mysql).

            Because of that they end up creating support cases to address this miss behaviours during the upgrade.

            We indeed added a collation checker for both MySQL and MSSQL but what we would like is to add that check in the initial setup as well, so we will get new users unable to setup Confluence due the above error (L3/L4) instead of clients with odd errors or production outages due the wrong collation in an failed upgrade attempt (L1/L2).

            Fix those settings is stressful to our customers since they only find this out months after installing Confluence (during an upgrade) and most of them do not have an allocated DBA to address these problems.

            h4. Work Around:

            In case you already have a Confluence installed check the set of steps on below KB to fix the database inconsistencies:

            https://confluence.atlassian.com/display/CONFKB/How+to+fix+the+collation+and+character+set+of+a+Microsoft+SQL+Server+database             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Cloud*. Using *Confluence Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFSERVER-33769].
              {panel}

            We notice that a lot of our customer have troubles upgrading Confluence when their collation (MSSQL) or charter encoding /Colation/Engine (mysql).

            Because of that they end up creating support cases to address this miss behaviours during the upgrade.

            We indeed added a collation checker for both MySQL and MSSQL but what we would like is to add that check in the initial setup as well, so we will get new users unable to setup Confluence due the above error (L3/L4) instead of clients with odd errors or production outages due the wrong collation in an failed upgrade attempt (L1/L2).

            Fix those settings is stressful to our customers since they only find this out months after installing Confluence (during an upgrade) and most of them do not have an allocated DBA to address these problems.

            h4. Work Around:

            In case you already have a Confluence installed check the set of steps on below KB to fix the database inconsistencies:

            https://confluence.atlassian.com/display/CONFKB/How+to+fix+the+collation+and+character+set+of+a+Microsoft+SQL+Server+database
            jonah (Inactive) made changes -
            Link New: This issue is related to CONFSERVER-33769 [ CONFSERVER-33769 ]
            vkharisma made changes -
            Project Import New: Sat Apr 01 14:06:06 UTC 2017 [ 1491055566265 ]
            Confluence Escalation Bot (Inactive) made changes -

              Unassigned Unassigned
              dluvison Deividi Luvison (Inactive)
              Votes:
              39 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated: