Re: Point in time restore error
- From: "DCraig" <dcraig@xxxxxxxxxx>
- Date: Fri, 14 Apr 2006 16:16:16 -0700
Tibor;
When I tried it the next day it worked fine. If it happens again I will
fire up the profiler and see what/if it's sending to the database and post
what I find. It's very nice when it works.
I suspect you are correct about it being a problem with the GUI because the
error happens so quick I doubt it's hitting the database. It may not be the
same error as what was fixed at SP3 just because it's the same error
message.
At this point, our documentation includes instructions for using the GUI and
an SQL example in case this problem crops up again, so I guess we're covered
either way. I plan on doing test restores on a regular basis until we are
comfortable with them so if it comes up again I'll be back.
Thanks for replying;
David Craig.
"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx> wrote in
message news:OvaY4ZwXGHA.508@xxxxxxxxxxxxxxxxxxxxxxx
First you need to track down where the problem really is. I have a feeling
it is in the GUI. I know for sure that the GUI doesn't handle different
datetime settings properly. Catch the RESTORE statement submitted by the
GUI using the Profiler tool and you can see what is submitted. If that
doesn't solve your problem, you can post that RESTORE statement here and
we can have a look at it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DCraig" <dcraig@xxxxxxxxxx> wrote in message
news:%23%23v$y4oXGHA.4324@xxxxxxxxxxxxxxxxxxxxxxx
SQL Server 2000 Standard edition SP4, Windows server 03, W2K and XP Pro
clients.
I'm setting up a recovery plan and doing some test restores. My problem
is that when I try to do a point in time restore with Enterprise Manager
(EM) I get an error message:
"The time specified is less than the minimum point in time allowed. Time
corrected." And it sets the point in time back to the time the log
backup was run. This sort of defeats the pupose of having point in time
restore.
A google search provided the answer but the page on MS's site says that
this problem was fixed at SP3, yet we are running SP4.
<http://support.microsoft.com/kb/q260182>
There is a workaround, which is to use SQL to restore the final log
backup and set the time with the SQL Statement, but my question is more:
do other people have this problem when they try to do point in time
restores with EM or is it something with the database?
I suspect that it may have to do with the fact that that database
probably has no transactions in the log. So is Microsoft lying about the
issue being fixed or does it have to do with the test database?
Any help is welcome;
DCraig.
.
- References:
- Point in time restore error
- From: DCraig
- Re: Point in time restore error
- From: Tibor Karaszi
- Point in time restore error
- Prev by Date: Re: run Profiler on a specific SP/Query/Function
- Next by Date: Importing data with BCP using a query...
- Previous by thread: Re: Point in time restore error
- Next by thread: Re: SQL 2005
- Index(es):
Relevant Pages
|
