Record Locks: transaction

Showing posts with label transaction. Show all posts

Friday, March 30, 2012

Recovery options when the transaction log is unavailable

Hi,
On MS SQL Server 2000 SP3, what are my recovery options when only the
database transaction log becomes unavailable and when there are active
transactions in the database?
Sp_detach_db/sp_attach_db/sp_attach_single_file_db doesn't work in this
scenario, I have tried that.
Are there any other options and how much of data loss to expect in each case?
-- Many thanks, OskarIs the DB currenlty in Suspect state, have you tried...
sp_add_log_file_recover_suspect_db , Read BOL to get more information
regarding this.
For Active transactions on a damaged / corrupted database you can do a
transacgion log backup using NO_TRUNCATE option. This will backup all the
active transaction in the database. This command will be used only when your
database is damaged.
BACKUP LOG DBNAME TO DISK='C:\db_corr.trn' WITH NO_TRUNCATE
So once the DB is up..
Restorethe last TX log backup taken with NO_TRUNCATE. During this time
mention 'RECOVERY' during RESTORE
Please do share once you restore the DB or let us know if you have any other
queries...
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Oskar" wrote:
> Hi,
> On MS SQL Server 2000 SP3, what are my recovery options when only the
> database transaction log becomes unavailable and when there are active
> transactions in the database?
> Sp_detach_db/sp_attach_db/sp_attach_single_file_db doesn't work in this
> scenario, I have tried that.
> Are there any other options and how much of data loss to expect in each case?
> -- Many thanks, Oskar
>|||Sorry, but neither of your suggestions work:
sp_add_log_file_recover_suspect_db 'TestDB1', 'TestDB1_Log',
'C:\TEMP\TestDB1_Log.LDF'
returned this error
Server: Msg 5004, Level 16, State 2, Line 1
To use ALTER DATABASE, the database must be in a writable state in which a
checkpoint can be executed.
ALTER DATABASE TestDB1 ADD LOG FILE(NAME = [TestDB1_Log], FILENAME ='C:\TEMP\TestDB1_Log.LDF' )
Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
incorrect.
Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
incorrect.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
and I can't backup the transaction log because it is not accessible:
backup tran TestDB1 to disk = 'C:\BACKUP\TestDB1_backup' with no_truncate
returns
Server: Msg 3447, Level 16, State 1, Line 1
Could not activate or scan all of the log files for database 'TestDB1'.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
incorrect.
So it seems, that only option I have in this case is to restore from backup.
-- Thanks, Oskar
"Sreejith G" wrote:
> Is the DB currenlty in Suspect state, have you tried...
> sp_add_log_file_recover_suspect_db , Read BOL to get more information
> regarding this.
> For Active transactions on a damaged / corrupted database you can do a
> transacgion log backup using NO_TRUNCATE option. This will backup all the
> active transaction in the database. This command will be used only when your
> database is damaged.
> BACKUP LOG DBNAME TO DISK='C:\db_corr.trn' WITH NO_TRUNCATE
> So once the DB is up..
> Restorethe last TX log backup taken with NO_TRUNCATE. During this time
> mention 'RECOVERY' during RESTORE
> Please do share once you restore the DB or let us know if you have any other
> queries...
>
>
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and time
> asking back if its 2000 or 2005]
>
> "Oskar" wrote:
> > Hi,
> >
> > On MS SQL Server 2000 SP3, what are my recovery options when only the
> > database transaction log becomes unavailable and when there are active
> > transactions in the database?
> > Sp_detach_db/sp_attach_db/sp_attach_single_file_db doesn't work in this
> > scenario, I have tried that.
> > Are there any other options and how much of data loss to expect in each case?
> >
> > -- Many thanks, Oskar
> >|||In your first thread you said u tried detach/attach/sp_attach_single_file_db,
Below is the syntax and after detach you need not have to execute sp_attach
EXEC sp_detach_db @.dbname = 'pubs'
EXEC sp_attach_single_file_db @.dbname = 'pubs',
@.physname = 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf'
Can you answer the below questions.
Is the DB in SUSPECT state?
Do your DB have multiple data file?
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Oskar" wrote:
> Sorry, but neither of your suggestions work:
> sp_add_log_file_recover_suspect_db 'TestDB1', 'TestDB1_Log',
> 'C:\TEMP\TestDB1_Log.LDF'
> returned this error
> Server: Msg 5004, Level 16, State 2, Line 1
> To use ALTER DATABASE, the database must be in a writable state in which a
> checkpoint can be executed.
> ALTER DATABASE TestDB1 ADD LOG FILE(NAME = [TestDB1_Log], FILENAME => 'C:\TEMP\TestDB1_Log.LDF' )
> Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
> incorrect.
> Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
> incorrect.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> and I can't backup the transaction log because it is not accessible:
> backup tran TestDB1 to disk = 'C:\BACKUP\TestDB1_backup' with no_truncate
> returns
> Server: Msg 3447, Level 16, State 1, Line 1
> Could not activate or scan all of the log files for database 'TestDB1'.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
> Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
> incorrect.
> So it seems, that only option I have in this case is to restore from backup.
> -- Thanks, Oskar
> "Sreejith G" wrote:
> > Is the DB currenlty in Suspect state, have you tried...
> >
> > sp_add_log_file_recover_suspect_db , Read BOL to get more information
> > regarding this.
> >
> > For Active transactions on a damaged / corrupted database you can do a
> > transacgion log backup using NO_TRUNCATE option. This will backup all the
> > active transaction in the database. This command will be used only when your
> > database is damaged.
> >
> > BACKUP LOG DBNAME TO DISK='C:\db_corr.trn' WITH NO_TRUNCATE
> >
> > So once the DB is up..
> > Restorethe last TX log backup taken with NO_TRUNCATE. During this time
> > mention 'RECOVERY' during RESTORE
> >
> > Please do share once you restore the DB or let us know if you have any other
> > queries...
> >
> >
> >
> >
> >
> > --
> > Thanks,
> > Sree
> > [Please specify the version of Sql Server as we can save one thread and time
> > asking back if its 2000 or 2005]
> >
> >
> >
> > "Oskar" wrote:
> >
> > > Hi,
> > >
> > > On MS SQL Server 2000 SP3, what are my recovery options when only the
> > > database transaction log becomes unavailable and when there are active
> > > transactions in the database?
> > > Sp_detach_db/sp_attach_db/sp_attach_single_file_db doesn't work in this
> > > scenario, I have tried that.
> > > Are there any other options and how much of data loss to expect in each case?
> > >
> > > -- Many thanks, Oskar
> > >|||1) Yes, it is suspect as you would expect it to be with inaccessible tran.
log file.
2) No, single data file.
-- Thanks, Oskar
"Sreejith G" wrote:
> In your first thread you said u tried detach/attach/sp_attach_single_file_db,
> Below is the syntax and after detach you need not have to execute sp_attach
> EXEC sp_detach_db @.dbname = 'pubs'
> EXEC sp_attach_single_file_db @.dbname = 'pubs',
> @.physname = 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf'
> Can you answer the below questions.
> Is the DB in SUSPECT state?
> Do your DB have multiple data file?
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and time
> asking back if its 2000 or 2005]
>
> "Oskar" wrote:
> > Sorry, but neither of your suggestions work:
> >
> > sp_add_log_file_recover_suspect_db 'TestDB1', 'TestDB1_Log',
> > 'C:\TEMP\TestDB1_Log.LDF'
> >
> > returned this error
> >
> > Server: Msg 5004, Level 16, State 2, Line 1
> > To use ALTER DATABASE, the database must be in a writable state in which a
> > checkpoint can be executed.
> > ALTER DATABASE TestDB1 ADD LOG FILE(NAME = [TestDB1_Log], FILENAME => > 'C:\TEMP\TestDB1_Log.LDF' )
> > Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
> > incorrect.
> > Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
> > incorrect.
> > DBCC execution completed. If DBCC printed error messages, contact your
> > system administrator.
> >
> > and I can't backup the transaction log because it is not accessible:
> >
> > backup tran TestDB1 to disk = 'C:\BACKUP\TestDB1_backup' with no_truncate
> >
> > returns
> >
> > Server: Msg 3447, Level 16, State 1, Line 1
> > Could not activate or scan all of the log files for database 'TestDB1'.
> > Server: Msg 3013, Level 16, State 1, Line 1
> > BACKUP LOG is terminating abnormally.
> > Device activation error. The physical file name 'E:\TestDB1_Log.LDF' may be
> > incorrect.
> >
> > So it seems, that only option I have in this case is to restore from backup.
> >
> > -- Thanks, Oskar
> >
> > "Sreejith G" wrote:
> >
> > > Is the DB currenlty in Suspect state, have you tried...
> > >
> > > sp_add_log_file_recover_suspect_db , Read BOL to get more information
> > > regarding this.
> > >
> > > For Active transactions on a damaged / corrupted database you can do a
> > > transacgion log backup using NO_TRUNCATE option. This will backup all the
> > > active transaction in the database. This command will be used only when your
> > > database is damaged.
> > >
> > > BACKUP LOG DBNAME TO DISK='C:\db_corr.trn' WITH NO_TRUNCATE
> > >
> > > So once the DB is up..
> > > Restorethe last TX log backup taken with NO_TRUNCATE. During this time
> > > mention 'RECOVERY' during RESTORE
> > >
> > > Please do share once you restore the DB or let us know if you have any other
> > > queries...
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Thanks,
> > > Sree
> > > [Please specify the version of Sql Server as we can save one thread and time
> > > asking back if its 2000 or 2005]
> > >
> > >
> > >
> > > "Oskar" wrote:
> > >
> > > > Hi,
> > > >
> > > > On MS SQL Server 2000 SP3, what are my recovery options when only the
> > > > database transaction log becomes unavailable and when there are active
> > > > transactions in the database?
> > > > Sp_detach_db/sp_attach_db/sp_attach_single_file_db doesn't work in this
> > > > scenario, I have tried that.
> > > > Are there any other options and how much of data loss to expect in each case?
> > > >
> > > > -- Many thanks, Oskar
> > > >

