Answers.Body: <p>Yes, you can have multiple Civi/CMS instances on the same server. Depending on your preference, when looking at your server, you will see something along the lines of one of the the following structure:</p>
  
  <p><a href="https://i.sstatic.net/EDTXf.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/EDTXf.jpg" alt="enter image description here"></a></p>
  
  <p>Per comment - editing my response to include database - unless you are setting up a multi-site instance of Civi, you would need a separate database for each CMS instance.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-13T01:22:49.453Z
Answers.Text: did you answer the issue that they only have one db?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-12T19:19:13.800Z
Answers.Text: Hi, thanks for your explanation, but as mentioned in the previous comment, it does not solve my issue. I have only one database. If there a possibility to work with different table prefixes? For instance civicrm_contact is used for production, staging_civicrm_contact is used for staging?
Answers.UserDisplayName: DirkV
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-15T22:33:43.693Z
Answers.Text: You might be able to add tables to the Civi database without breaking it, but you would have no way of telling Civi to store something in the staging_ table vs. the civicrm_ table. You can change the mode of your database from production to demo/staging, but that doesn't create a whole new set of tables in the database, it simply prevents emails being sent out and cron jobs will not be executed. Admittedly, I'm not technical, but it is unclear to me (unless you are unable to add server resources) why you are limited to a single database?
Answers.UserDisplayName: Tamar Meir - Cividesk
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-12T21:01:36.037Z
Answers.LastActivityDate: 2018-09-13T05:30:14.637Z
Answers.LastEditDate: 2018-09-13T05:30:14.637Z
Answers.UserDisplayName: Tamar Meir - Cividesk
Body: <p>I have one mySQL database and one Apache webserver. Can I still run 2 separate wordpress/Civicrm environments (like staging and production)?</p>
  
Tags: <database><installation>
Title: Running 2 civicrm instances on 1 database
ThreadText: # Running 2 civicrm instances on 1 database
  
  (Asked by: username_0 on 2018-09-12)
  
  I have one mySQL database and one Apache webserver. Can I still run 2 separate wordpress/Civicrm environments (like staging and production)?
  
  **Tags:** database, installation
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-09-12. Score: 1
  
  Yes, you can have multiple Civi/CMS instances on the same server. Depending on your preference, when looking at your server, you will see something along the lines of one of the the following structure:
  
  [![enter image description here](https://i.sstatic.net/EDTXf.jpg)](https://i.sstatic.net/EDTXf.jpg)
  
  Per comment - editing my response to include database - unless you are setting up a multi-site instance of Civi, you would need a separate database for each CMS instance.
  
  > **Comments:**
  > **username_2**: did you answer the issue that they only have one db?  
  > **username_0**: Hi, thanks for your explanation, but as mentioned in the previous comment, it does not solve my issue. I have only one database. If there a possibility to work with different table prefixes? For instance civicrm_contact is used for production, staging_civicrm_contact is used for staging?  
  > **username_1**: You might be able to add tables to the Civi database without breaking it, but you would have no way of telling Civi to store something in the staging_ table vs. the civicrm_ table. You can change the mode of your database from production to demo/staging, but that doesn't create a whole new set of tables in the database, it simply prevents emails being sent out and cron jobs will not be executed. Admittedly, I'm not technical, but it is unclear to me (unless you are unable to add server resources) why you are limited to a single database?  
  
  ---
  
  