To fix an issue it is important to understand why it happens. Easiest way to do it is to repeat the issue few times, make assumptions, create few possible workarounds, then try them. Ideally you would do it on your own machine where you developed application, then push changes to production. In the databases world this approach, however, could fail, because you need real production data to repeat the issue or simply cannot afford to have server of same performance which production server uses.

In this webinar, which is the first one of "MySQL Troubleshooting Webinars" series I will demonstrate how to create test environment which can imitate your production server in a way, sufficient to perform tests.

We will discuss what to do in case:

- If production database is too large to be copied
- If production database contains sensitive data
- If production server much more performant than one you can use for tests
- If you don't have separate server to run tests

We will pay attention on what must be copied and which data or options can be modified without risk to make test invalid.

After this webinar you will be prepared to try any troubleshooting technique without fear.