Recovery options when the transaction log is unavailable

Recovery Models

In an attempt to manage the size of the transaction log , I would like to use
the
Simple verses the Full Recovery model. Other than the loss of transaction log
backup and recovery only to the last full or differential backup, are
there any
other “landmines” I should consider? Thanks for being there to help. Regards
Ed.
No landmines, but remember the tlog will still grow to accept the largest
single transaction you ever do, so the log might still get quite large, and
it does not shrink automatically.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
> In an attempt to manage the size of the transaction log , I would like to
> use
> the
> Simple verses the Full Recovery model. Other than the loss of transaction
> log
> backup and recovery only to the last full or differential backup, are
> there any
> other "landmines" I should consider? Thanks for being there to help.
> Regards
> Ed.
>
|||I thing that features that come with transaction log are many time worthier
than the time you lose learning how to deal with transaction log. So put
some effort on learning and you will have great benefit.
Regards,
Daniel
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
> In an attempt to manage the size of the transaction log , I would like to
use
> the
> Simple verses the Full Recovery model. Other than the loss of transaction
log
> backup and recovery only to the last full or differential backup, are
> there any
> other "landmines" I should consider? Thanks for being there to help.
Regards
> Ed.
>
|||Dealing with the size of the transaction log is about as difficult as
dealing with any of the other maitenance plans. You are doing the other
maitenance options aren't you? Because if you are, the transaction log will
grow to the size of the single largest transaction, which is typically the
Database Reorganization plan, REINDEX.
Now, also consider what the transaction log really is. It is akin to the
general ledger of an accounting system. It records every action take
against a database the takes the database image from one snapshot to
another. The FULL and DIFFERENTIALS are only the snapshots. The
transaction logs are the actual work modifications that get you between the
two.
Sincerely,
Anthony Thomas

"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
In an attempt to manage the size of the transaction log , I would like to
use
the
Simple verses the Full Recovery model. Other than the loss of transaction
log
backup and recovery only to the last full or differential backup, are
there any
other "landmines" I should consider? Thanks for being there to help.
Regards
Ed.

