Closed (fixed)
Project:
Drush
Component:
SQL
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 May 2011 at 04:05 UTC
Updated:
4 Jan 2014 at 00:53 UTC
Jump to comment: Most recent, Most recent file
sql-dump does not work with Windows SQL Server, and sql-sync needs adjustment for all database types.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | sql_server_dump_initial.patch | 1.16 KB | welinwelchev |
Comments
Comment #1
greg.1.anderson commentedForgot 'windows' tag again.
Comment #2
greg.1.anderson commentedsql-sync is refactored in #1149880: Remote commands to drush on Windows server + backend invoke / sql-sync refactor.
Comment #3
welinwelchev commentedHi,
Appologies if I am not putting the right status here. "needs review" seem the most appropriate.
I want to suggest a patch for this enabling basic dump ability for sql server. I have tested it locally and it works fine.
Sql server dumps are that they are binary files, and all our other dumps actually have .sql statement files generated.
In my research towards this issues I found this http://sqlserverdump.codeplex.com/ tool, which it is too new and still in Alpha but still it can be a tool to be packed by the installer and will provide sql statement dumps from sql server also.
Comment #4
greg.1.anderson commentedThanks for pushing this issue forward! You are correct, "needs review" was the right status for #3.
If there is nothing in $file, use drush_set_error instead of
echo.The other really important thing is that there needs to be a way to import the file again after you dump it. Currently, we have no
sql-importcommand for Drush; we just tell folks to use`drush sql-connect` < $file. What is the best way to import a binary SQL Server dump file? Maybe we needsql-importto wrap this operation (maintaining database agnosticism for Drush clients)?As for sqlserverdump, it certainly sounds promising. My instinct would be to use the native tool by default, but dumping to sql statements could be a good ad-on feature for the future, if it becomes stable enough to be packaged with the Drush installer.
Comment #5
moshe weitzman commentedarchive-restore needs to be able to restore whatever was dumped so we do have a use for this in core. i guess this does argue for adding a sql-import command as a wrapper.
Still, sqlserv compatibility is a way lower priority (for me) than general Windows compatibility for drush.
Comment #6
greg.1.anderson commentedDon't have time for sqlserv compatibility right now.
Comment #7
moshe weitzman commentedWe actually added this during the code sprint this weekend. It uses sqlcmd
Comment #8
greg.1.anderson commentedAwesome.