We worked hard on fine-tuning C2S into being very fast, but the time depends entirely on the size of the file and the kind of data it contains. The big majority of the conversions are done within the hour. In most cases, it's just a matter of minutes.
The system deletes the source file directly after the conversion is done, after 24 hours your converted file is also deleted.
No, we deliver it as a seperate SQL file. This makes it easier to edit it rather then if it would have been included directly in the SQL dump file.
With this option we generate and include a migration php-file with your download. Laravel Migration is a feature of the Laravel PHP Framework. It is like version control for your database. Click here for more info!
No - the system only takes the first worksheet of the excel file, even if it contains more then one. So if the file contains multiple ones you need to seperate them into different files and upload them one for one.
Yes, all traffic on C2S is encrypted with strong TLS/SSL over HTTPS.
Sometimes it's easier just to concatenate both files into one joined dump file before the import. You can use the following commands for that:
$ cat path/to/schema.sql path/to/dump.sql >> path/to/joined-import-file.sql
: type schema.sql dump.sql > joined-import-file.sql
> use YOUR_DATABASE_NAME; > source path/to/schema.sql; > source path/to/dump.sql;
> \c YOUR_DATABASE_NAME; > \i path/to/schema.sql; > \i path/to/dump.sql;
: sqlcmd -S server_name\instance_name -d database_name -i C:\path\to\schema.sql -o C:\path\where\you\want\output-file.txt : sqlcmd -S server_name\instance_name -d database_name -i C:\path\to\dump.sql -o C:\path\where\you\want\output-file.txt
Sometimes you might experience this problem. Because the Laravel migration file was not generated by your application, using
$ php artisan migrate:rollback might throw a
"Class not found" FatalErrorException. Thankfully, there is a easy fix for this. Just run:
$ composer dump-autoload