Recovery Models

In an attempt to manage the size of the transaction log , I would like to us
e
the
Simple verses the Full Recovery model. Other than the loss of transaction lo
g
backup and recovery only to the last full or differential backup, are
there any
other “landmines” I should consider? Thanks for being there to help. Reg
ards
Ed.No landmines, but remember the tlog will still grow to accept the largest
single transaction you ever do, so the log might still get quite large, and
it does not shrink automatically.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
> In an attempt to manage the size of the transaction log , I would like to
> use
> the
> Simple verses the Full Recovery model. Other than the loss of transaction
> log
> backup and recovery only to the last full or differential backup, are
> there any
> other "landmines" I should consider? Thanks for being there to help.
> Regards
> Ed.
>|||I thing that features that come with transaction log are many time worthier
than the time you lose learning how to deal with transaction log. So put
some effort on learning and you will have great benefit.
Regards,
Daniel
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
> In an attempt to manage the size of the transaction log , I would like to
use
> the
> Simple verses the Full Recovery model. Other than the loss of transaction
log
> backup and recovery only to the last full or differential backup, are
> there any
> other "landmines" I should consider? Thanks for being there to help.
Regards
> Ed.
>|||Dealing with the size of the transaction log is about as difficult as
dealing with any of the other maitenance plans. You are doing the other
maitenance options aren't you? Because if you are, the transaction log will
grow to the size of the single largest transaction, which is typically the
Database Reorganization plan, REINDEX.
Now, also consider what the transaction log really is. It is akin to the
general ledger of an accounting system. It records every action take
against a database the takes the database image from one snapshot to
another. The FULL and DIFFERENTIALS are only the snapshots. The
transaction logs are the actual work modifications that get you between the
two.
Sincerely,
Anthony Thomas
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
In an attempt to manage the size of the transaction log , I would like to
use
the
Simple verses the Full Recovery model. Other than the loss of transaction
log
backup and recovery only to the last full or differential backup, are
there any
other "landmines" I should consider? Thanks for being there to help.
Regards
Ed.

Recovery Models

In an attempt to manage the size of the transaction log , I would like to use
the
Simple verses the Full Recovery model. Other than the loss of transaction log
backup and recovery only to the last full or differential backup, are
there any
other â'landminesâ' I should consider? Thanks for being there to help. Regards
Ed.No landmines, but remember the tlog will still grow to accept the largest
single transaction you ever do, so the log might still get quite large, and
it does not shrink automatically.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
> In an attempt to manage the size of the transaction log , I would like to
> use
> the
> Simple verses the Full Recovery model. Other than the loss of transaction
> log
> backup and recovery only to the last full or differential backup, are
> there any
> other "landmines" I should consider? Thanks for being there to help.
> Regards
> Ed.
>|||I thing that features that come with transaction log are many time worthier
than the time you lose learning how to deal with transaction log. So put
some effort on learning and you will have great benefit.
Regards,
Daniel
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
> In an attempt to manage the size of the transaction log , I would like to
use
> the
> Simple verses the Full Recovery model. Other than the loss of transaction
log
> backup and recovery only to the last full or differential backup, are
> there any
> other "landmines" I should consider? Thanks for being there to help.
Regards
> Ed.
>|||Dealing with the size of the transaction log is about as difficult as
dealing with any of the other maitenance plans. You are doing the other
maitenance options aren't you? Because if you are, the transaction log will
grow to the size of the single largest transaction, which is typically the
Database Reorganization plan, REINDEX.
Now, also consider what the transaction log really is. It is akin to the
general ledger of an accounting system. It records every action take
against a database the takes the database image from one snapshot to
another. The FULL and DIFFERENTIALS are only the snapshots. The
transaction logs are the actual work modifications that get you between the
two.
Sincerely,
Anthony Thomas
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:BB2640FA-431E-485B-8B30-B5D3B72DE5EA@.microsoft.com...
In an attempt to manage the size of the transaction log , I would like to
use
the
Simple verses the Full Recovery model. Other than the loss of transaction
log
backup and recovery only to the last full or differential backup, are
there any
other "landmines" I should consider? Thanks for being there to help.
Regards
Ed.

Wednesday, March 28, 2012

Recovery Mode and Replication

Is there any requirement for either the publisher or subscriber to have
full recovery model enabled when using transaction replication.
No, but put your subscriber in bulk copy mode when you are applying the
snapshot for a faster deployment.
I normally put my publication database in full recovery model and dump
frequently to make life easier for the log reader.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul" <sueme.sucker@.gmail.com> wrote in message
news:1138896281.822489.160290@.g47g2000cwa.googlegr oups.com...
> Is there any requirement for either the publisher or subscriber to have
> full recovery model enabled when using transaction replication.
>
|||Nope. Replication will still work in any recovery model.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Paul" <sueme.sucker@.gmail.com> wrote in message
news:1138896281.822489.160290@.g47g2000cwa.googlegr oups.com...
> Is there any requirement for either the publisher or subscriber to have
> full recovery model enabled when using transaction replication.
>
|||Thanks for the quick reponses

Monday, March 26, 2012

Recovery from Delete statement using the transaction logs

I ran some delete statements in Query Analyzer and I
found out it was the wrong database. Can you rollback the
delete statements and recover the data from the
transaction logs?
I assume you didn't protect the delete with BEGIN TRAN? If you did, just do ROLLBACK.
Are you performing regular transaction log backups? Is database in full or bulk logged recovery
mode? If answers to these questions are "no", you will probably need to go to your most recent
backup or just accept the data loss. If answers are "yes", you *might* be in better shape.
Anyhow, I suggest you read my article on the topic at:
http://www.karaszi.com/SQLServer/inf...eral_times.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Robert" <robert@.expressprogramming.com> wrote in message
news:179b01c51500$f58a6c00$a601280a@.phx.gbl...
>I ran some delete statements in Query Analyzer and I
> found out it was the wrong database. Can you rollback the
> delete statements and recover the data from the
> transaction logs?

Recovery from Delete statement using the transaction logs

