Re: just wondering about MSKB 828481
From: SuperGumby [SBS MVP] (not_at_your.nellie)
Date: 09/16/04
- Next message: Marina Roos [SBS-MVP]: "Re: Client Connection problems"
- Previous message: N. Hughes: "ISA Messed Up..."
- In reply to: Steve Foster [SBS MVP]: "Re: just wondering about MSKB 828481"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 21:22:47 +1000
I believe (and I've gotta point out that I am NOT familiar with their app)
that the app can, if I retain the current recovery model, restore the
database via a combination of backup and logs to a specific time. Specific
to the extent 'No, we don't want the data from 12:34:14.59, we want
12:34:14.58'.
If I change the recovery model I can assure the client 'we can rollback to
time X (last SQL backup to file)', time Y (last system backup to tape), or
any other time which exists on our tapes which also inlude the SQL backups
to file at whatever interval they occur.
As the client is a financial market player it _may_ be worth more to them to
rollback to an arbitrary point than my time costs.
AWWW HECK, I've told the client we have a patch we haven't needed to
implement on any other site. We'll do it and if it fixes the problem we'll
forget about it. If the patch doesn't fix the problem we have alternatives
but those alternatives may result in the 3rd party's app functions being
limited.
MY PET PEEVE. Why do I have to consider the overall pros and cons of every
minor registry change when some know-nothing application programmer can
impact the overall system activity and say 'because that's the way we like
to do it'. It wouldn't take a lot of encouragement for me to put Application
Programmers right up there against the wall with SPAMMERS and VIRI authors.
Many of them have no freakin idea. And then their installer program does
something really simple, like change the NETBIOS name of the machine it is
installed on.
"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0dnbxmtzzr3t006@msnews.microsoft.com...
> SuperGumby [SBS MVP] wrote:
>
>> The package accessing the database is supplied by a third party. An
>> available function, the ability to rollback the database to a
>> particular point, seems to depend on the database being in other than
>> simple recovery mode. If I can patch and retain the recovery mode and
>> rollback I'll be OK.
>>
>> and despite the fact that their implementation has broken my backup
>> I'm going to try not to break their database.
>
> SQL Server doesn't, AFAIK, offer any native method for unravelling
> data, other than by using an older backup and restoring it. The SQL
> Transaction logs are there so that you can roll forward from a previous
> backup when doing DR. SQL does allow some control over the roll forward
> process, but I doubt that an application would be using this
> methodology to provide user rollback capabilities (I'd have thought it
> too unwieldy).
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.
- Next message: Marina Roos [SBS-MVP]: "Re: Client Connection problems"
- Previous message: N. Hughes: "ISA Messed Up..."
- In reply to: Steve Foster [SBS MVP]: "Re: just wondering about MSKB 828481"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
