Hello,
I'm trying to backup a database running on SQL Server 2008 Express.
I'm using pyodbc as the driver.
This backup code executes happily, however no file is written to the
provided path. I've also tried placing an empty file in the path, and
only 2KB of data gets written to it.
eng = create_engine("mssql+pyodbc://%s:%s@%s" % (uid, pwd, server))
eng.execute('BACKUP DATABASE test TO DISK=?',
backupFilePath)
# <sqlalchemy.engine.base.ResultProxy object at 0x015868F0>
os.path.isfile(backupFilePath)
# False
I am able to backup the database with the same parameters in 'bare'
pyodbc.
Here's a more verbose version of both, sqlalchemy and pyodbc, backup
code:
http://pastebin.com/6x1RRTqz
I've also tried restoring an existing backup with sqlalchemy. Again, I
get the ResultProxy, but the newly 'restored' database is stuck in
perpetual 'Restoring...' state, and trying to use it results in:
# Database 'test' cannot be opened. It is in the middle of a restore.
I had a similar problem with bare pyodbc, and googling suggested that
this loop is required for the backup/restore operation to continue and
finish:
while backupCursor.nextset():
pass
where backupCursor is the one returned by execute('BACKUP...').
Is there a different way of doing backups via sqlalchemy, or some way
around this, or should I stick with bare pyodbc for backups?
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