I ran some delete statements in Query Analyzer and I
found out it was the wrong database. Can you rollback the
delete statements and recover the data from the
transaction logs'I assume you didn't protect the delete with BEGIN TRAN? If you did, just do
ROLLBACK.
Are you performing regular transaction log backups? Is database in full or b
ulk logged recovery
mode? If answers to these questions are "no", you will probably need to go t
o your most recent
backup or just accept the data loss. If answers are "yes", you *might* be in
better shape.
Anyhow, I suggest you read my article on the topic at:
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/
"Robert" <robert@.expressprogramming.com> wrote in message
news:179b01c51500$f58a6c00$a601280a@.phx.gbl...
>I ran some delete statements in Query Analyzer and I
> found out it was the wrong database. Can you rollback the
> delete statements and recover the data from the
> transaction logs'

Recovery from Delete statement using the transaction logs

I ran some delete statements in Query Analyzer and I
found out it was the wrong database. Can you rollback the
delete statements and recover the data from the
transaction logs'I assume you didn't protect the delete with BEGIN TRAN? If you did, just do ROLLBACK.
Are you performing regular transaction log backups? Is database in full or bulk logged recovery
mode? If answers to these questions are "no", you will probably need to go to your most recent
backup or just accept the data loss. If answers are "yes", you *might* be in better shape.
Anyhow, I suggest you read my article on the topic at:
http://www.karaszi.com/SQLServer/info_restore_log_several_times.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Robert" <robert@.expressprogramming.com> wrote in message
news:179b01c51500$f58a6c00$a601280a@.phx.gbl...
>I ran some delete statements in Query Analyzer and I
> found out it was the wrong database. Can you rollback the
> delete statements and recover the data from the
> transaction logs'

Recovering using the transaction log

I have a database hosted on a comercial web server
I can access it using SQL server Entreprise Manager
I have never backed the database up though i copy it
regularly.
Exactly how do you recover the database to an earlier point using the
Transaction Log and can it be done to recover 'Dropped' objects
Help gratefully received regards EarnieMost probably you have to revert to one of your older copies. You *might* be
able to use any of the
log reader tools out there, but as you never backed up the database, then mo
st probably the log
records needed to undo the modifications aren't around anymore in the transa
ction log files of the
database. See my article on the subject at:
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/
http://www.sqlug.se/
"Earnie" <Earnie@.discussions.microsoft.com> wrote in message
news:A6434B02-D7BA-4E6D-ABD7-E5D177DBAF4F@.microsoft.com...
>I have a database hosted on a comercial web server
> I can access it using SQL server Entreprise Manager
> I have never backed the database up though i copy it
> regularly.
> Exactly how do you recover the database to an earlier point using the
> Transaction Log and can it be done to recover 'Dropped' objects
> Help gratefully received regards Earniesql

Friday, March 23, 2012

Recovering from transaction log deletion in 6.5

I was trying to relocate my transaction log to a bigger drive using
sp_movedevice but I made a mistake in the syntax of the second parameter
and put only the path, not the path and the file name.
Now my database is marked as "suspect" and I get an error message in my log
upon database start up saying that the log file cannot be open.

