hhhhelp, restore

ho fatto un update che non dovevo senza fare backup prima come posso
ripescare i dati?
gia committato ovviamente
carloUsted habla ingls?
(Also, pick a single newsgroup to post to.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Carlo wrote:

>ho fatto un update che non dovevo senza fare backup prima come posso
>ripescare i dati?
>gia committato ovviamente
>carlo
>
>|||Translated by bablefish:
I have made update that I did not have without to make before backup as I ca
n find again the data?
Probably not, if you don't have any backups at all. Do you have transaction
log backups?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Carlo" <carletto.mNOSPAM@.gmail.com> wrote in message news:OnD6BLncFHA.2664@.TK2MSFTNGP15.phx
.gbl...
> ho fatto un update che non dovevo senza fare backup prima come posso ripes
care i dati?
> gia committato ovviamente
> carlo
>|||Mike, I believe he's Italian (I recognize the writing since I'm Italian too)
.
I think he's saying he updated some data without backing up his database fir
st.
Now he thinks he messed up and wants to uncommit those changes.
Carlo, non e eventuale senza backup.
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:ey%
23DQPncFHA.4040@.TK2MSFTNGP14.phx.gbl...
Usted habla ingls?
(Also, pick a single newsgroup to post to.)
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Carlo wrote:
ho fatto un update che non dovevo senza fare backup prima come posso
ripescare i dati?
gia committato ovviamente
carlo|||Thank you all for Translation.
Carlo,
All on to tibor,
You can see the database before update Provided you have the below :-
1. Datbase must be in FULL recovery mode
2. Full database backup
3. All transaction log backups
If you passed the above then you can do a Point in time recovery until you
update the data:-
1. Perform a Transaction log backup in your database.
2. Create a new database
3. Restore the full database backup WITH NORECOVERY option into the new
database
4. Restore the subsequent transaction log backups till the last (DO not
restore last) with NORECOVERY option
5. Restore the Last Transaction log backup with Recovery option and STOPAT
='Date and time"
Refer RESTORE database/Log in books online for more information
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:esihFlncFHA.2180@.TK2MSFTNGP12.phx.gbl...
> Translated by bablefish:
> I have made update that I did not have without to make before backup as I
> can find again the data?
> Probably not, if you don't have any backups at all. Do you have
> transaction log backups?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Carlo" <carletto.mNOSPAM@.gmail.com> wrote in message
> news:OnD6BLncFHA.2664@.TK2MSFTNGP15.phx.gbl...
>|||Out of curiosity, would this restore up to the last complete transaction up
to the point in time specified but leave any transactions that bridge the
time un-applied (I would hope so)? And I would think maybe a log reader
would be helpful to pinpoint the EXACT time. Just plugging in a time because
it was "about 8:15 when it happened" doesn't seem like a great idea.
Bob Castleman
DBA Poseur.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OY95kSqcFHA.3504@.TK2MSFTNGP12.phx.gbl...
> Thank you all for Translation.
> Carlo,
> All on to tibor,
> You can see the database before update Provided you have the below :-
> 1. Datbase must be in FULL recovery mode
> 2. Full database backup
> 3. All transaction log backups
> If you passed the above then you can do a Point in time recovery until you
> update the data:-
> 1. Perform a Transaction log backup in your database.
> 2. Create a new database
> 3. Restore the full database backup WITH NORECOVERY option into the new
> database
> 4. Restore the subsequent transaction log backups till the last (DO not
> restore last) with NORECOVERY option
> 5. Restore the Last Transaction log backup with Recovery option and STOPAT
> ='Date and time"
> Refer RESTORE database/Log in books online for more information
> Thanks
> Hari
> SQL Server MVP
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:esihFlncFHA.2180@.TK2MSFTNGP12.phx.gbl...
>|||Yes, uncommitted transactions will be rolled back. And, yes a log mining too
l is good to have to
pinpoint the time. An option is to restore the same last log backup several
times with standby and
STOPAT pushing the time forward a little bit each time:
http://www.karaszi.com/SQLServer/in...veral_times.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Bob Castleman" <nomail@.here> wrote in message news:%23MAq5ErcFHA.720@.TK2MSFTNGP15.phx.gbl..
.
> Out of curiosity, would this restore up to the last complete transaction u
p to the point in time
> specified but leave any transactions that bridge the time un-applied (I wo
uld hope so)? And I
> would think maybe a log reader would be helpful to pinpoint the EXACT time
. Just plugging in a
> time because it was "about 8:15 when it happened" doesn't seem like a grea
t idea.
> Bob Castleman
> DBA Poseur.
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:OY95kSqcFHA.3504@.TK2MSFTNGP12.phx.gbl...
>