Answers.Body: <p>You can find a number of shared hosts that do support InnoDB if your budget doesn't cover costs for a VPS (not to mention that you may/not have the expertise or time to manage/administer a virtual private server).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-05T17:02:01.040Z
Answers.LastActivityDate: 2015-10-05T17:02:01.040Z
Answers.UserDisplayName: Lesley Evensen
Answers.Body: <p>To speak to the worth of a VPS -- <strong>yes, it is worth the money to use a VPS instead of shared hosting when CiviCRM is involved.</strong>  Certainly, you get the benefit of controlling your server environment for things like database engine changes, but perhaps the biggest benefit you will see is increased performance. The shared environment may work in the short term, but as your database and needs grow, I suspect you will hit limitations with your hosting.</p>
  
  <p>See this question for reference: <a href="https://civicrm.stackexchange.com/questions/6467/choosing-a-vps-solution-for-civicrm">Choosing a VPS solution for CiviCRM</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-07T02:11:42.907Z
Answers.Text: It's true we've hit the limit now and again but, generally, shared hosting fits our needs :) We're only a small association. I think changing providers is the right answer here!
Answers.UserDisplayName: Esther
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-05T03:35:20.687Z
Answers.LastActivityDate: 2015-10-05T03:35:20.687Z
Answers.LastEditDate: 2017-04-13T12:53:13.167Z
Answers.UserDisplayName: Allen Hutchison
Answers.Body: <p>And you can not use MyISAM for CiviCRM!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-07T02:12:48.450Z
Answers.Text: It's been working for the past 2 years, it'll be interesting to see what difference it makes! :) It's only since the last upgrade that we've been receiving the error message. So maybe it's not the upgrade itself causing the error, but that the message is now built-in!
Answers.UserDisplayName: Esther
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-11T11:48:44.880Z
Answers.Text: There are some triggers on tables, as far as I know they cause errors when you are using MyISAM. Also, in the installation instructions on the CiviCRM documentation wiki there is this message: 
  MySQL 5.1.x or higher with INNODB support : CiviCRM is compatible with the current generally available MySQL release. Trigger permission is required. SUPER privileges are required in MySQL 5.1 if binary logging is enabled. See the CiviCRM MySQL Permission Requirements page.
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-05T06:29:14.857Z
Answers.LastActivityDate: 2015-10-05T06:29:14.857Z
Answers.UserDisplayName: ErikH - CiviCooP
Body: <p>We're running CiviCRM 4.6.8 on WordPress 4.3.1.</p>
  
  <p>I've been getting the following error message since the last CiviCRM upgrade:</p>
  
  <blockquote>
    <p>Warning Your database is configured to use the MyISAM database engine.
    CiviCRM requires InnoDB. You will need to convert any MyISAM tables in
    your database to InnoDB. Using MyISAM tables will result in data
    integrity issues.</p>
  </blockquote>
  
  <p>The site is on a shared server, so I can't change the storage engine unless we move the website to a VPS package. </p>
  
  <p>Does it matter? Should we fork out the $ for a VPS? Migrate elsewhere?</p>
  
Tags: <wordpress><database><mysql>
Title: MyISAM vs InnoDB - WordPress Installation
ThreadText: # MyISAM vs InnoDB - WordPress Installation
  
  (Asked by: username_0 on 2015-10-04)
  
  We're running CiviCRM 4.6.8 on WordPress 4.3.1.
  
  I've been getting the following error message since the last CiviCRM upgrade:
  
  > Warning Your database is configured to use the MyISAM database engine.
  > CiviCRM requires InnoDB. You will need to convert any MyISAM tables in
  > your database to InnoDB. Using MyISAM tables will result in data
  > integrity issues.
  
  The site is on a shared server, so I can't change the storage engine unless we move the website to a VPS package.
  
  Does it matter? Should we fork out the $ for a VPS? Migrate elsewhere?
  
  **Tags:** wordpress, database, mysql
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2015-10-05. Score: 0 | Accepted answer
  
  You can find a number of shared hosts that do support InnoDB if your budget doesn't cover costs for a VPS (not to mention that you may/not have the expertise or time to manage/administer a virtual private server).
  
  
  ---
  
  ### Answer by username_2 on 2015-10-05. Score: 2
  
  To speak to the worth of a VPS -- **yes, it is worth the money to use a VPS instead of shared hosting when CiviCRM is involved.** Certainly, you get the benefit of controlling your server environment for things like database engine changes, but perhaps the biggest benefit you will see is increased performance. The shared environment may work in the short term, but as your database and needs grow, I suspect you will hit limitations with your hosting.
  
  See this question for reference: [Choosing a VPS solution for CiviCRM](https://civicrm.stackexchange.com/questions/6467/choosing-a-vps-solution-for-civicrm)
  
  > **Comments:**
  > **username_0**: It's true we've hit the limit now and again but, generally, shared hosting fits our needs :) We're only a small association. I think changing providers is the right answer here!  
  
  ---
  
  ### Answer by username_3 on 2015-10-05. Score: 0
  
  And you can not use MyISAM for CiviCRM!
  
  > **Comments:**
  > **username_0**: It's been working for the past 2 years, it'll be interesting to see what difference it makes! :) It's only since the last upgrade that we've been receiving the error message. So maybe it's not the upgrade itself causing the error, but that the message is now built-in!  
  > **username_3**: There are some triggers on tables, as far as I know they cause errors when you are using MyISAM. Also, in the installation instructions on the CiviCRM documentation wiki there is this message:  MySQL 5.1.x or higher with INNODB support : CiviCRM is compatible with the current generally available MySQL release. Trigger permission is required. SUPER privileges are required in MySQL 5.1 if binary logging is enabled. See the CiviCRM MySQL Permission Requirements page.  
  
  ---
  
  