Notice: Stripping USE / CREATE statements from Database Exports

We recently improved the ways you can configure and download copies of your database backups from VIP Dashboard. We also want to make sure that the data you download is as easy to use as possible.

Starting Wednesday, January 25, 2023, SQL files exported by VIP (either through the VIP Dashboard or Backup Shipping) will no longer include USE and CREATE statements.

These statements can cause compatibility issues with many tools, including our own Local Development Environment, and requires an extra, often very difficult, step to clean up the SQL file before it can be used. We hope that this change will simplify your workflows and remove the need for the cleanup step (for example, importing to VIP local development environments or VIP Platform environments).

If your integrations are expecting the the USE / CREATE statements to be present in the exported SQL files, you will need to execute the equivalent statements before using them to ensure the expected database is available and selected.

Before

-- MySQL dump 10.19  Distrib 10.3.28-MariaDB, for debian-linux-gnu (x86_64)
--
-- Host: localhost    Database:
-- ------------------------------------------------------
-- Server version 10.3.28-MariaDB-1:10.3.28+maria~focal-log
 
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
 
--
-- Current Database: `vt_mytestsitego4323`
--
 
CREATE DATABASE /*!32312 IF NOT EXISTS*/ `vt_mytestsitego4323` /*!40100 DEFAULT CHARACTER SET utf8 */;
 
USE `vt_mytestsitego4323`;
 
--
-- Table structure for table `wp_a8c_cron_control_jobs`
--
 
DROP TABLE IF EXISTS `wp_a8c_cron_control_jobs`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;

After

-- MySQL dump 10.19  Distrib 10.3.28-MariaDB, for debian-linux-gnu (x86_64)
--
-- Host: localhost    Database:
-- ------------------------------------------------------
-- Server version 10.3.28-MariaDB-1:10.3.28+maria~focal-log
 
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
 
 
 
--
-- Table structure for table `wp_a8c_cron_control_jobs`
--
 
DROP TABLE IF EXISTS `wp_a8c_cron_control_jobs`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;

If you have any questions or need assistance with this change, please do not hesitate to open a support ticket.

Before

After

Responses