Is there a way to have MS SQL 6.5 "forget" all the logs of this database,
create new ones and restart the database? The logs contained nothing
important, I had truncated them an hour or so before I made my mistake. I
just want to make sure the data are still usable.
When I look at the devices with sp_helpdevice, I can see a log that exist
and is hopefully in pristine condition and the one that doesn't exist
anymore.
I looked in the archives of various newsgroups but couldn't find something
that correspond closely to my situation. I saw something similar but with
MS SQL 7.0
(http://groups.google.com/groups?hl=...om %26rnum%3D4)
using sp_attach_db/sp_detach_db. What would be the equivalent with version
6.5?

Thanks!

Charles

--
Charles-E. Nadeau Ph.D
http://radio.weblogs.com/0111823/[posted and mailed]

Charles Nadeau (charlesnadeau@.hotmail.com) writes:
> I was trying to relocate my transaction log to a bigger drive using
> sp_movedevice but I made a mistake in the syntax of the second parameter
> and put only the path, not the path and the file name. Now my database
> is marked as "suspect" and I get an error message in my log upon
> database start up saying that the log file cannot be open.
> Is there a way to have MS SQL 6.5 "forget" all the logs of this database,
> create new ones and restart the database? The logs contained nothing
> important, I had truncated them an hour or so before I made my mistake. I
> just want to make sure the data are still usable.
> When I look at the devices with sp_helpdevice, I can see a log that exist
> and is hopefully in pristine condition and the one that doesn't exist
> anymore.

Indeed, you should be able to get to the data. I know how to deal with
the situation in SQL2000, but I don't know if those commands work in
6.5. (It's not the same as in the link you posted; sp_attach_db is not
in 6.5.) As the hour is late, I am not going to test, but I'll ask
around with my contacts at Microsoft, to see if they know.

If the mail address is not one you monitor, please send me a mail, since
the answer I get from MS may not be suitable for a public newsgroup. (The
method for SQL2000 is very dangerous if you don't understand what you
are doing.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||You can set to emergency mode
http://support.microsoft.com/defaul...kb;en-us;165918

Which should allow you to access the data.

Didn't you take a backup first?

Nigel Rivett
www.nigelrivett.net

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Erland Sommarskog wrote:

> [posted and mailed]
> Charles Nadeau (charlesnadeau@.hotmail.com) writes:
>> I was trying to relocate my transaction log to a bigger drive using
>> sp_movedevice but I made a mistake in the syntax of the second parameter
>> and put only the path, not the path and the file name. Now my database
>> is marked as "suspect" and I get an error message in my log upon
>> database start up saying that the log file cannot be open.
>>
>> Is there a way to have MS SQL 6.5 "forget" all the logs of this database,
>> create new ones and restart the database? The logs contained nothing
>> important, I had truncated them an hour or so before I made my mistake. I
>> just want to make sure the data are still usable.
>> When I look at the devices with sp_helpdevice, I can see a log that exist
>> and is hopefully in pristine condition and the one that doesn't exist
>> anymore.
> Indeed, you should be able to get to the data. I know how to deal with

Just a few more details:
My log files are on the f: drive:

F:\mssql\data>dir
*Volume in drive F has no label.
*Volume Serial Number is 8018-882A

*Directory of F:\mssql\data

18/05/04* 01:40p******* <DIR>********* .
18/05/04* 01:40p******* <DIR>********* ..
24/08/01* 02:14p*************** 26,522 defn_ticket.sql.sql
18/05/04* 01:40p******* <DIR>********* dump
22/09/00* 01:45p**************** 1,384 dump.bat
18/05/04* 01:39p********** 268,435,456 master.mir
10/04/03* 08:12a*********** 42,844,160 Support-Processed.ps
18/05/04* 11:47a********** 268,435,456 ticket.mir
18/05/04* 12:16p******** 1,073,741,824 Ticketlog2.DAT
18/05/04* 12:16p******** 1,073,741,824 Ticket_log.dat
18/05/04* 01:39p************ 8,388,608 Winnie.DAT
18/05/04* 01:39p*********** 25,165,824 Winnie_log.DAT
************* 12 File(s)* 2,760,781,058 bytes
************************* 4,938,989,568 bytes free

The valid log file is Ticketlog2.DAT. Ticket_log.dat is simply a copy of
Ticketlog2.DAT I renamed and put there to try to force SQL Server to read
it.

And here is the output of two commands listing the state of my devices:

select * from sysdevices
go
sp_helpdevice
go

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 16995 ms.
SQL Server Parse and Compile Time:
** cpu time = 0 ms.
low******** high******* status cntrltype name**************************
phyname******************************************* ************************************************** ***************************
mirrorname**************************************** ************************************************** ***************************
stripeset*********************

---- ---- -- --- ----------
--------------------------------------
--------------------------------------
----------

0********** 19********* 16**** 3******** diskettedumpa*****************
a:sqltable.dat************************************ ************************************************** ***************************
(null)******************************************** ************************************************** ***************************
(null)************************

0********** 19********* 16**** 4******** diskettedumpb*****************
b:sqltable.dat************************************ ************************************************** ***************************
(null)******************************************** ************************************************** ***************************
(null)************************

0********** 131071***** 739*** 0******** master************************ C
\MSSQL\DATA\MASTER.DAT**************************** ************************************************** *************************
f:\mssql\data\master.mir************************** ************************************************** ***************************
(null)************************

2130706432* 2130709503* 2***** 0******** MSDBData********************** C
\MSSQL\DATA\MSDB.DAT****************************** ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

2113929216* 2113930239* 2***** 0******** MSDBLog*********************** C
\MSSQL\DATA\MSDBLOG.DAT*************************** ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

16777216*** 16908287*** 2***** 0******** ticket************************ f
\mssql\data\ticket.mir**************************** ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

33554432*** 33832959*** 2***** 0******** Ticket_log******************** f
\mssql\data\ticket_log.dat************************ ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

0********** 0********** 16**** 2******** TicketBackUp****************** F
\mssql\BackUp\TicketBackUp.DAT******************** ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

83886080*** 84410367*** 2***** 0******** Ticketlog2******************** F
\mssql\data\Ticketlog2.DAT************************ ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

50331648*** 50335743*** 2***** 0******** Winnie************************ F
\MSSQL\DATA\Winnie.DAT**************************** ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

0********** 0********** 16**** 2******** Winnie_backup***************** f
\MSSQL\BACKUP\Winnie_backup.DAT******************* ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

67108864*** 67121151*** 2***** 0******** Winnie_log******************** F
\MSSQL\DATA\Winnie_log.DAT************************ ************************************************** *************************
(null)******************************************** ************************************************** ***************************
(null)************************

(12 row(s) affected)

Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 0 ms.
SQL Server Parse and Compile Time:
** cpu time = 0 ms.
SQL Server Parse and Compile Time:
** cpu time = 70 ms.
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 261 ms.

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 50 ms.

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 0 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 12,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 10 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 16,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 8,* logical reads: 8,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 40 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 4,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 2,* logical reads: 2,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 10 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 4,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 2,* logical reads: 2,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 4,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 2,* logical reads: 2,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 110 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 521 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 20 ms.
Table: sysdevices* scan count 1,* logical reads: 1,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 1,* logical reads: 2,* physical reads: 1,*
read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 10 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 2,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 2,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 8,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 12,* logical reads: 24,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 16,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 12,* logical reads: 24,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 16,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 1,* logical reads: 2,* physical reads: 1,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 70 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 12,* logical reads: 24,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 10 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 12,* logical reads: 24,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 20 ms.
Table: #spdevtab___________0100000002* scan count 0,* logical reads: 0,*
physical reads: 0,* read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: spt_values* scan count 12,* logical reads: 24,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 10 ms.

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 0 ms.
device_name******************* physical_name*********************************
description*************************************** ************************************************** ************************************************** ************************************************** ************************************************** *****
status cntrltype device_number low******** high*******

----------
--------------
----------------------------------------------------------------------------
-- --- ---- ---- ----

TicketBackUp****************** F:\mssql\BackUp\TicketBackUp.DAT**************
disk, dump device******************************************** ************************************************** ************************************************** ************************************************** ********************************************
16**** 2******** 0************ 0********** 0**********

Winnie_backup***************** f:\MSSQL\BACKUP\Winnie_backup.DAT*************
disk, dump device******************************************** ************************************************** ************************************************** ************************************************** ********************************************
16**** 2******** 0************ 0********** 0**********

diskettedumpa***************** a:sqltable.dat********************************
diskette, 1.2 MB, dump device******************************************** ************************************************** ************************************************** ************************************************** ********************************
16**** 3******** 0************ 0********** 19*********

diskettedumpb***************** b:sqltable.dat********************************
diskette, 1.2 MB, dump device******************************************** ************************************************** ************************************************** ************************************************** ********************************
16**** 4******** 0************ 0********** 19*********

MSDBData********************** C:\MSSQL\DATA\MSDB.DAT************************
special, physical disk, 6 MB************************************************ ************************************************** ************************************************** ************************************************** *****************************
2***** 0******** 127********** 2130706432* 2130709503*

MSDBLog*********************** C:\MSSQL\DATA\MSDBLOG.DAT*********************
special, physical disk, 2 MB************************************************ ************************************************** ************************************************** ************************************************** *****************************
2***** 0******** 126********** 2113929216* 2113930239*

ticket************************ f:\mssql\data\ticket.mir**********************
special, physical disk, 256 MB************************************************ ************************************************** ************************************************** ************************************************** ***************************
2***** 0******** 1************ 16777216*** 16908287***

Ticket_log******************** f:\mssql\data\ticket_log.dat******************
special, physical disk, 544 MB************************************************ ************************************************** ************************************************** ************************************************** ***************************
2***** 0******** 2************ 33554432*** 33832959***

Ticketlog2******************** F:\mssql\data\Ticketlog2.DAT******************
special, physical disk, 1024 MB************************************************ ************************************************** ************************************************** ************************************************** **************************
2***** 0******** 5************ 83886080*** 84410367***

Winnie************************ F:\MSSQL\DATA\Winnie.DAT**********************
special, physical disk, 8 MB************************************************ ************************************************** ************************************************** ************************************************** *****************************
2***** 0******** 3************ 50331648*** 50335743***

Winnie_log******************** F:\MSSQL\DATA\Winnie_log.DAT******************
special, physical disk, 24 MB************************************************ ************************************************** ************************************************** ************************************************** ****************************
2***** 0******** 4************ 67108864*** 67121151***

master************************ C:\MSSQL\DATA\MASTER.DAT**********************
special, MIRROR ENABLED, mirrored on 'f:\mssql\data\master.mir', serial
writes, reads mirrored, default disk, physical disk, 256 MB************************************************ ************************************************** **************************
739*** 0******** 0************ 0********** 131071*****

(1 row(s) affected)

Table: sysdevices* scan count 12,* logical reads: 12,* physical reads: 0,*
read ahead reads: 0
Table: #spdevtab___________0100000002* scan count 1,* logical reads: 1,*
physical reads: 0,* read ahead reads: 0
Table: spt_values* scan count 1,* logical reads: 2,* physical reads: 0,*
read ahead reads: 0

SQL Server Execution Times:
** cpu time = 10 ms.* elapsed time = 10 ms.

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 0 ms.

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 20 ms.
SQL Server Parse and Compile Time:
** cpu time = 0 ms.

SQL Server Execution Times:
** cpu time = 0 ms.* elapsed time = 0 ms.

I hope this will shed more lights on my problem. Thanks again for your help!

Charles

> the situation in SQL2000, but I don't know if those commands work in
> 6.5. (It's not the same as in the link you posted; sp_attach_db is not
> in 6.5.) As the hour is late, I am not going to test, but I'll ask
> around with my contacts at Microsoft, to see if they know.
> If the mail address is not one you monitor, please send me a mail, since
> the answer I get from MS may not be suitable for a public newsgroup. (The
> method for SQL2000 is very dangerous if you don't understand what you
> are doing.)

--
Charles-E. Nadeau Ph.D
http://radio.weblogs.com/0111823/|||Nigel Rivett wrote:

> You can set to emergency mode
> http://support.microsoft.com/defaul...kb;en-us;165918

Using this I can backup my data and truncate the log but I don't think it
can take care of the bad information inside sysdevices. I'll take a deeper
look at it later on.

> Which should allow you to access the data.
> Didn't you take a backup first?

I backup the database daily by "dumping" them using bcp (i.e. bcp
Ticket.dbo.Item2Ticket out f:\mssql\data\dump\Item2Ticket.tbl /n /U
username /P password /S WINHKONG ).
This is my last backup:

K:\mssql\data\dump>dir
*Volume in drive K has no label.
*Volume Serial Number is 8018-882A

*Directory of K:\mssql\data\dump

18/05/04* 01:40p******* <DIR>********* .
18/05/04* 01:40p******* <DIR>********* ..
15/10/01* 04:10p*************** 29,022 all db scripts.sql.sql
17/05/04* 04:15p****************** 184 Item2Ticket.tbl
17/05/04* 04:15p*************** 15,895 LastInteraction.tbl
17/05/04* 04:15p*************** 30,647 Mission.tbl
17/05/04* 04:15p****************** 164 RSM.tbl
17/05/04* 04:15p******************* 28 Status.tbl
17/05/04* 04:15p**************** 2,059 TaskItems.tbl
17/05/04* 04:15p******************* 69 Tasks.tbl
17/05/04* 04:15p******************* 24 TaskType.tbl
17/05/04* 04:20p*********** 43,394,880 Ticket.tbl
17/05/04* 04:20p****************** 286 Topics.tbl
17/05/04* 04:20p******************* 60 Types.tbl
17/05/04* 04:20p************** 316,258 Words.tbl
17/05/04* 04:24p*********** 19,785,780 WordsInTicket.tbl
************* 16 File(s)**** 63,575,356 bytes
************************* 4,938,989,568 bytes free

> Nigel Rivett
> www.nigelrivett.net

Thanks for your help, much appreciated!

Charles

> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

--
Charles-E. Nadeau Ph.D
http://radio.weblogs.com/0111823/|||Have you tried setting to emergency mode?
That should allow you to bcp all the data out and copy to another
database.

Nigel Rivett
www.nigelrivett.net

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Charles Nadeau (charlesnadeau@.hotmail.com) writes:
> Using this I can backup my data and truncate the log but I don't think it
> can take care of the bad information inside sysdevices. I'll take a deeper
> look at it later on.

Once you have gotten the data out, I suggest that you drop the database
and create a new one. You should not continue with the database once it
has been marked suspect.

I assume that you have your scripts on version control, but if not there are
scripting facitilies in Enterprise Manager.

> I backup the database daily by "dumping" them using bcp (i.e. bcp
> Ticket.dbo.Item2Ticket out f:\mssql\data\dump\Item2Ticket.tbl /n /U
> username /P password /S WINHKONG ).
> This is my last backup:

While that saves your data, you don't save metadata and stored procedures
this way. What's wrong with the regular DUMP command.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

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

> Charles Nadeau (charlesnadeau@.hotmail.com) writes:
>> Using this I can backup my data and truncate the log but I don't think it
>> can take care of the bad information inside sysdevices. I'll take a
>> deeper look at it later on.
> Once you have gotten the data out, I suggest that you drop the database

This is what I did. Everything was smooth:
I put the database is emergency mode, bcp all the data out of it.
I cheked where my last back-up and the database scripts were.
I droped the database and its devices, then recreated the devices.
I created the database FOR LOAD.
I restored from my latest back-up (I didn't loose any data!).
I set the databse for use not only by dbo.
At this point I panicked a bit because the database was flagged as loading
even after I had put the data back into it. I restarted the server and I
was back in business. I was expecting the whole thing to be longer and more
painfull.
Thanks a lot for your help!

Charles

> and create a new one. You should not continue with the database once it
> has been marked suspect.
> I assume that you have your scripts on version control, but if not there
> are scripting facitilies in Enterprise Manager.
>> I backup the database daily by "dumping" them using bcp (i.e. bcp
>> Ticket.dbo.Item2Ticket out f:\mssql\data\dump\Item2Ticket.tbl /n /U
>> username /P password /S WINHKONG ).
>> This is my last backup:
> While that saves your data, you don't save metadata and stored procedures
> this way. What's wrong with the regular DUMP command.

--
Charles-E. Nadeau Ph.D
http://radio.weblogs.com/0111823/|||Charles Nadeau (charlesnadeau@.hotmail.com) writes:
> This is what I did. Everything was smooth:
> I put the database is emergency mode, bcp all the data out of it.
> I cheked where my last back-up and the database scripts were.
> I droped the database and its devices, then recreated the devices.
> I created the database FOR LOAD.
> I restored from my latest back-up (I didn't loose any data!).
> I set the databse for use not only by dbo.
> At this point I panicked a bit because the database was flagged as
> loading even after I had put the data back into it. I restarted the
> server and I was back in business. I was expecting the whole thing to be
> longer and more painfull.

Glad to hear that it worked out fine!

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

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

Wednesday, March 21, 2012

Recover Transaction Log

Hi - I'm requesting help to understand a concept:
Can you restore a Transaction Log Backup only Transaction Logs backed up
AFTER a Full Backup?
EXAMPLE: Setup assuming 2 hard drives:
* Database MDF files stored on hard drive (A)
* Database Transaction Log files soted on hard drive(B)
First, Lets assume a Full Backup has been peformed nightly for a week at
Midnight.
Second, lets also assume that a week ago I temporaily stoped the
every-2-hour-schedule for a Transaction Log Backup and forgot to turn the
schedule back on - Therefore no Transaction Log Backup occured during the
past week.
Now, lets assume that harddrive (A) crashes at noon today - but hard drive
(B) is ok and still works. I have a succesfull Full Backup at Midnight, so I
know I can restore that.
Question: After Restoring from the Midnight Full Backup, Can I use the
current Transaction Log file as of Noon to restore the remainder of the logs
,
even though it had not been backuped for 6 days? Or is it required that a
transaction log backup have occured at some point after the Full backup?> Question: After Restoring from the Midnight Full Backup, Can I use the
> current Transaction Log file as of Noon to restore the remainder of the lo
gs,
> even though it had not been backuped for 6 days?
No. The reason you can't do that is the when you do the restore, you will ov
erwrite the log records
in the ldf file. What you can do, is *before* you do the restore, backup the
log. You now have a
database backup and a log backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"labsRcool@.community.nospan" <labsRcoolcommunitynospan@.discussions.microsoft
.com> wrote in message
news:ACC73D9F-EE1A-4E2B-B25D-24F4927A8BC6@.microsoft.com...
> Hi - I'm requesting help to understand a concept:
> Can you restore a Transaction Log Backup only Transaction Logs backed up
> AFTER a Full Backup?
> EXAMPLE: Setup assuming 2 hard drives:
> * Database MDF files stored on hard drive (A)
> * Database Transaction Log files soted on hard drive(B)
> First, Lets assume a Full Backup has been peformed nightly for a week at
> Midnight.
> Second, lets also assume that a week ago I temporaily stoped the
> every-2-hour-schedule for a Transaction Log Backup and forgot to turn the
> schedule back on - Therefore no Transaction Log Backup occured during the
> past week.
> Now, lets assume that harddrive (A) crashes at noon today - but hard drive
> (B) is ok and still works. I have a succesfull Full Backup at Midnight, so
I
> know I can restore that.
> Question: After Restoring from the Midnight Full Backup, Can I use the
> current Transaction Log file as of Noon to restore the remainder of the lo
gs,
> even though it had not been backuped for 6 days? Or is it required that a
> transaction log backup have occured at some point after the Full backup?
>
>|||Thanks!
Follow up question:
If I do as you suggest, and Backup the current log, then I'm assuming the
process is as follows:
1)Restore Full Backup from the midnight backup
2)Restore the Log backup that I just "backed up" before the restore.
In regards to the Log restore, I'm assuming then, that the restore process
is smart enough to only include from the transaction log the transactions
that have occured since the Midnight backup...and will not attempt to
re-include(duplicate) the transaction over the last week. (i.e., it's now
just treated as a normal transaction log backup/restore as if it I had been
backing them up like I was supposed to ;)
Thanks!
"Tibor Karaszi" wrote:

> No. The reason you can't do that is the when you do the restore, you will
overwrite the log records
> in the ldf file. What you can do, is *before* you do the restore, backup t
he log. You now have a
> database backup and a log backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "labsRcool@.community.nospan" <labsRcoolcommunitynospan@.discussions.microso
ft.com> wrote in message
> news:ACC73D9F-EE1A-4E2B-B25D-24F4927A8BC6@.microsoft.com...
>|||Yes, that is correct. The database backup has all log records produced durin
g that database backup.
So, restore will copy in the data pages, and use the log records in the data
base backup to do the
REDO process. When you then restore the log backup, SQL Server will start th
e REDO operation from
the very last log record in the database backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"labsRcool@.community.nospan" <labsRcoolcommunitynospan@.discussions.microsoft
.com> wrote in message
news:0CED8BB9-8B1D-4E04-BD07-B9525D1A5037@.microsoft.com...[vbcol=seagreen]
> Thanks!
> Follow up question:
> If I do as you suggest, and Backup the current log, then I'm assuming the
> process is as follows:
> 1)Restore Full Backup from the midnight backup
> 2)Restore the Log backup that I just "backed up" before the restore.
> In regards to the Log restore, I'm assuming then, that the restore process
> is smart enough to only include from the transaction log the transactions
> that have occured since the Midnight backup...and will not attempt to
> re-include(duplicate) the transaction over the last week. (i.e., it's now
> just treated as a normal transaction log backup/restore as if it I had bee
n
> backing them up like I was supposed to ;)
> Thanks!
> "Tibor Karaszi" wrote:
>

