Maciej Filip, did you ever found a solution in SQLAlchemy for this? I'm
experiencing the same "Restoring.." problem..
On Tuesday, July 12, 2011 at 1:04:00 PM UTC-4, Michael Bayer wrote:
>
>
> On Jul 12, 2011, at 12:44 PM, Maciej Filip Szkodziński wrote:
>
> Oops, I was trying it with
>
The database is part of a desktop accounting application running on
Windows. I'm writing a program to interface with it, to automate
adding documents.
The idea was that it would be run once a month to add a bunch of
invoices. The backup would run before this operation, in case
something
On Jul 12, 2011, at 8:27 AM, Maciej Filip Szkodziński wrote:
The database is part of a desktop accounting application running on
Windows. I'm writing a program to interface with it, to automate
adding documents.
The idea was that it would be run once a month to add a bunch of
invoices.
Oops, I was trying it with
engine.connect().execution_options(autocommit=True).execute as well,
and didn't notice there was a difference in the echo when editing the
pastebin. There's of course no COMMIT at the end with eng.execute().
I've updated pastebin with both versions.
The behaviour
On Jul 12, 2011, at 12:44 PM, Maciej Filip Szkodziński wrote:
Oops, I was trying it with
engine.connect().execution_options(autocommit=True).execute as well,
and didn't notice there was a difference in the echo when editing the
pastebin. There's of course no COMMIT at the end with
I think more common practice is just to use shell scripts (whether in
scheduled tasks / cron jobs or manually) for backup. But I don't know
MSSQL specifically. I just have rarely heard of anyone trying to
accomplish their backup with SQLAlchemy as part of the chain of
command.
On Jul 11, 2:06
