To reproduce try this command in any site managed in Aegir.

The result:

o1@v227a:~/platforms/cod-alpha3/sites/cod2.o1.chicago.aegir.cc$ drush sql-connect < database.sql -d                                                
Bootstrap to phase 0. [0.02 sec, 2.19 MB]                            [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drush() [0.02 sec, 2.41 MB] [bootstrap]
Bootstrap to phase 3. [0.06 sec, 9.37 MB]                                                                                                [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_root() [0.06 sec, 9.38 MB]                                                               [bootstrap]
Loading drushrc "/data/disk/o1/platforms/cod-alpha3/drushrc.php" into "drupal" scope. [0.06 sec, 9.38 MB]                                [bootstrap]
Initialized Drupal 6.20 root directory at /data/disk/o1/platforms/cod-alpha3 [0.07 sec, 11.38 MB]                                           [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site() [0.07 sec, 11.38 MB]                                                              [bootstrap]
Initialized Drupal site cod2.o1.chicago.aegir.cc at sites/cod2.o1.chicago.aegir.cc [0.07 sec, 11.39 MB]                                     [notice]
Loading drushrc "/data/disk/o1/platforms/cod-alpha3/sites/cod2.o1.chicago.aegir.cc/drushrc.php" into "site" scope. [0.07 sec, 11.39 MB]  [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration() [0.08 sec, 12.8 MB]                                                      [bootstrap]
Found command: sql-connect (commandfile=sql) [0.08 sec, 12.81 MB]                                                                        [bootstrap]
Initializing drush commandfile: drush_make [0.08 sec, 12.82 MB]                                                                          [bootstrap]
Initializing drush commandfile: drush_make_d_o [0.08 sec, 12.82 MB]                                                                      [bootstrap]
Initializing drush commandfile: provision [0.09 sec, 12.82 MB]                                                                           [bootstrap]
Loading drushrc "/data/disk/o1/platforms/cod-alpha3/sites/cod2.o1.chicago.aegir.cc/drushrc.php" into "site" scope. [0.09 sec, 12.83 MB]  [bootstrap]
Load alias @server_master [0.09 sec, 12.84 MB]                                                                                              [notice]
Loading mysql driver for the db service [0.09 sec, 12.87 MB]                                                                                [notice]
Loading nginx driver for the http service [0.09 sec, 12.88 MB]                                                                              [notice]
Initializing drush commandfile: user [0.09 sec, 12.89 MB]                                                                                [bootstrap]
mysql --database=cod2o1chicagoa_0 --host=v227a.us.host8.biz --port=3306 --user=cod2o1chicagoa_0 --password=****
Command dispatch complete [0.09 sec, 12.89 MB]                                                                                              [notice]
 Timer  Cum (sec)  Count  Avg (msec) 
 page   0.007      1      6.51       

Peak memory usage was 13.88 MB [0.09 sec, 12.89 MB]                                                                                         [memory]
Press any key to continue...

Comments

damien tournoud’s picture

Category: bug » support

You probably want drush sql-cli < database.sql, not sql-connect.

msonnabaum’s picture

Status: Active » Fixed

sql-connect just prints out the connect string, so you need to evaluate it like so:

$(drush sql-connect) < database.sql
omega8cc’s picture

Status: Fixed » Active

Yes, drush sql-cli < database.sql works, right, but http://drush.ws/#sql-connect has drush sql-connect < database.sql listed as a valid db import command, so I was confused.

omega8cc’s picture

Component: SQL » Documentation

Oops, I changed the status by accident.

Ah, right, in fact it is `drush sql-connect` < example.sql.

Status: Active » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.