Recover Transaction Log

recover sql db with only data file

I accidentally deleted transaction log file on my test sql server, I can't get my database back now.
Does anybody know how to recover a database with only datafile? (.mdf and ndf)
Thanks in advanceThe only option left is to use DBCC REBUILD_LOG and when the transaction log for a database is lost or damaged. In such a case, it is very likely there are unapplied transactions lost with the log, and the database is therefore inconsistent. Also, the event that causes the loss of the transaction log, such as a hardware failure, may have damaged the database.

KBA -Q232518 refers the same.|||Thank you so much for your quick reply. I'll try it.

Originally posted by Satya
The only option left is to use DBCC REBUILD_LOG and when the transaction log for a database is lost or damaged. In such a case, it is very likely there are unapplied transactions lost with the log, and the database is therefore inconsistent. Also, the event that causes the loss of the transaction log, such as a hardware failure, may have damaged the database.

KBA -Q232518 refers the same.sql

Tuesday, March 20, 2012

recover Dropped table

Hi,
This is a dissaster.
tables are dropped from the database, which there is no transaction log (it
was set up with simple recovery mode.)
Data has never been backup.
Is there anyway that the data can be recover from those dropped table.
Thanks,
DaraDara,
If there is no transaction log, Lumigent won't help you.
If the data has never been backed up, then I have nothing else to offer you.
(If you had a backup, then you could restore it to another database and copy
the tables from the restore database back to your working database.)
Russell Fields
Crazy Idea: If ABSOLUTELY NOTHING has been done to the database since the
tables were dropped and if you are willing to pay for the help, Microsoft
might be able to root out the tables from the database structure. This is
NOT likely though.
"Dara Bunhim" <bdara@.racha.org.kh> wrote in message
news:eCQbzvtcDHA.3520@.tk2msftngp13.phx.gbl...
> Hi,
> This is a dissaster.
> tables are dropped from the database, which there is no transaction log
(it
> was set up with simple recovery mode.)
> Data has never been backup.
> Is there anyway that the data can be recover from those dropped table.
> Thanks,
> Dara
>|||Not sure if this will work. If there was a file system backup, recover data
and log files from the backup before the table was dropped and do sp_attach.
Good luck!
"Russell Fields" <rlfields@.sprynet.com> wrote in message
news:ej3axNucDHA.1532@.TK2MSFTNGP10.phx.gbl...
> Dara,
> If there is no transaction log, Lumigent won't help you.
> If the data has never been backed up, then I have nothing else to offer
you.
> (If you had a backup, then you could restore it to another database and
copy
> the tables from the restore database back to your working database.)
> Russell Fields
> Crazy Idea: If ABSOLUTELY NOTHING has been done to the database since the
> tables were dropped and if you are willing to pay for the help, Microsoft
> might be able to root out the tables from the database structure. This is
> NOT likely though.
> "Dara Bunhim" <bdara@.racha.org.kh> wrote in message
> news:eCQbzvtcDHA.3520@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > This is a dissaster.
> >
> > tables are dropped from the database, which there is no transaction log
> (it
> > was set up with simple recovery mode.)
> >
> > Data has never been backup.
> >
> > Is there anyway that the data can be recover from those dropped table.
> >
> > Thanks,
> > Dara
> >
> >
>

