Record Locks: run

Showing posts with label run. Show all posts

Wednesday, March 21, 2012

Recover SQL Database from suspect status

Hi I'm trying to recover database from a suspect status but when I run this
command:
sp_resetstatus webc
sql return me this message:
Prior to updating sysdatabases entry for database 'webc', mode = 0 and
status = 1073741840 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already
correctly reset. No error and no changes made.
What is it= What can I do to recover DB?
Thanks.
--
--
Filippo MacchiHi
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
Have you tried to restart SQL Server? Aren't you still available to see your
data?
It seems you have to set your database in emergency mode
update sysdatabases set status=32768 where name='your name'
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> Hi I'm trying to recover database from a suspect status but when I run
this
> command:
> sp_resetstatus webc
> sql return me this message:
> Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> status = 1073741840 (status suspect_bit = 0).
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
> What is it= What can I do to recover DB?
> Thanks.
> --
> --
> Filippo Macchi
>|||Hi,
Stop and start the SQL server and try accessing the webc database
use webc
go
select * from sysobjects
If it still gives the error then go thru the below informations:-
Details:-
Suspect database may be due to below reasons.
1. MDF or LDF files may be used during the SQL Server service startup
2. LDF file might be corrupt or immediate power shutdown caused the LDF to
corrupt
3. MDF file - Page allocations issue
For the point 1.
Just Run sp_resetstatus <dbname> and restart SQL server (This you have done
already)
For the point 2. ( LDF file might be corrupt or immediate power shutdown
caused the LDF to corrupt)
a. Start SQL Server in emergency mode
Setting the database status to emergency mode tells SQL Server to skip
automatic recovery and lets you access the data.
To get your data, use this script:
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = 'webc'
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
You might be able to use bulk copy program (bcp), simple SELECT commands, or
use DTS to extract
your data while the database is in emergency mode.
After this database will be usable with out transaction log. AFter this
create a new database and use DTS to transfer objects and data
For point 3. Very critical error , try executing DBCC CHECKDB with
REPAIR_REBUILD option. If the problem is not rectified try
with restore from Backup or contact Microsoft support.
Thanks
Hari
MCDBA
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> Hi I'm trying to recover database from a suspect status but when I run
this
> command:
> sp_resetstatus webc
> sql return me this message:
> Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> status = 1073741840 (status suspect_bit = 0).
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
> What is it= What can I do to recover DB?
> Thanks.
> --
> --
> Filippo Macchi
>|||I run the command and received this message, is it correct?:
Server: Msg 259, Level 16, State 2, Line 1
Ad hoc updates to system catalogs are not enabled. The system administrator
must reconfigure SQL Server to allow this.
"Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
news:uWWEfRWQEHA.3660@.tk2msftngp13.phx.gbl...
> Hi
> > No row in sysdatabases was updated because mode and status are already
> > correctly reset. No error and no changes made.
> Have you tried to restart SQL Server? Aren't you still available to see
your
> data?
> It seems you have to set your database in emergency mode
> update sysdatabases set status=32768 where name='your name'
>
> "Azkaban" <azkaban74@.libero.it> wrote in message
> news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> > Hi I'm trying to recover database from a suspect status but when I run
> this
> > command:
> >
> > sp_resetstatus webc
> >
> > sql return me this message:
> >
> > Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> > status = 1073741840 (status suspect_bit = 0).
> > No row in sysdatabases was updated because mode and status are already
> > correctly reset. No error and no changes made.
> >
> > What is it= What can I do to recover DB?
> >
> > Thanks.
> >
> > --
> > --
> > Filippo Macchi
> >
> >
>|||Hi
Sp_configure "allow updates", 1
go
Reconfigure with override
go
Update sysdatabases set status = 32768 where name = 'yourname'
go
Sp_configure "allow updates", 0
go
Reconfigure with override
go
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uyJxIXWQEHA.904@.TK2MSFTNGP12.phx.gbl...
> I run the command and received this message, is it correct?:
> Server: Msg 259, Level 16, State 2, Line 1
> Ad hoc updates to system catalogs are not enabled. The system
administrator
> must reconfigure SQL Server to allow this.
>
> "Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
> news:uWWEfRWQEHA.3660@.tk2msftngp13.phx.gbl...
> > Hi
> > > No row in sysdatabases was updated because mode and status are already
> > > correctly reset. No error and no changes made.
> > Have you tried to restart SQL Server? Aren't you still available to see
> your
> > data?
> >
> > It seems you have to set your database in emergency mode
> > update sysdatabases set status=32768 where name='your name'
> >
> >
> >
> > "Azkaban" <azkaban74@.libero.it> wrote in message
> > news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> > > Hi I'm trying to recover database from a suspect status but when I run
> > this
> > > command:
> > >
> > > sp_resetstatus webc
> > >
> > > sql return me this message:
> > >
> > > Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> > > status = 1073741840 (status suspect_bit = 0).
> > > No row in sysdatabases was updated because mode and status are already
> > > correctly reset. No error and no changes made.
> > >
> > > What is it= What can I do to recover DB?
> > >
> > > Thanks.
> > >
> > > --
> > > --
> > > Filippo Macchi
> > >
> > >
> >
> >
>|||Hi,
Can you go thru the steps specified by me in the previous post. That
contains the detailed information on recovering from the suspect status.
Thanks
Hari
MCDBA
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uyJxIXWQEHA.904@.TK2MSFTNGP12.phx.gbl...
> I run the command and received this message, is it correct?:
> Server: Msg 259, Level 16, State 2, Line 1
> Ad hoc updates to system catalogs are not enabled. The system
administrator
> must reconfigure SQL Server to allow this.
>
> "Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
> news:uWWEfRWQEHA.3660@.tk2msftngp13.phx.gbl...
> > Hi
> > > No row in sysdatabases was updated because mode and status are already
> > > correctly reset. No error and no changes made.
> > Have you tried to restart SQL Server? Aren't you still available to see
> your
> > data?
> >
> > It seems you have to set your database in emergency mode
> > update sysdatabases set status=32768 where name='your name'
> >
> >
> >
> > "Azkaban" <azkaban74@.libero.it> wrote in message
> > news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> > > Hi I'm trying to recover database from a suspect status but when I run
> > this
> > > command:
> > >
> > > sp_resetstatus webc
> > >
> > > sql return me this message:
> > >
> > > Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> > > status = 1073741840 (status suspect_bit = 0).
> > > No row in sysdatabases was updated because mode and status are already
> > > correctly reset. No error and no changes made.
> > >
> > > What is it= What can I do to recover DB?
> > >
> > > Thanks.
> > >
> > > --
> > > --
> > > Filippo Macchi
> > >
> > >
> >
> >
>

Tuesday, March 20, 2012

Recover SQL Database from suspect status

Friday, March 9, 2012

Recover data with updated transaction Log only

I am newbie in MS SQL Server, today I wrongly run a script to clear all data of a table, and the backup is one month ago. Can I just use the existing transaction log to rollback what I have done today? If yes, how to do so.
The data is very important, please help.
Regards,
Thomas
If you are using the FULL recovery model, you can backup your transaction
log, restore the database (perhaps with a different name or server) and
apply the log up to the point of the problem. You can then extract the lost
data.
Your only other option is to use a utility like Log Explorer
www.lumigent.com to recover data from the log, if it is available.
Hope this helps.
Dan Guzman
SQL Server MVP
"Thomas Tsang" <thomast@.hkc.net> wrote in message
news:O1hYtVylEHA.2492@.TK2MSFTNGP15.phx.gbl...
I am newbie in MS SQL Server, today I wrongly run a script to clear all data
of a table, and the backup is one month ago. Can I just use the existing
transaction log to rollback what I have done today? If yes, how to do so.
The data is very important, please help.
Regards,
Thomas
|||I can retored the data that is one month ago, but what I need is the current
data.
I have readingthe doc about Log Explorer, but how can I check if the data is
still available in the log and can be recovered by the Log Explorer?
Regards,
Thomas
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:%23DZrzhylEHA.3476@.tk2msftngp13.phx.gbl g...
> If you are using the FULL recovery model, you can backup your transaction
> log, restore the database (perhaps with a different name or server) and
> apply the log up to the point of the problem. You can then extract the
lost
> data.
> Your only other option is to use a utility like Log Explorer
> www.lumigent.com to recover data from the log, if it is available.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Thomas Tsang" <thomast@.hkc.net> wrote in message
> news:O1hYtVylEHA.2492@.TK2MSFTNGP15.phx.gbl...
> I am newbie in MS SQL Server, today I wrongly run a script to clear all
data
> of a table, and the backup is one month ago. Can I just use the existing
> transaction log to rollback what I have done today? If yes, how to do so.
> The data is very important, please help.
> Regards,
> Thomas
>
|||You'll need to run the utility to see if it is still available.
Hope this helps.
Dan Guzman
SQL Server MVP
"Thomas Tsang" <thomast@.hkc.net> wrote in message
news:uXa0GsylEHA.1656@.TK2MSFTNGP09.phx.gbl...
>I can retored the data that is one month ago, but what I need is the
>current
> data.
> I have readingthe doc about Log Explorer, but how can I check if the data
> is
> still available in the log and can be recovered by the Log Explorer?
> Regards,
> Thomas
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
> news:%23DZrzhylEHA.3476@.tk2msftngp13.phx.gbl g...
> lost
> data
>
|||i know, but the trial version of Log Explorer is restricted to access my
database and the log...
Any ideas?
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:ukfRFyylEHA.3544@.TK2MSFTNGP15.phx.gbl g...[vbcol=seagreen]
> You'll need to run the utility to see if it is still available.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Thomas Tsang" <thomast@.hkc.net> wrote in message
> news:uXa0GsylEHA.1656@.TK2MSFTNGP09.phx.gbl...
data[vbcol=seagreen]
transaction[vbcol=seagreen]
existing
>
|||You can get an idea of whats in the log using the undocumented fn_dblog
system function:
SELECT * FROM ::fn_dblog(null, null)
Hope this helps.
Dan Guzman
SQL Server MVP
"Thomas Tsang" <thomast@.hkc.net> wrote in message
news:%23hnAi6ylEHA.1244@.TK2MSFTNGP15.phx.gbl...
>i know, but the trial version of Log Explorer is restricted to access my
> database and the log...
> Any ideas?
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
> news:ukfRFyylEHA.3544@.TK2MSFTNGP15.phx.gbl g...
> data
> transaction
> existing
>
|||Thx for your information, and the attached is the return data. I find that
the value of the column Checkpoint Begin in first record is match with the
time i start execute the wrong query, does it mean that the data can be get
back using Log Explorer?
Regards,
Thomas
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:%23MiraJzlEHA.1672@.TK2MSFTNGP14.phx.gbl g...[vbcol=seagreen]
> You can get an idea of whats in the log using the undocumented fn_dblog
> system function:
> SELECT * FROM ::fn_dblog(null, null)
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Thomas Tsang" <thomast@.hkc.net> wrote in message
> news:%23hnAi6ylEHA.1244@.TK2MSFTNGP15.phx.gbl...
do
>
|||Attached file missing in previous mail...
"Thomas Tsang" <thomast@.hkc.net> bl
news:emIuHXzlEHA.2492@.TK2MSFTNGP15.phx.gbl g...
> Thx for your information, and the attached is the return data. I find
that
> the value of the column Checkpoint Begin in first record is match with the
> time i start execute the wrong query, does it mean that the data can be
get[vbcol=seagreen]
> back using Log Explorer?
> Regards,
> Thomas
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
> news:%23MiraJzlEHA.1672@.TK2MSFTNGP14.phx.gbl g...
my[vbcol=seagreen]
the[vbcol=seagreen]
Explorer?[vbcol=seagreen]
server)[vbcol=seagreen]
extract[vbcol=seagreen]
clear[vbcol=seagreen]
to
> do
>
begin 666 result.txt
M0W5R<F5N="!,4TX@.(" @.(" @.(" @.("!/<&5R871I;VX@.(" @.(" @.(" @.(" @.
M(" @.($-O;G1E>'0@.(" @.(" @.(" @.(" @.(" @.(" @.5')A;G-A8W1I;VX@.240@.
M5&%G($)I=',@.3&]G(%)E8V]R9"!,96YG=&@.@.4')E=FEO=7,@.3%-.(" @.(" @.
M(" @.("!&;&%G($)I=',@.3V)J96-T($YA;64@.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M("!);F1E>"!.86UE(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.4&%G92!)1" @.(" @.("!3;&]T($E$(%!R979I;W5S(%!A9V4@.
M3%-.(" @.(" @.3V9F<V5T(&EN(%)O=R!.=6T@.16QE;65N=',@.16QE;65N="!%
M;&5M96YT($QE;F=T:"!/9F9S970@.4F]W($1A=&$@.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.($-H96-K<&]I;G0@.0F5G:6X@.(" @.(" @.($-(2U!4($)E9VEN
M($1"(%9E<G-I;VX@.36%X(%A$15-)1" @.(" @.3G5M(%1R86YS86-T:6]N<R!4
M<F%N<V%C=&EO;B!#='(@.5')A;G-A8W1I;VX@.240@.:6X@.0TA+4%0@.5')A;G-A
M8W1I;VX@.4W1A='5S($-(2U!4($)E9VEN($Q33B @.(" @.(" @.5')A;G-A8W1I
M;VX@.4W1A=&4@.(" @.5')A;G-A8W1I;VX@.5'EP92!,87-T($Q33B @.(" @.(" @.
M(" @.(" @.(%)E8V]R9"!#;W5N="!">71E<R!5<V5D("!">71E<R!297-E<G9E
M9"!#:&5C:W!O:6YT($5N9" @.(" @.(" @.("!#2$M05"!%;F0@.1$(@.5F5R<VEO
M;B!-:6YI;75M($Q33B @.(" @.(" @.(" @.($1I<G1Y(%!A9V5S($]L9&5S="!2
M97!L:6-A=&5D($)E9VEN($Q33B!.97AT(%)E<&QI8V%T960@.16YD($Q33 B!,
M87-T($1I<W1R:6)U=&5D($)A8VMU<"!%;F0@.3%-.($QA<W0@.1&ES=')I8G5T
M960@.16YD($Q33B!397)V97(@.54E$("!5240@.(" @.(" @.("!34$E$(" @.(" @.
M("!"96=I;FQO9R!3=&%T=7,@.0F5G:6X@.5&EM92 @.(" @.(" @.(" @.(" @.5')A
M;G-A8W1I;VX@.3F%M92 @.(" @.16YD(%1I;64@.(" @.(" @.(" @.(" @.(" @.5')A
M;G-A8W1I;VX@.0F5G:6X@.(" @.("!297!L:6-A=&5D(%)E8V]R9',@.3VQD97-T
M($%C=&EV92!,4TX@.(" @.("!397)V97(@.3F%M92 @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.("!$871A8F%S92!.86UE(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.("!-87)K($YA;64@.(" @.(" @.(" @.(" @.(" @.(" @.(" @.("!-87-T97(@.
M6$1%4TE$("!-87-T97(@.1$))1"!0<F5P;&]G($)E9VEN($Q33B @.(" @.(%!R
M97!A<F4@.5&EM92 @.(" @.(" @.(" @.(%!R979I;W5S(%-A=F5P;VEN=" @.(" @.
M4V%V97!O:6YT($YA;64@.(" @.(" @.4F]W8FET<R!&:7)S="!":70@.4F]W8FET
M<R!":70@.0V]U;G0@.4F]W8FET<R!":70@.5F%L=64@.3%-.(&)E9F]R92!W<FET
M97,@.(" @.("!086=E<R!7<FET=&5N(%!A9V4@.0V]U;G1E<B!"=69W<FET92!0
M86=E($ED($1A=&$@.4&%G97,@.1&5L=&$@.4F5S97)V960@.4&%G9 7,@.1&5L=&$@.
M57-E9"!086=E<R!$96QT82!$871A(%)O=W,@.1&5L=&$@.0V]M;6%N9"!4>7!E
M(%!U8FQI8V%T:6]N($E$($%R=&EC;&4@.240@.(%!A<G1I86P@.4W1A='5S($-O
M;6UA;F0@.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.($)Y=&4@.3V9F
M<V5T($YE=R!686QU92!/;&0@.5F%L=64@.3F5W(%-P;&ET(%!A9V4@.4F]W<R!$
M96QE=&5D($)Y=&5S($9R965D($-)(%1A8FQE($ED($-)($EN9&5X($ED($9I
M;&5'<F]U<"!)1" -"BTM+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM("TM
M+2TM+2TM+2TM+2TM("TM+2TM+2TM("TM+2TM+2TM+2TM+2TM+ 2TM("TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM("TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+2T@.+ 2TM+2TM+2 M
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+2T@.+ 2TM+2TM+2TM
M+2TM("TM+2TM+2T@.+2TM+2TM+2TM+2TM+2T@.+2TM+2TM("TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2 M+2TM+2TM+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+2TM( "TM+2TM
M+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM("TM+2TM+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM("TM+2TM+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+ 2TM+2T@.+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2T@.
M+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2T@.+2TM+2TM
M+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2 M+2TM+2TM
M+2TM+2 M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+ 2TM
M+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2 M
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2T@.+ 2TM+2TM+2TM
M+2T@.+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM("TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM("TM+2TM+2TM+2TM+2TM+2TM+2TM("TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM("TM+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+ 2TM+2TM+2TM
M+2TM+2TM("TM+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2T@.+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2T@.+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+2TM+2TM+2TM("TM+ 2TM+2TM+2TM
M+2TM+2TM("TM+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+ 2TM+2TM("TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM
M+2T@.+2TM+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2TM("TM+2TM+2TM
M+2TM+2TM+2TM+2TM("TM+2TM+2TM+2TM+2TM+2T@.+2TM+2TM+ 2TM+2TM+2TM
M("TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2 M+2TM
M+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+ 2TM+2TM+2TM
M+2TM+2 M+2TM+2TM+2TM+2 M+2TM+2TM+2T@.+2TM+2TM+2TM("TM+2TM+2TM
M+2TM+2TM("TM+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2 M
M+2TM+2TM+2TM+2 M+2TM+2TM+2TM+2T@.#0HP,# P,3,T83HP,# P,3(V8CHP
M,# Q($Q/4%]"14=)3E]#2U!4(" @.(" @.(" @.(" @.3$-87TY53$P@.(" @.(" @.
M(" @.(" @.(" @.(" P,# P.C P,# P,# P(" P># P,# @.(" Y-B @.(" @.(" @.
M(" @.(" @.(" P,# P,3,T.3HP,# P,C4X-CHP,# R(#!X,# P," @.("!.54Q,
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.
M(" @.($Y53$P@.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.
M(" @.($Y53$P@.(" @.(" @.("!.54Q,(" @.($Y53$P@.(" @.(" @.(" @.($Y53$P@.
M("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.,C P-"\P.2\Q
M," Q,CHU-3HU-#HV,#<@.-3,Y(" @.(" @.(" @.(" @.(" @.(" @.(" P,# P.C S
M-C=A-3DU("!.54Q,(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.("!.54Q,
M(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.3E5,3" @.
M(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.
M(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.
M($Y53$P@.(" @.(" @.($Y53$P@.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.
M(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.
M(" @.(" @.3E5,3" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M($Y53$P@.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.
M(" @.($Y53$P@.(" @.(" @.($Y53$P@.(" @.(" @.($Y53$P@.(" @.(" @.(" @.("!.
M54Q,(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.("!.
M54Q,(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.
M($Y53$P@.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.($Y5
M3$P@.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.($Y53$P@.(" @.(" @.
M($Y53$P@.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.
M(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.
M("!.54Q,(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.("!.54Q,(" @.
M(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.
M(" @.3E5,3" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.
M(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.($Y5
M3$P@.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.3E5,
M3" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.3E5,3" @.(" @.($Y53$P@.
M(" @.("!.54Q,(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.3E5,3" @.(" @.(" @.
M3E5,3" @.(" @.(" @.3E5,3" @.(" @.(" @.3E5,3 T*,# P,#$S-&$Z,# P,#$R
M-F,Z,# P,2!,3U!?14Y$7T-+4%0@.(" @.(" @.(" @.(" @.($Q#6%].54Q,(" @.
M(" @.(" @.(" @.(" @.(" @.,# P,#HP,# P,# P," @.,'@.P,# P(" @.,3,V(" @.
M(" @.(" @.(" @.(" @.,# P,#$S-&$Z,# P,#$R-F(Z,# P,2 P># P,# @.(" @.
M3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.
M(" @.(" @.("!.54Q,(" @.($Y53$P@.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.
M(" @.(" @.("!.54Q,(" @.(" @.(" @.3E5,3" @.("!.54Q,(" @.(" @.(" @.("!.
M54Q,(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.
M(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.(" @.(" @.3E5,
M3" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.
M3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.($Y5
M3$P@.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.3E5,
M3" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.
M(" @.("!.54Q,(" @.(" @.("!.54Q,(" @.(" @.(" @.(" R,# T+S Y+S$P(#$R
M.C4V.C P.C(P," U,SD@.(" @.(" @.(" @.(" @.(" @.(" P,# P,3,T83HP,# P
M,3(V8CHP,# Q(#DR-2 @.(" @.(" @.(# P,# P,# P.C P,# P,# P.C P,# @.
M(" @.(" P,# P,# P,#HP,# P,# P,#HP,# P(" P,# P,# P,#HP,# P,# P
M,#HP,# P(" @.(" @.(" @.(# P,# P,# P.C P,# P,# P.C P,# @.("!.54Q,
M(" @.(" @.("!.54Q,(" @.(" @.("!.54Q,(" @.(" @.("!.54Q,(" @.(" @.(" @.
M(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.
M(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.
M(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.
M("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.(" @.(" @.("!.54Q,(" @.
M(" @.("!.54Q,(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.
M(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.
M(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.3E5,
M3" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.("!.54Q,(" @.
M(" @.(" @.($Y53$P@.(" @.(" @.("!.54Q,(" @.(" @.(" @.(" @.($Y53$P@.(" @.
M(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.(" @.
M("!.54Q,(" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.
M($Y53$P@.(" @.(" @.($Y53$P@.(" @.(" @.(" @.($Y53$P@.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.(" @.
M(" @.(" @.(" @.(" @.(" @.(" @.(" @.($Y53$P@.(" @.(" @.($Y53$P@.(" @.("!.
M54Q,(" @.(" @.3E5,3" @.(" @.(" @.(" @.3E5,3" @.(" @.(" @.($Y53$P@.(" @.
M(" @.($Y53$P@.(" @.(" @.($Y53$P@.(" @.(" @.($Y53$P-"@.T**#(@.<F]W*',I
,(&%F9F5C=&5D*0T*
`
end
|||It looks like your database is in the SIMPLE recovery model and the log was
truncated. Some of the data might still be in the log but there's no
guarantee. I don't know of a way to find out without running the utility.
Hope this helps.
Dan Guzman
SQL Server MVP
"Thomas Tsang" <thomast@.hkc.net> wrote in message
news:OUE$UbzlEHA.3428@.TK2MSFTNGP14.phx.gbl...
> Attached file missing in previous mail...
> "Thomas Tsang" <thomast@.hkc.net> bl
> news:emIuHXzlEHA.2492@.TK2MSFTNGP15.phx.gbl g...
> that
> get
> my
> the
> Explorer?
> server)
> extract
> clear
> to
>
>
|||Agree with Dan. You can try attaching the online log and look for the
records in recycled area. It may still be there depending the db activities.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u$spsqzlEHA.2380@.TK2MSFTNGP14.phx.gbl...
> It looks like your database is in the SIMPLE recovery model and the log
was[vbcol=seagreen]
> truncated. Some of the data might still be in the log but there's no
> guarantee. I don't know of a way to find out without running the utility.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Thomas Tsang" <thomast@.hkc.net> wrote in message
> news:OUE$UbzlEHA.3428@.TK2MSFTNGP14.phx.gbl...
fn_dblog[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
how
>

Recover data from Database Transaction Log

Hi Everyone
I have a problem with one of our databases. One of our developers run a
query on a live database which resulted in the deletion of several records
in a group of tables. No database Backup is available for the data erased
and so comes my question, is there any way of rolling back those
transactions from the database logs?
Thanks in advance for your attentionJohn Grisham wrote:
> Hi Everyone
> I have a problem with one of our databases. One of our developers run a
> query on a live database which resulted in the deletion of several records
> in a group of tables. No database Backup is available for the data erased
> and so comes my question, is there any way of rolling back those
> transactions from the database logs?
> Thanks in advance for your attention
>
What recovery model?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The idea is to recover the lost data in any way from a detached database,
and later re introduce the recovered data in the live database. The erased
records correspond to tariff data fro some products and offer variations
during the whole year 2006.
Thanks in advance...
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AD3FF2.1060900@.realsqlguy.com...
> John Grisham wrote:
> What recovery model?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||John Grisham wrote:
> The idea is to recover the lost data in any way from a detached database
,
> and later re introduce the recovered data in the live database. The erased
> records correspond to tariff data fro some products and offer variations
> during the whole year 2006.
>
Again, what recovery model? Simple, Bulk-Logged, or Full?
If Full, you should be able to take a backup of the database, followed
by a log backup, then use the STOPAT clause of the RESTORE command to
restore the database and log to a point just prior to the deletion.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The recovery model is set to simple.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AD4361.6090506@.realsqlguy.com...
> John Grisham wrote:
> Again, what recovery model? Simple, Bulk-Logged, or Full?
> If Full, you should be able to take a backup of the database, followed by
> a log backup, then use the STOPAT clause of the RESTORE command to restore
> the database and log to a point just prior to the deletion.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||John Grisham wrote:
> The recovery model is set to simple.
>
Not much you can do then... Backup, backup, backup, it can't be said
enough times... You really should read up on the various recovery
models, and understand how they can benefit you.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Ok, thanks for your attention and kind advice
Regards
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AE2968.9070106@.realsqlguy.com...
> John Grisham wrote:
> Not much you can do then... Backup, backup, backup, it can't be said
> enough times... You really should read up on the various recovery models,
> and understand how they can benefit you.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Recover data from Database Transaction Log

Hi Everyone
I have a problem with one of our databases. One of our developers run a
query on a live database which resulted in the deletion of several records
in a group of tables. No database Backup is available for the data erased
and so comes my question, is there any way of rolling back those
transactions from the database logs?
Thanks in advance for your attention
John Grisham wrote:
> Hi Everyone
> I have a problem with one of our databases. One of our developers run a
> query on a live database which resulted in the deletion of several records
> in a group of tables. No database Backup is available for the data erased
> and so comes my question, is there any way of rolling back those
> transactions from the database logs?
> Thanks in advance for your attention
>
What recovery model?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||The idea is to recover the lost data in any way from a detached database,
and later re introduce the recovered data in the live database. The erased
records correspond to tariff data fro some products and offer variations
during the whole year 2006.
Thanks in advance...
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AD3FF2.1060900@.realsqlguy.com...
> John Grisham wrote:
> What recovery model?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||John Grisham wrote:
> The idea is to recover the lost data in any way from a detached database,
> and later re introduce the recovered data in the live database. The erased
> records correspond to tariff data fro some products and offer variations
> during the whole year 2006.
>
Again, what recovery model? Simple, Bulk-Logged, or Full?
If Full, you should be able to take a backup of the database, followed
by a log backup, then use the STOPAT clause of the RESTORE command to
restore the database and log to a point just prior to the deletion.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||The recovery model is set to simple.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AD4361.6090506@.realsqlguy.com...
> John Grisham wrote:
> Again, what recovery model? Simple, Bulk-Logged, or Full?
> If Full, you should be able to take a backup of the database, followed by
> a log backup, then use the STOPAT clause of the RESTORE command to restore
> the database and log to a point just prior to the deletion.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||John Grisham wrote:
> The recovery model is set to simple.
>
Not much you can do then... Backup, backup, backup, it can't be said
enough times... You really should read up on the various recovery
models, and understand how they can benefit you.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Ok, thanks for your attention and kind advice
Regards
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AE2968.9070106@.realsqlguy.com...
> John Grisham wrote:
> Not much you can do then... Backup, backup, backup, it can't be said
> enough times... You really should read up on the various recovery models,
> and understand how they can benefit you.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Recover data from Database Transaction Log

Hi Everyone
I have a problem with one of our databases. One of our developers run a
query on a live database which resulted in the deletion of several records
in a group of tables. No database Backup is available for the data erased
and so comes my question, is there any way of rolling back those
transactions from the database logs?
Thanks in advance for your attentionJohn Grisham wrote:
> Hi Everyone
> I have a problem with one of our databases. One of our developers run a
> query on a live database which resulted in the deletion of several records
> in a group of tables. No database Backup is available for the data erased
> and so comes my question, is there any way of rolling back those
> transactions from the database logs?
> Thanks in advance for your attention
>
What recovery model?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The idea is to recover the lost data in any way from a detached database,
and later re introduce the recovered data in the live database. The erased
records correspond to tariff data fro some products and offer variations
during the whole year 2006.
Thanks in advance...
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AD3FF2.1060900@.realsqlguy.com...
> John Grisham wrote:
>> Hi Everyone
>> I have a problem with one of our databases. One of our developers run a
>> query on a live database which resulted in the deletion of several
>> records in a group of tables. No database Backup is available for the
>> data erased and so comes my question, is there any way of rolling back
>> those transactions from the database logs?
>> Thanks in advance for your attention
> What recovery model?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||John Grisham wrote:
> The idea is to recover the lost data in any way from a detached database,
> and later re introduce the recovered data in the live database. The erased
> records correspond to tariff data fro some products and offer variations
> during the whole year 2006.
>
Again, what recovery model? Simple, Bulk-Logged, or Full?
If Full, you should be able to take a backup of the database, followed
by a log backup, then use the STOPAT clause of the RESTORE command to
restore the database and log to a point just prior to the deletion.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The recovery model is set to simple.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AD4361.6090506@.realsqlguy.com...
> John Grisham wrote:
>> The idea is to recover the lost data in any way from a detached
>> database, and later re introduce the recovered data in the live database.
>> The erased records correspond to tariff data fro some products and offer
>> variations during the whole year 2006.
> Again, what recovery model? Simple, Bulk-Logged, or Full?
> If Full, you should be able to take a backup of the database, followed by
> a log backup, then use the STOPAT clause of the RESTORE command to restore
> the database and log to a point just prior to the deletion.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||John Grisham wrote:
> The recovery model is set to simple.
>
Not much you can do then... Backup, backup, backup, it can't be said
enough times... You really should read up on the various recovery
models, and understand how they can benefit you.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Ok, thanks for your attention and kind advice
Regards
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AE2968.9070106@.realsqlguy.com...
> John Grisham wrote:
>> The recovery model is set to simple.
> Not much you can do then... Backup, backup, backup, it can't be said
> enough times... You really should read up on the various recovery models,
> and understand how they can benefit you.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Wednesday, March 7, 2012

records wont delete

I have some records that will not delete, whenever I run a delete
statement in the Query analyzer, it never completes the statement, and
I am only deleting one record at a time. Can anyone tell me why a
record wouldn't delete?[posted and mailed, please reply in news]

alloowishus (alloowishus@.yahoo.com) writes:
> I have some records that will not delete, whenever I run a delete
> statement in the Query analyzer, it never completes the statement, and
> I am only deleting one record at a time. Can anyone tell me why a
> record wouldn't delete?

There are several possible reasons:

o The row you are trying to delete is locked by another process.
o There is a foreign-key constraint from a referencing table, and that
table is large, but the referencing column is not indexed, so
checking whether the row is deletable takes a very long time.
o A variation of the above, but the foreign-key relationship uses
cascading updates.
o The table has a DELETE trigger which takes a very long time to
execute.

To check for locking, issue an sp_who from another connection. If you see
a non-zero value in the Blk column, the process on that row is blocked by
the process in the Blk column.

To check the other, use sp_helpconstraint and sp_helptrigger to look
for constraints and triggers.

The above list is not necessarily exhaustive.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Saturday, February 25, 2012

Records disappearing Data/Preview tabs.

On "Data" tab I run the data. 3 records are returned. i.e.
Part# 12345 Philadelphia PA Qty 60
Part# 11223 Philadelphia PA Qty 100
Part# 11223 Bronx NY Qty 500
On "Preview" tab I see the following:
Part# 12345 Philadelphia PA 60
Part# 11223 Philadelphia PA 100
Customer break SUM 660
So, I loose the 3rd record in the detail section of the report
yet the totals sum up all 3 records.
I realize the 2nd & 3rd records have the same Part#.
None of the textboxes have "Hide Duplicates" checked off.
Can somebody explain to me what's happening?You arent grouping it by the Part# are you?
"BillB" <BillB@.discussions.microsoft.com> wrote in message
news:F9A6FA80-4F67-40D6-B9A8-1A9196B83CA4@.microsoft.com...
> On "Data" tab I run the data. 3 records are returned. i.e.
> Part# 12345 Philadelphia PA Qty 60
> Part# 11223 Philadelphia PA Qty 100
> Part# 11223 Bronx NY Qty 500
> On "Preview" tab I see the following:
> Part# 12345 Philadelphia PA 60
> Part# 11223 Philadelphia PA 100
>
> Customer break SUM 660
> So, I loose the 3rd record in the detail section of the report
> yet the totals sum up all 3 records.
> I realize the 2nd & 3rd records have the same Part#.
> None of the textboxes have "Hide Duplicates" checked off.
> Can somebody explain to me what's happening?
>|||Thanks for the reply.
Yes I am grouping it by the part #
the detail line is in a list and the customer total is an another list.
I'd expect it to total the Qty's on the detail line for the two records
with the identical Part#'s.
so part # 11223 would show 600 on the detail line not 100!
"Ben Watts" wrote:
> You arent grouping it by the Part# are you?
> "BillB" <BillB@.discussions.microsoft.com> wrote in message
> news:F9A6FA80-4F67-40D6-B9A8-1A9196B83CA4@.microsoft.com...
> > On "Data" tab I run the data. 3 records are returned. i.e.
> >
> > Part# 12345 Philadelphia PA Qty 60
> > Part# 11223 Philadelphia PA Qty 100
> > Part# 11223 Bronx NY Qty 500
> >
> > On "Preview" tab I see the following:
> >
> > Part# 12345 Philadelphia PA 60
> > Part# 11223 Philadelphia PA 100
> >
> >
> > Customer break SUM 660
> >
> > So, I loose the 3rd record in the detail section of the report
> > yet the totals sum up all 3 records.
> >
> > I realize the 2nd & 3rd records have the same Part#.
> >
> > None of the textboxes have "Hide Duplicates" checked off.
> >
> > Can somebody explain to me what's happening?
> >
> >
>
>|||I may be understanding it wrong, but it sounds like it is only showing one
because of the group. It will still total everything it finds because of
the detail, but if you are showing your group then it will only bring back
one record. Are you showing any detail in the group. Or is it all showing
in the details?
"BillB" <BillB@.discussions.microsoft.com> wrote in message
news:A43A1A2D-2F40-4B17-A01D-D4E289428D6A@.microsoft.com...
> Thanks for the reply.
> Yes I am grouping it by the part #
> the detail line is in a list and the customer total is an another list.
> I'd expect it to total the Qty's on the detail line for the two records
> with the identical Part#'s.
> so part # 11223 would show 600 on the detail line not 100!
> "Ben Watts" wrote:
>> You arent grouping it by the Part# are you?
>> "BillB" <BillB@.discussions.microsoft.com> wrote in message
>> news:F9A6FA80-4F67-40D6-B9A8-1A9196B83CA4@.microsoft.com...
>> > On "Data" tab I run the data. 3 records are returned. i.e.
>> >
>> > Part# 12345 Philadelphia PA Qty 60
>> > Part# 11223 Philadelphia PA Qty 100
>> > Part# 11223 Bronx NY Qty 500
>> >
>> > On "Preview" tab I see the following:
>> >
>> > Part# 12345 Philadelphia PA 60
>> > Part# 11223 Philadelphia PA 100
>> >
>> >
>> > Customer break SUM 660
>> >
>> > So, I loose the 3rd record in the detail section of the report
>> > yet the totals sum up all 3 records.
>> >
>> > I realize the 2nd & 3rd records have the same Part#.
>> >
>> > None of the textboxes have "Hide Duplicates" checked off.
>> >
>> > Can somebody explain to me what's happening?
>> >
>> >
>>|||Hi Ben
In the detail list I show
part# 12345 Qty= 60 this is correct
part#11223 Qty is showing 100 which is not correct.
remember the 2nd record is part # 11223 with qty = 100
the third record does not show in the detail at all but the 3rd
record
has a qty of 500.
so i should see in the detail:
Part # 11223 qty=600 because it should combine the 2nd record of 100 &
the 3rd record with the same Part# of 500.
the customer total shows correctly qty 660.
hope this makes it clearer & thanks fro the help.
"Ben Watts" wrote:
> I may be understanding it wrong, but it sounds like it is only showing one
> because of the group. It will still total everything it finds because of
> the detail, but if you are showing your group then it will only bring back
> one record. Are you showing any detail in the group. Or is it all showing
> in the details?
> "BillB" <BillB@.discussions.microsoft.com> wrote in message
> news:A43A1A2D-2F40-4B17-A01D-D4E289428D6A@.microsoft.com...
> > Thanks for the reply.
> > Yes I am grouping it by the part #
> > the detail line is in a list and the customer total is an another list.
> > I'd expect it to total the Qty's on the detail line for the two records
> > with the identical Part#'s.
> > so part # 11223 would show 600 on the detail line not 100!
> >
> > "Ben Watts" wrote:
> >
> >> You arent grouping it by the Part# are you?
> >>
> >> "BillB" <BillB@.discussions.microsoft.com> wrote in message
> >> news:F9A6FA80-4F67-40D6-B9A8-1A9196B83CA4@.microsoft.com...
> >> > On "Data" tab I run the data. 3 records are returned. i.e.
> >> >
> >> > Part# 12345 Philadelphia PA Qty 60
> >> > Part# 11223 Philadelphia PA Qty 100
> >> > Part# 11223 Bronx NY Qty 500
> >> >
> >> > On "Preview" tab I see the following:
> >> >
> >> > Part# 12345 Philadelphia PA 60
> >> > Part# 11223 Philadelphia PA 100
> >> >
> >> >
> >> > Customer break SUM 660
> >> >
> >> > So, I loose the 3rd record in the detail section of the report
> >> > yet the totals sum up all 3 records.
> >> >
> >> > I realize the 2nd & 3rd records have the same Part#.
> >> >
> >> > None of the textboxes have "Hide Duplicates" checked off.
> >> >
> >> > Can somebody explain to me what's happening?
> >> >
> >> >
> >>
> >>
> >>
>
>|||Go to your detail line and right click on the three lines.then click edit
group. Even in the detail you can group it and it will hide records. Make
sure there is nothing in "Group On" Expression. I am betting you have
something in that. If so just delete it and leave it blank. I just
recreated that with one of my own reports and when I put something in the
"group on" in the details line it hid alot of records.
"BillB" <BillB@.discussions.microsoft.com> wrote in message
news:A3A0CAAD-7B02-4E76-A03A-802C0D3A34EF@.microsoft.com...
> Hi Ben
> In the detail list I show
> part# 12345 Qty= 60 this is correct
> part#11223 Qty is showing 100 which is not correct.
> remember the 2nd record is part # 11223 with qty = 100
> the third record does not show in the detail at all but the 3rd
> record
> has a qty of 500.
> so i should see in the detail:
> Part # 11223 qty=600 because it should combine the 2nd record of 100 &
> the 3rd record with the same Part# of 500.
> the customer total shows correctly qty 660.
> hope this makes it clearer & thanks fro the help.
> "Ben Watts" wrote:
>> I may be understanding it wrong, but it sounds like it is only showing
>> one
>> because of the group. It will still total everything it finds because of
>> the detail, but if you are showing your group then it will only bring
>> back
>> one record. Are you showing any detail in the group. Or is it all
>> showing
>> in the details?
>> "BillB" <BillB@.discussions.microsoft.com> wrote in message
>> news:A43A1A2D-2F40-4B17-A01D-D4E289428D6A@.microsoft.com...
>> > Thanks for the reply.
>> > Yes I am grouping it by the part #
>> > the detail line is in a list and the customer total is an another list.
>> > I'd expect it to total the Qty's on the detail line for the two records
>> > with the identical Part#'s.
>> > so part # 11223 would show 600 on the detail line not 100!
>> >
>> > "Ben Watts" wrote:
>> >
>> >> You arent grouping it by the Part# are you?
>> >>
>> >> "BillB" <BillB@.discussions.microsoft.com> wrote in message
>> >> news:F9A6FA80-4F67-40D6-B9A8-1A9196B83CA4@.microsoft.com...
>> >> > On "Data" tab I run the data. 3 records are returned. i.e.
>> >> >
>> >> > Part# 12345 Philadelphia PA Qty 60
>> >> > Part# 11223 Philadelphia PA Qty 100
>> >> > Part# 11223 Bronx NY Qty 500
>> >> >
>> >> > On "Preview" tab I see the following:
>> >> >
>> >> > Part# 12345 Philadelphia PA 60
>> >> > Part# 11223 Philadelphia PA 100
>> >> >
>> >> >
>> >> > Customer break SUM 660
>> >> >
>> >> > So, I loose the 3rd record in the detail section of the report
>> >> > yet the totals sum up all 3 records.
>> >> >
>> >> > I realize the 2nd & 3rd records have the same Part#.
>> >> >
>> >> > None of the textboxes have "Hide Duplicates" checked off.
>> >> >
>> >> > Can somebody explain to me what's happening?
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>|||Hi Ben
That's it . Thanks for all the help and sticking with me!
"Ben Watts" wrote:
> Go to your detail line and right click on the three lines.then click edit
> group. Even in the detail you can group it and it will hide records. Make
> sure there is nothing in "Group On" Expression. I am betting you have
> something in that. If so just delete it and leave it blank. I just
> recreated that with one of my own reports and when I put something in the
> "group on" in the details line it hid alot of records.
> "BillB" <BillB@.discussions.microsoft.com> wrote in message
> news:A3A0CAAD-7B02-4E76-A03A-802C0D3A34EF@.microsoft.com...
> > Hi Ben
> > In the detail list I show
> > part# 12345 Qty= 60 this is correct
> > part#11223 Qty is showing 100 which is not correct.
> > remember the 2nd record is part # 11223 with qty = 100
> > the third record does not show in the detail at all but the 3rd
> > record
> > has a qty of 500.
> >
> > so i should see in the detail:
> > Part # 11223 qty=600 because it should combine the 2nd record of 100 &
> > the 3rd record with the same Part# of 500.
> >
> > the customer total shows correctly qty 660.
> > hope this makes it clearer & thanks fro the help.
> >
> > "Ben Watts" wrote:
> >
> >> I may be understanding it wrong, but it sounds like it is only showing
> >> one
> >> because of the group. It will still total everything it finds because of
> >> the detail, but if you are showing your group then it will only bring
> >> back
> >> one record. Are you showing any detail in the group. Or is it all
> >> showing
> >> in the details?
> >>
> >> "BillB" <BillB@.discussions.microsoft.com> wrote in message
> >> news:A43A1A2D-2F40-4B17-A01D-D4E289428D6A@.microsoft.com...
> >> > Thanks for the reply.
> >> > Yes I am grouping it by the part #
> >> > the detail line is in a list and the customer total is an another list.
> >> > I'd expect it to total the Qty's on the detail line for the two records
> >> > with the identical Part#'s.
> >> > so part # 11223 would show 600 on the detail line not 100!
> >> >
> >> > "Ben Watts" wrote:
> >> >
> >> >> You arent grouping it by the Part# are you?
> >> >>
> >> >> "BillB" <BillB@.discussions.microsoft.com> wrote in message
> >> >> news:F9A6FA80-4F67-40D6-B9A8-1A9196B83CA4@.microsoft.com...
> >> >> > On "Data" tab I run the data. 3 records are returned. i.e.
> >> >> >
> >> >> > Part# 12345 Philadelphia PA Qty 60
> >> >> > Part# 11223 Philadelphia PA Qty 100
> >> >> > Part# 11223 Bronx NY Qty 500
> >> >> >
> >> >> > On "Preview" tab I see the following:
> >> >> >
> >> >> > Part# 12345 Philadelphia PA 60
> >> >> > Part# 11223 Philadelphia PA 100
> >> >> >
> >> >> >
> >> >> > Customer break SUM 660
> >> >> >
> >> >> > So, I loose the 3rd record in the detail section of the report
> >> >> > yet the totals sum up all 3 records.
> >> >> >
> >> >> > I realize the 2nd & 3rd records have the same Part#.
> >> >> >
> >> >> > None of the textboxes have "Hide Duplicates" checked off.
> >> >> >
> >> >> > Can somebody explain to me what's happening?
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>

Monday, February 20, 2012

Record Selection Crystal Reports

I'm trying to get Crystal reports to prompt the user each time they run the report for the company they want to run the report an the date range they want to run the report on. Unfortunatly I can only get it to do the company at run time. In order to filter out the date range and the company I have to use the selection expert which dosent really help my users is there anyway to filter both sets of values when running the report live for the customer?Cant you pass these values thru the Application you are using?

Wednesday, March 21, 2012

Recover SQL Database from suspect status

Tuesday, March 20, 2012

Recover SQL Database from suspect status

Recover SQL Database from suspect status

Friday, March 9, 2012

Recover data with updated transaction Log only

Recover data from Database Transaction Log

Recover data from Database Transaction Log

Recover data from Database Transaction Log

Wednesday, March 7, 2012

records wont delete

Saturday, February 25, 2012

Records disappearing Data/Preview tabs.

Monday, February 20, 2012

Record Selection Crystal Reports

Record Locks

Blog Archive

About Me