Monday, March 12, 2012

Recover Database Help!

Hello,

Is it possible to restore a SQL 2000 database with data from a transaction log?

I am not sure what happened to my database, all the data in the tables is gone. I generated a db script to create a duplicate database. I saved the .sql file on my local machine, separate from the db server, renamed the database name in the .sql file to a new database. Tested script in query analyzer for syntax, all was fine. Running it at this point would have created a new database with a different name, right?

Now my original database is empty. Can someone please provide me with information on getting my data back. Is there a way of using the transaction log to recover the data.

ThanksIf you have backups and your db is set to full recovery, you can backup the trans log and issue the restore with StopAt.

http://msdn.microsoft.com/library/en-us/tsqlref/ts_ra-rz_25rm.asp

You could also take a look at third party app, log explorer:
http://www.lumigent.com/products/le_sql.html|||In order to use the native SQL Server backups, you need to start from a full backup, which makes sense, since it is the only way to have a point to roll transactions forward from.

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
>

Friday, March 30, 2012

Recovery options when the transaction log is unavailable

Recovery options when the transaction log is unavailable

Recovery options when the transaction log is unavailable

Recovery Models

Recovery Models

Recovery Models

Wednesday, March 28, 2012

Recovery Mode and Replication

Monday, March 26, 2012

Recovery from Delete statement using the transaction logs

Recovery from Delete statement using the transaction logs

Recovery from Delete statement using the transaction logs

Recovering using the transaction log

Friday, March 23, 2012

Recovering from transaction log deletion in 6.5

Wednesday, March 21, 2012

Recover Transaction Log

Recover Transaction Log

recover sql db with only data file

Tuesday, March 20, 2012

recover Dropped table

Monday, March 12, 2012

Recover Database Help!

Friday, March 9, 2012

Recover data with updated transaction Log only

Record Locks

Blog Archive

About Me