Showing posts with label files. Show all posts
Showing posts with label files. Show all posts

Friday, March 30, 2012

Help!! Database always In Recovery...

Hi all,

I had to change the path of .mdf and .ldf files, so I decided to:

1) Take offline the database

2) run the quey ALTER DATABASE... MODIFY to change the path

3) Bring online the database.

The last step hung up (with no errors) and left the database In Recovery.

When I tried to stop and restart sql server other databases changed their status In Recovery...

Here is a dump of Errorlog files

2007-08-26 18:13:29.28 spid24s Starting up database 'DbOrdini'.

...

...

2007-08-26 18:13:30.09 spid24s * BEGIN STACK DUMP:
2007-08-26 18:13:30.09 spid24s * 08/26/07 18:13:30 spid 24
2007-08-26 18:13:30.09 spid24s *
2007-08-26 18:13:30.09 spid24s * Location: "logmgr.cpp":5334
2007-08-26 18:13:30.09 spid24s * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)
2007-08-26 18:13:30.09 spid24s * SPID: 24
2007-08-26 18:13:30.09 spid24s * Process ID: 1380
.....

.....

2007-08-26 18:13:30.40 spid24s Error: 17066, Severity: 16, State: 1.
2007-08-26 18:13:30.40 spid24s SQL Server Assertion: File: <"logmgr.cpp">, line=5334 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2007-08-26 18:13:30.40 spid24s Error: 3624, Severity: 20, State: 1.
2007-08-26 18:13:30.40 spid24s A system assertion check has failed. Check the SQL Server error log for details

Could it be dangerous trying to kill this process ? If not, what is the best way do to it ? From Sql Server Activity Monitor (spid 24) or from Task Manager ?

Thanks in advance

you should have used Detach /attach method in this scenario. I hope u have kept backup.

(a) Detach db first

(b) copy the files to whereever u want

(c) attach the db

this should work

|||

Thanks for your answer!!

I have a backup, but I can't restore it. If I try to detach the database I get this error:

Cannot detach the database .. because it is currently in use (Sql Server Error 3703).

I can't do anything about this database, I tried to drop it, to open in emergency mode,...but nothing to do.

If I kill the process from Task Manager, do you think I colud damage other databases ?

Thanks

|||

You can't detach database when somebody is connected to it. Kill the process it will not harm... But i repeat again before doing anything on database you should have backup. Its dba mantra... Use SP_Who and see who all are connected to it kill the process and detach and attach.

otherwise you can restore the datbase with some other name using WITH MOVE option.

Madhu

|||

I have a database backup, but I would like to detach the db hanging in recovery, because when I stop and restart Sql Server other databases change their status in recovering...

I executed sp_who and sp_who2 and I get a strange result: the spid 24 (the id I get from error log files) is referred to a different database. Here is the row

CPU TIME

24 BACKGROUND sa . otherdb UNKNOWN TOKEN 13368187 43 01/01 00:00:00

To fix this problem do I have to kill the spid 24, and then detach and attach the db ?

Thanks again

|||

since the spid points to a different db as suggested by Madhu, you can try to detach it now and move the files to diff location and then attach...else try to drop the database and restore from latest backup......if nothing works try to brig the db into emergency mode as below and export the data out to a diff db

alter database dbname set emergency........may be now this command might work as there is no exclusive access to the db........

|||

I have tried to detach the database, but there's no hope, I get the message

Msg 6107, Level 14, State 1, Line 1
Only user processes can be killed.

and ALTER DATABASE dbname SET Emergency returns

User does not have permission to alter database dbname or the database does not exist.

SpId24 is a system process, so I can't kill from Management Studio.

Thanks for your replies

|||

try this...

(a) Stop the service

(c) Copy the MDF and LDF file to someother location

(d) Delete the mdf and LDF file from the current location

(e) restart the service

(f) Attach the MDF & LDF file back to server

Madhu

|||

Great!! It's worked!!!

Thanks all for the support

Help!! Database always In Recovery...

Hi all,

I had to change the path of .mdf and .ldf files, so I decided to:

1) Take offline the database

2) run the quey ALTER DATABASE... MODIFY to change the path

3) Bring online the database.

The last step hung up (with no errors) and left the database In Recovery.

When I tried to stop and restart sql server other databases changed their status In Recovery...

Here is a dump of Errorlog files

2007-08-26 18:13:29.28 spid24s Starting up database 'DbOrdini'.

...

...

2007-08-26 18:13:30.09 spid24s * BEGIN STACK DUMP:
2007-08-26 18:13:30.09 spid24s * 08/26/07 18:13:30 spid 24
2007-08-26 18:13:30.09 spid24s *
2007-08-26 18:13:30.09 spid24s * Location: "logmgr.cpp":5334
2007-08-26 18:13:30.09 spid24s * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)
2007-08-26 18:13:30.09 spid24s * SPID: 24
2007-08-26 18:13:30.09 spid24s * Process ID: 1380
.....

.....

2007-08-26 18:13:30.40 spid24s Error: 17066, Severity: 16, State: 1.
2007-08-26 18:13:30.40 spid24s SQL Server Assertion: File: <"logmgr.cpp">, line=5334 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2007-08-26 18:13:30.40 spid24s Error: 3624, Severity: 20, State: 1.
2007-08-26 18:13:30.40 spid24s A system assertion check has failed. Check the SQL Server error log for details

Could it be dangerous trying to kill this process ? If not, what is the best way do to it ? From Sql Server Activity Monitor (spid 24) or from Task Manager ?

Thanks in advance

you should have used Detach /attach method in this scenario. I hope u have kept backup.

(a) Detach db first

(b) copy the files to whereever u want

(c) attach the db

this should work

|||

Thanks for your answer!!

I have a backup, but I can't restore it. If I try to detach the database I get this error:

Cannot detach the database .. because it is currently in use (Sql Server Error 3703).

I can't do anything about this database, I tried to drop it, to open in emergency mode,...but nothing to do.

If I kill the process from Task Manager, do you think I colud damage other databases ?

Thanks

|||

You can't detach database when somebody is connected to it. Kill the process it will not harm... But i repeat again before doing anything on database you should have backup. Its dba mantra... Use SP_Who and see who all are connected to it kill the process and detach and attach.

otherwise you can restore the datbase with some other name using WITH MOVE option.

Madhu

|||

I have a database backup, but I would like to detach the db hanging in recovery, because when I stop and restart Sql Server other databases change their status in recovering...

I executed sp_who and sp_who2 and I get a strange result: the spid 24 (the id I get from error log files) is referred to a different database. Here is the row

CPU TIME

24 BACKGROUND sa . otherdb UNKNOWN TOKEN 13368187 43 01/01 00:00:00

To fix this problem do I have to kill the spid 24, and then detach and attach the db ?

Thanks again

|||

since the spid points to a different db as suggested by Madhu, you can try to detach it now and move the files to diff location and then attach...else try to drop the database and restore from latest backup......if nothing works try to brig the db into emergency mode as below and export the data out to a diff db

alter database dbname set emergency........may be now this command might work as there is no exclusive access to the db........

|||

I have tried to detach the database, but there's no hope, I get the message

Msg 6107, Level 14, State 1, Line 1
Only user processes can be killed.

and ALTER DATABASE dbname SET Emergency returns

User does not have permission to alter database dbname or the database does not exist.

SpId24 is a system process, so I can't kill from Management Studio.

Thanks for your replies

|||

try this...

(a) Stop the service

(c) Copy the MDF and LDF file to someother location

(d) Delete the mdf and LDF file from the current location

(e) restart the service

(f) Attach the MDF & LDF file back to server

Madhu

|||

Great!! It's worked!!!

Thanks all for the support

Wednesday, March 28, 2012

Help! Uninstall

Hi, Sandy
When you uninstall SQL Server (or MSDE), it leaves the database files
and the error logs (usually, in "C:\Program Files\Microsoft SQL
Server\MSSQL\Data" and "...\Log"). If the executable files were removed
(i.e. you don't have anything in "C:\Program Files\Microsoft SQL
Server\MSSQL\Binn" and in "C:\Program Files\Microsoft SQL Server\80",
etc), and if you don't need the data files, you can remove the
remaining files manually, before reinstalling SQL Server. If you do not
remove them before reinstalling, I think they would be overwritten,
anyway (without any error message).
RazvanThanks, Razvan!
--
Sandy
"Razvan Socol" wrote:

> Hi, Sandy
> When you uninstall SQL Server (or MSDE), it leaves the database files
> and the error logs (usually, in "C:\Program Files\Microsoft SQL
> Server\MSSQL\Data" and "...\Log"). If the executable files were removed
> (i.e. you don't have anything in "C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn" and in "C:\Program Files\Microsoft SQL Server\80",
> etc), and if you don't need the data files, you can remove the
> remaining files manually, before reinstalling SQL Server. If you do not
> remove them before reinstalling, I think they would be overwritten,
> anyway (without any error message).
> Razvan
>

HELP! Transaction log huge, & I'm out of space!

I have several .ldf files for one of my databases and one
of them is taking up 23 gigs. I really dont need to save
the transaction logs so I would like to just delete them
and start with a smaller log file. We created another
log file on c: now just so we can keep things running but
that is going to fill up very soon as well.
Is there any ways I can just delete the all the
transaction logs and just create one that is very small?
When I try to delete them I get an error message that
says I cant delete the file because it is not empty.
When I take the database offline to delete the file I
cant do that either because I cant access the database.
Any suggestions?
Two things:
A) Put your databases into Simple Recovery mode. They're probably in
Full Recovery mode now, which is why your logs are growing so quickly.
B) To truncate the logs, run:
BACKUP LOG DatabaseName WITH TRUNCATE_ONLY
Then use sp_helpfile to get the file ID of the log file(s), and for
each, run:
DBCC SHRINKFILE(<FileID>, EMPTYFILE)
This should drop any space available back to the operating system.
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?
|||Hi,
Detach the database. Then delete the .ldf (rename it to be on the safe
side). Then reattach the database. It will create a new .ldf. Once this
is achieved, you can permanently delete that .ldf.
If you never need the .ldf, change the recovery model to simple.
HTH,
Bernie Yaeger
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?
|||You can't attach a database with multiple log files using
sp_attach_single_file_db. The method Adam suggested is the right approach
to remove unneeded log files.
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:hsuYc.11778$Es2.6336186@.news4.srv.hcvlny.cv.n et...
> Hi,
> Detach the database. Then delete the .ldf (rename it to be on the safe
> side). Then reattach the database. It will create a new .ldf. Once this
> is achieved, you can permanently delete that .ldf.
> If you never need the .ldf, change the recovery model to simple.
> HTH,
> Bernie Yaeger
> "Groundid" <groundid@.comcast.net> wrote in message
> news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
>
|||Hi Dan,
If you either delete or rename (at the DOS level) the log file, you will not
be attaching a database with multiple log files.
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:O7raWMjjEHA.3608@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> You can't attach a database with multiple log files using
> sp_attach_single_file_db. The method Adam suggested is the right approach
> to remove unneeded log files.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:hsuYc.11778$Es2.6336186@.news4.srv.hcvlny.cv.n et...
this
>
|||"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.n et...
> If you either delete or rename (at the DOS level) the log file, you will
not
> be attaching a database with multiple log files.
Bernie,
To understand what Dan is talking about (and to get a glimpse into how I
once destroyed a weeks' worth of work and decided to never again manually
delete the log file):
Create a database with two log files. Detach it. Delete one (or both)
of the log files. Now try to re-attach it.
|||Hi groundid,
Dont delete, just shrink the file. Steps to shrink the Log file.
1. Backup the transaction log (Use command:- BACKUP Log dbname to
disk='c:\backup\dbname.tr1' (or use enterprise manager) or (if you do need
the trasaction log backup execute below command)
backup log <dbname> with truncate_only
2. Idetify the log file for shrinking:-
use <dbname>
go
sp_helpfile
Based on the name column for the transaction log file execute the dbcc
shrinkfile
3. Shrink the transaction log file.
DBCC SHRINKFILE('logical_transaction_log file name','truncateonly')
4. Check the current file size by execution
DBCC SQLPERF(LOGSPACE)
Have a look into the below article on shrink file,
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default...b;en-us;272318
Note:
Please perform a full database backup after performing the above steps, as
well as schedule a transaction log backup frequently based on ur
requirement.
Thanks
Hari
MCDBA
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?
|||Bernie, try the script below.
CREATE DATABASE TwoLogFiles ON
(NAME='TwoLogFiles',
FILENAME='C:\TwoLogFiles.mdf')
LOG ON
(NAME='TwoLogFiles_Log1',
FILENAME='C:\TwoLogFiles_Log1.ldf'),
(NAME='TwoLogFiles_Log2',
FILENAME='C:\TwoLogFiles_Log2.ldf')
EXEC sp_detach_db 'TwoLogFiles'
EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
EXEC sp_attach_db
'TwoLogFiles',
'C:\TwoLogFiles.mdf',
'C:\TwoLogFiles_Log1.ldf'
EXEC sp_attach_single_file_db
'TwoLogFiles',
'C:\TwoLogFiles.mdf'
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.n et...
> Hi Dan,
> If you either delete or rename (at the DOS level) the log file, you will
> not
> be attaching a database with multiple log files.
> Bernie
>
|||Hi Dan, Adam,
Why are you guys talking about 2 transaction logs? This guy has one.
Here's a process I've used countless times and haven't experienced any
problem:
1.. right click the database in em;
2.. select all tasks;
3.. select detach database;
4.. proceed to detach;
5.. delete the .ldf at the DOS level;
6.. right click the 'databases' line beneath the server in em; all tasks;
attach the .mdf (browse for it to the appropriate sub);
7.. it will automatically create its own blank transaction log;
I am using the simple recovery model, but I don't know if this makes any
difference.
Now tell me why this doesn't work in your opinion and explain to me why it
always works for me (SQL Server 2000).
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:uvhweXkjEHA.536@.TK2MSFTNGP11.phx.gbl...
> Bernie, try the script below.
> CREATE DATABASE TwoLogFiles ON
> (NAME='TwoLogFiles',
> FILENAME='C:\TwoLogFiles.mdf')
> LOG ON
> (NAME='TwoLogFiles_Log1',
> FILENAME='C:\TwoLogFiles_Log1.ldf'),
> (NAME='TwoLogFiles_Log2',
> FILENAME='C:\TwoLogFiles_Log2.ldf')
> EXEC sp_detach_db 'TwoLogFiles'
> EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
> EXEC sp_attach_db
> 'TwoLogFiles',
> 'C:\TwoLogFiles.mdf',
> 'C:\TwoLogFiles_Log1.ldf'
> EXEC sp_attach_single_file_db
> 'TwoLogFiles',
> 'C:\TwoLogFiles.mdf'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.n et...
>
|||Hi Dan, Adam,
Why are you guys talking about 2 transaction logs? This guy has one.
Here's a process I've used countless times and haven't experienced any
problem:
1.. right click the database in em;
2.. select all tasks;
3.. select detach database;
4.. proceed to detach;
5.. delete the .ldf at the DOS level;
6.. right click the 'databases' line beneath the server in em; all tasks;
attach the .mdf (browse for it to the appropriate sub);
7.. it will automatically create its own blank transaction log;
I am using the simple recovery model, but I don't know if this makes any
difference.
Now tell me why this doesn't work in your opinion and explain to me why it
always works for me (SQL Server 2000).
Bernie
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:%23k44GyjjEHA.1136@.tk2msftngp13.phx.gbl...
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.n et...
> not
> Bernie,
> To understand what Dan is talking about (and to get a glimpse into how
I
> once destroyed a weeks' worth of work and decided to never again manually
> delete the log file):
> Create a database with two log files. Detach it. Delete one (or
both)
> of the log files. Now try to re-attach it.
>

HELP! Transaction log huge, & I'm out of space!

I have several .ldf files for one of my databases and one
of them is taking up 23 gigs. I really dont need to save
the transaction logs so I would like to just delete them
and start with a smaller log file. We created another
log file on c: now just so we can keep things running but
that is going to fill up very soon as well.
Is there any ways I can just delete the all the
transaction logs and just create one that is very small?
When I try to delete them I get an error message that
says I cant delete the file because it is not empty.
When I take the database offline to delete the file I
cant do that either because I cant access the database.
Any suggestions?Two things:
A) Put your databases into Simple Recovery mode. They're probably in
Full Recovery mode now, which is why your logs are growing so quickly.
B) To truncate the logs, run:
BACKUP LOG DatabaseName WITH TRUNCATE_ONLY
Then use sp_helpfile to get the file ID of the log file(s), and for
each, run:
DBCC SHRINKFILE(<FileID>, EMPTYFILE)
This should drop any space available back to the operating system.
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?|||Hi,
Detach the database. Then delete the .ldf (rename it to be on the safe
side). Then reattach the database. It will create a new .ldf. Once this
is achieved, you can permanently delete that .ldf.
If you never need the .ldf, change the recovery model to simple.
HTH,
Bernie Yaeger
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?|||You can't attach a database with multiple log files using
sp_attach_single_file_db. The method Adam suggested is the right approach
to remove unneeded log files.
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:hsuYc.11778$Es2.6336186@.news4.srv.hcvlny.cv.net...
> Hi,
> Detach the database. Then delete the .ldf (rename it to be on the safe
> side). Then reattach the database. It will create a new .ldf. Once this
> is achieved, you can permanently delete that .ldf.
> If you never need the .ldf, change the recovery model to simple.
> HTH,
> Bernie Yaeger
> "Groundid" <groundid@.comcast.net> wrote in message
> news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
>|||Hi Dan,
If you either delete or rename (at the DOS level) the log file, you will not
be attaching a database with multiple log files.
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:O7raWMjjEHA.3608@.TK2MSFTNGP09.phx.gbl...
> You can't attach a database with multiple log files using
> sp_attach_single_file_db. The method Adam suggested is the right approach
> to remove unneeded log files.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:hsuYc.11778$Es2.6336186@.news4.srv.hcvlny.cv.net...
this[vbcol=seagreen]
>|||"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> If you either delete or rename (at the DOS level) the log file, you will
not
> be attaching a database with multiple log files.
Bernie,
To understand what Dan is talking about (and to get a glimpse into how I
once destroyed a weeks' worth of work and decided to never again manually
delete the log file):
Create a database with two log files. Detach it. Delete one (or both)
of the log files. Now try to re-attach it.|||Hi groundid,
Dont delete, just shrink the file. Steps to shrink the Log file.
1. Backup the transaction log (Use command:- BACKUP Log dbname to
disk='c:\backup\dbname.tr1' (or use enterprise manager) or (if you do need
the trasaction log backup execute below command)
backup log <dbname> with truncate_only
2. Idetify the log file for shrinking:-
use <dbname>
go
sp_helpfile
Based on the name column for the transaction log file execute the dbcc
shrinkfile
3. Shrink the transaction log file.
DBCC SHRINKFILE('logical_transaction_log file name','truncateonly')
4. Check the current file size by execution
DBCC SQLPERF(LOGSPACE)
Have a look into the below article on shrink file,
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/defaul...kb;en-us;272318
Note:
Please perform a full database backup after performing the above steps, as
well as schedule a transaction log backup frequently based on ur
requirement.
Thanks
Hari
MCDBA
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?|||Bernie, try the script below.
CREATE DATABASE TwoLogFiles ON
(NAME='TwoLogFiles',
FILENAME='C:\TwoLogFiles.mdf')
LOG ON
(NAME='TwoLogFiles_Log1',
FILENAME='C:\TwoLogFiles_Log1.ldf'),
(NAME='TwoLogFiles_Log2',
FILENAME='C:\TwoLogFiles_Log2.ldf')
EXEC sp_detach_db 'TwoLogFiles'
EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
EXEC sp_attach_db
'TwoLogFiles',
'C:\TwoLogFiles.mdf',
'C:\TwoLogFiles_Log1.ldf'
EXEC sp_attach_single_file_db
'TwoLogFiles',
'C:\TwoLogFiles.mdf'
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> Hi Dan,
> If you either delete or rename (at the DOS level) the log file, you will
> not
> be attaching a database with multiple log files.
> Bernie
>|||Hi Dan, Adam,
Why are you guys talking about 2 transaction logs? This guy has one.
Here's a process I've used countless times and haven't experienced any
problem:
1.. right click the database in em;
2.. select all tasks;
3.. select detach database;
4.. proceed to detach;
5.. delete the .ldf at the DOS level;
6.. right click the 'databases' line beneath the server in em; all tasks;
attach the .mdf (browse for it to the appropriate sub);
7.. it will automatically create its own blank transaction log;
I am using the simple recovery model, but I don't know if this makes any
difference.
Now tell me why this doesn't work in your opinion and explain to me why it
always works for me (SQL Server 2000).
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:uvhweXkjEHA.536@.TK2MSFTNGP11.phx.gbl...
> Bernie, try the script below.
> CREATE DATABASE TwoLogFiles ON
> (NAME='TwoLogFiles',
> FILENAME='C:\TwoLogFiles.mdf')
> LOG ON
> (NAME='TwoLogFiles_Log1',
> FILENAME='C:\TwoLogFiles_Log1.ldf'),
> (NAME='TwoLogFiles_Log2',
> FILENAME='C:\TwoLogFiles_Log2.ldf')
> EXEC sp_detach_db 'TwoLogFiles'
> EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
> EXEC sp_attach_db
> 'TwoLogFiles',
> 'C:\TwoLogFiles.mdf',
> 'C:\TwoLogFiles_Log1.ldf'
> EXEC sp_attach_single_file_db
> 'TwoLogFiles',
> 'C:\TwoLogFiles.mdf'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
>|||Hi Dan, Adam,
Why are you guys talking about 2 transaction logs? This guy has one.
Here's a process I've used countless times and haven't experienced any
problem:
1.. right click the database in em;
2.. select all tasks;
3.. select detach database;
4.. proceed to detach;
5.. delete the .ldf at the DOS level;
6.. right click the 'databases' line beneath the server in em; all tasks;
attach the .mdf (browse for it to the appropriate sub);
7.. it will automatically create its own blank transaction log;
I am using the simple recovery model, but I don't know if this makes any
difference.
Now tell me why this doesn't work in your opinion and explain to me why it
always works for me (SQL Server 2000).
Bernie
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:%23k44GyjjEHA.1136@.tk2msftngp13.phx.gbl...
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> not
> Bernie,
> To understand what Dan is talking about (and to get a glimpse into how
I
> once destroyed a weeks' worth of work and decided to never again manually
> delete the log file):
> Create a database with two log files. Detach it. Delete one (or
both)
> of the log files. Now try to re-attach it.
>sql

HELP! Transaction log huge, & I'm out of space!

I have several .ldf files for one of my databases and one
of them is taking up 23 gigs. I really dont need to save
the transaction logs so I would like to just delete them
and start with a smaller log file. We created another
log file on c: now just so we can keep things running but
that is going to fill up very soon as well.
Is there any ways I can just delete the all the
transaction logs and just create one that is very small?
When I try to delete them I get an error message that
says I cant delete the file because it is not empty.
When I take the database offline to delete the file I
cant do that either because I cant access the database.
Any suggestions?Two things:
A) Put your databases into Simple Recovery mode. They're probably in
Full Recovery mode now, which is why your logs are growing so quickly.
B) To truncate the logs, run:
BACKUP LOG DatabaseName WITH TRUNCATE_ONLY
Then use sp_helpfile to get the file ID of the log file(s), and for
each, run:
DBCC SHRINKFILE(<FileID>, EMPTYFILE)
This should drop any space available back to the operating system.
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?|||Hi,
Detach the database. Then delete the .ldf (rename it to be on the safe
side). Then reattach the database. It will create a new .ldf. Once this
is achieved, you can permanently delete that .ldf.
If you never need the .ldf, change the recovery model to simple.
HTH,
Bernie Yaeger
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?|||You can't attach a database with multiple log files using
sp_attach_single_file_db. The method Adam suggested is the right approach
to remove unneeded log files.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:hsuYc.11778$Es2.6336186@.news4.srv.hcvlny.cv.net...
> Hi,
> Detach the database. Then delete the .ldf (rename it to be on the safe
> side). Then reattach the database. It will create a new .ldf. Once this
> is achieved, you can permanently delete that .ldf.
> If you never need the .ldf, change the recovery model to simple.
> HTH,
> Bernie Yaeger
> "Groundid" <groundid@.comcast.net> wrote in message
> news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
>> I have several .ldf files for one of my databases and one
>> of them is taking up 23 gigs. I really dont need to save
>> the transaction logs so I would like to just delete them
>> and start with a smaller log file. We created another
>> log file on c: now just so we can keep things running but
>> that is going to fill up very soon as well.
>> Is there any ways I can just delete the all the
>> transaction logs and just create one that is very small?
>> When I try to delete them I get an error message that
>> says I cant delete the file because it is not empty.
>> When I take the database offline to delete the file I
>> cant do that either because I cant access the database.
>> Any suggestions?
>|||Hi Dan,
If you either delete or rename (at the DOS level) the log file, you will not
be attaching a database with multiple log files.
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:O7raWMjjEHA.3608@.TK2MSFTNGP09.phx.gbl...
> You can't attach a database with multiple log files using
> sp_attach_single_file_db. The method Adam suggested is the right approach
> to remove unneeded log files.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:hsuYc.11778$Es2.6336186@.news4.srv.hcvlny.cv.net...
> > Hi,
> >
> > Detach the database. Then delete the .ldf (rename it to be on the safe
> > side). Then reattach the database. It will create a new .ldf. Once
this
> > is achieved, you can permanently delete that .ldf.
> >
> > If you never need the .ldf, change the recovery model to simple.
> >
> > HTH,
> >
> > Bernie Yaeger
> >
> > "Groundid" <groundid@.comcast.net> wrote in message
> > news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> >> I have several .ldf files for one of my databases and one
> >> of them is taking up 23 gigs. I really dont need to save
> >> the transaction logs so I would like to just delete them
> >> and start with a smaller log file. We created another
> >> log file on c: now just so we can keep things running but
> >> that is going to fill up very soon as well.
> >>
> >> Is there any ways I can just delete the all the
> >> transaction logs and just create one that is very small?
> >> When I try to delete them I get an error message that
> >> says I cant delete the file because it is not empty.
> >> When I take the database offline to delete the file I
> >> cant do that either because I cant access the database.
> >> Any suggestions?
> >
> >
>|||"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> If you either delete or rename (at the DOS level) the log file, you will
not
> be attaching a database with multiple log files.
Bernie,
To understand what Dan is talking about (and to get a glimpse into how I
once destroyed a weeks' worth of work and decided to never again manually
delete the log file):
Create a database with two log files. Detach it. Delete one (or both)
of the log files. Now try to re-attach it.|||Hi groundid,
Dont delete, just shrink the file. Steps to shrink the Log file.
1. Backup the transaction log (Use command:- BACKUP Log dbname to
disk='c:\backup\dbname.tr1' (or use enterprise manager) or (if you do need
the trasaction log backup execute below command)
backup log <dbname> with truncate_only
2. Idetify the log file for shrinking:-
use <dbname>
go
sp_helpfile
Based on the name column for the transaction log file execute the dbcc
shrinkfile
3. Shrink the transaction log file.
DBCC SHRINKFILE('logical_transaction_log file name','truncateonly')
4. Check the current file size by execution
DBCC SQLPERF(LOGSPACE)
Have a look into the below article on shrink file,
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Note:
Please perform a full database backup after performing the above steps, as
well as schedule a transaction log backup frequently based on ur
requirement.
Thanks
Hari
MCDBA
"Groundid" <groundid@.comcast.net> wrote in message
news:24e601c48dee$ca240e70$a301280a@.phx.gbl...
> I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs. I really dont need to save
> the transaction logs so I would like to just delete them
> and start with a smaller log file. We created another
> log file on c: now just so we can keep things running but
> that is going to fill up very soon as well.
> Is there any ways I can just delete the all the
> transaction logs and just create one that is very small?
> When I try to delete them I get an error message that
> says I cant delete the file because it is not empty.
> When I take the database offline to delete the file I
> cant do that either because I cant access the database.
> Any suggestions?|||Bernie, try the script below.
CREATE DATABASE TwoLogFiles ON
(NAME='TwoLogFiles',
FILENAME='C:\TwoLogFiles.mdf')
LOG ON
(NAME='TwoLogFiles_Log1',
FILENAME='C:\TwoLogFiles_Log1.ldf'),
(NAME='TwoLogFiles_Log2',
FILENAME='C:\TwoLogFiles_Log2.ldf')
EXEC sp_detach_db 'TwoLogFiles'
EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
EXEC sp_attach_db
'TwoLogFiles',
'C:\TwoLogFiles.mdf',
'C:\TwoLogFiles_Log1.ldf'
EXEC sp_attach_single_file_db
'TwoLogFiles',
'C:\TwoLogFiles.mdf'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> Hi Dan,
> If you either delete or rename (at the DOS level) the log file, you will
> not
> be attaching a database with multiple log files.
> Bernie
>|||Hi Dan, Adam,
Why are you guys talking about 2 transaction logs? This guy has one.
Here's a process I've used countless times and haven't experienced any
problem:
1.. right click the database in em;
2.. select all tasks;
3.. select detach database;
4.. proceed to detach;
5.. delete the .ldf at the DOS level;
6.. right click the 'databases' line beneath the server in em; all tasks;
attach the .mdf (browse for it to the appropriate sub);
7.. it will automatically create its own blank transaction log;
I am using the simple recovery model, but I don't know if this makes any
difference.
Now tell me why this doesn't work in your opinion and explain to me why it
always works for me (SQL Server 2000).
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:uvhweXkjEHA.536@.TK2MSFTNGP11.phx.gbl...
> Bernie, try the script below.
> CREATE DATABASE TwoLogFiles ON
> (NAME='TwoLogFiles',
> FILENAME='C:\TwoLogFiles.mdf')
> LOG ON
> (NAME='TwoLogFiles_Log1',
> FILENAME='C:\TwoLogFiles_Log1.ldf'),
> (NAME='TwoLogFiles_Log2',
> FILENAME='C:\TwoLogFiles_Log2.ldf')
> EXEC sp_detach_db 'TwoLogFiles'
> EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
> EXEC sp_attach_db
> 'TwoLogFiles',
> 'C:\TwoLogFiles.mdf',
> 'C:\TwoLogFiles_Log1.ldf'
> EXEC sp_attach_single_file_db
> 'TwoLogFiles',
> 'C:\TwoLogFiles.mdf'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> > Hi Dan,
> >
> > If you either delete or rename (at the DOS level) the log file, you will
> > not
> > be attaching a database with multiple log files.
> >
> > Bernie
> >
>|||Hi Dan, Adam,
Why are you guys talking about 2 transaction logs? This guy has one.
Here's a process I've used countless times and haven't experienced any
problem:
1.. right click the database in em;
2.. select all tasks;
3.. select detach database;
4.. proceed to detach;
5.. delete the .ldf at the DOS level;
6.. right click the 'databases' line beneath the server in em; all tasks;
attach the .mdf (browse for it to the appropriate sub);
7.. it will automatically create its own blank transaction log;
I am using the simple recovery model, but I don't know if this makes any
difference.
Now tell me why this doesn't work in your opinion and explain to me why it
always works for me (SQL Server 2000).
Bernie
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:%23k44GyjjEHA.1136@.tk2msftngp13.phx.gbl...
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> >
> > If you either delete or rename (at the DOS level) the log file, you will
> not
> > be attaching a database with multiple log files.
> Bernie,
> To understand what Dan is talking about (and to get a glimpse into how
I
> once destroyed a weeks' worth of work and decided to never again manually
> delete the log file):
> Create a database with two log files. Detach it. Delete one (or
both)
> of the log files. Now try to re-attach it.
>|||Bernie,
> Why are you guys talking about 2 transaction logs? This guy has one.
Here's a quote from the OP:
"I have several .ldf files for one of my databases and one
of them is taking up 23 gigs."
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/|||> Why are you guys talking about 2 transaction logs? This guy has one.
As Tibor mentioned, the OP has multiple logs.
The procedure you suggest out to work with a single log file but is not the
preferred method. Even with a single log, the best approach to reduce log
file size is DBCC SHRINKFILE. This doesn't require the database to be
detached.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:MiFYc.18971$Es2.8127856@.news4.srv.hcvlny.cv.net...
> Hi Dan, Adam,
> Why are you guys talking about 2 transaction logs? This guy has one.
> Here's a process I've used countless times and haven't experienced any
> problem:
> 1.. right click the database in em;
> 2.. select all tasks;
> 3.. select detach database;
> 4.. proceed to detach;
> 5.. delete the .ldf at the DOS level;
> 6.. right click the 'databases' line beneath the server in em; all tasks;
> attach the .mdf (browse for it to the appropriate sub);
> 7.. it will automatically create its own blank transaction log;
> I am using the simple recovery model, but I don't know if this makes any
> difference.
> Now tell me why this doesn't work in your opinion and explain to me why it
> always works for me (SQL Server 2000).
> Bernie
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:uvhweXkjEHA.536@.TK2MSFTNGP11.phx.gbl...
>> Bernie, try the script below.
>> CREATE DATABASE TwoLogFiles ON
>> (NAME='TwoLogFiles',
>> FILENAME='C:\TwoLogFiles.mdf')
>> LOG ON
>> (NAME='TwoLogFiles_Log1',
>> FILENAME='C:\TwoLogFiles_Log1.ldf'),
>> (NAME='TwoLogFiles_Log2',
>> FILENAME='C:\TwoLogFiles_Log2.ldf')
>> EXEC sp_detach_db 'TwoLogFiles'
>> EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
>> EXEC sp_attach_db
>> 'TwoLogFiles',
>> 'C:\TwoLogFiles.mdf',
>> 'C:\TwoLogFiles_Log1.ldf'
>> EXEC sp_attach_single_file_db
>> 'TwoLogFiles',
>> 'C:\TwoLogFiles.mdf'
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
>> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
>> > Hi Dan,
>> >
>> > If you either delete or rename (at the DOS level) the log file, you
>> > will
>> > not
>> > be attaching a database with multiple log files.
>> >
>> > Bernie
>> >
>>
>|||Hi Tibor,
You're correct - I misread his question. Tx
Bernie
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23l2Sv9ojEHA.3876@.TK2MSFTNGP15.phx.gbl...
> Bernie,
> > Why are you guys talking about 2 transaction logs? This guy has one.
> Here's a quote from the OP:
> "I have several .ldf files for one of my databases and one
> of them is taking up 23 gigs."
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>|||Hi Dan,
You're correct - I misread the initial question. Sorry.
Bernie
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:ewXt$lpjEHA.2788@.tk2msftngp13.phx.gbl...
> > Why are you guys talking about 2 transaction logs? This guy has one.
> As Tibor mentioned, the OP has multiple logs.
> The procedure you suggest out to work with a single log file but is not
the
> preferred method. Even with a single log, the best approach to reduce log
> file size is DBCC SHRINKFILE. This doesn't require the database to be
> detached.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> news:MiFYc.18971$Es2.8127856@.news4.srv.hcvlny.cv.net...
> > Hi Dan, Adam,
> >
> > Why are you guys talking about 2 transaction logs? This guy has one.
> > Here's a process I've used countless times and haven't experienced any
> > problem:
> > 1.. right click the database in em;
> > 2.. select all tasks;
> > 3.. select detach database;
> > 4.. proceed to detach;
> > 5.. delete the .ldf at the DOS level;
> > 6.. right click the 'databases' line beneath the server in em; all
tasks;
> > attach the .mdf (browse for it to the appropriate sub);
> > 7.. it will automatically create its own blank transaction log;
> > I am using the simple recovery model, but I don't know if this makes any
> > difference.
> >
> > Now tell me why this doesn't work in your opinion and explain to me why
it
> > always works for me (SQL Server 2000).
> >
> > Bernie
> >
> > "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> > news:uvhweXkjEHA.536@.TK2MSFTNGP11.phx.gbl...
> >> Bernie, try the script below.
> >>
> >> CREATE DATABASE TwoLogFiles ON
> >> (NAME='TwoLogFiles',
> >> FILENAME='C:\TwoLogFiles.mdf')
> >> LOG ON
> >> (NAME='TwoLogFiles_Log1',
> >> FILENAME='C:\TwoLogFiles_Log1.ldf'),
> >> (NAME='TwoLogFiles_Log2',
> >> FILENAME='C:\TwoLogFiles_Log2.ldf')
> >>
> >> EXEC sp_detach_db 'TwoLogFiles'
> >>
> >> EXEC master..xp_cmdshell 'DEL C:\TwoLogFiles_Log2.ldf'
> >>
> >> EXEC sp_attach_db
> >> 'TwoLogFiles',
> >> 'C:\TwoLogFiles.mdf',
> >> 'C:\TwoLogFiles_Log1.ldf'
> >>
> >> EXEC sp_attach_single_file_db
> >> 'TwoLogFiles',
> >> 'C:\TwoLogFiles.mdf'
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
> >> news:fmwYc.12253$Es2.6666988@.news4.srv.hcvlny.cv.net...
> >> > Hi Dan,
> >> >
> >> > If you either delete or rename (at the DOS level) the log file, you
> >> > will
> >> > not
> >> > be attaching a database with multiple log files.
> >> >
> >> > Bernie
> >> >
> >>
> >>
> >
> >
>

Friday, March 23, 2012

HELP! Please Server Crash

I have had a piece of hardware fail (motherboard died),
and I don't have a back up of the entire SQL Box. What I
do have is all the files, master, tempdb, etc etc... in
the directory on the hard drive they were on. They are
fine.
I can't get SQL to run on another box tho, and there is a
humongous amount of jobs, and dts' that I need from there.
The data is fine, but is there a way to get this server
to run on another box?
I am in desparate need.
THank you
SvenInstall SQL Server on the new box .If you remember the paths for the install
,set it up in that fashion. Once completed, stop the SQL server service and
if you remember the exact path names/locations of your data files and log
files , you could restore all those files exactly in the same location
before you start the SQL Server instance on the other box. Give that a try..
"Sven Hansen" <shansen@.westjet.com> wrote in message
news:00c001c3c914$177c3210$a001280a@.phx.gbl...
> I have had a piece of hardware fail (motherboard died),
> and I don't have a back up of the entire SQL Box. What I
> do have is all the files, master, tempdb, etc etc... in
> the directory on the hard drive they were on. They are
> fine.
> I can't get SQL to run on another box tho, and there is a
> humongous amount of jobs, and dts' that I need from there.
> The data is fine, but is there a way to get this server
> to run on another box?
> I am in desparate need.
> THank you
> Sven
>|||After you install SQL , then stop the services and copy all of the files
back. You would then have to use sp_attach_db to attach the non-system
databases..
THe copying over of master, model , tempdb and msdb may or may not work...
The very least thing is that you MUST use the same collation that was
originally used...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.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
"Sven Hansen" <shansen@.westjet.com> wrote in message
news:00c001c3c914$177c3210$a001280a@.phx.gbl...
> I have had a piece of hardware fail (motherboard died),
> and I don't have a back up of the entire SQL Box. What I
> do have is all the files, master, tempdb, etc etc... in
> the directory on the hard drive they were on. They are
> fine.
> I can't get SQL to run on another box tho, and there is a
> humongous amount of jobs, and dts' that I need from there.
> The data is fine, but is there a way to get this server
> to run on another box?
> I am in desparate need.
> THank you
> Sven
>sql

Wednesday, March 21, 2012

HELP! Lost LDF file, multiple MDF files, no backups!

I am desperate...
I have a database (I didn't build this one...) where there are 4 MDF
files, and in trying to clear out the two LDF files, which where
initially set to autogrow and were larger than the actual database,
and backup of the transaction log didn't shrink it, I detached the
database, deleted the LDF files, and tried to reattach, which, when
there is a single MDF file, it works!! I cannot reattach this
database!!
Here is the error:
Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
aborted.
Device activation error. The physical file name 'd:\yadayada_01.ldf'
may be incorrect.
Device activation error. The physical file name 'd:\yadayada_02.ldf'
may be incorrect.
I've tried everything I can think of... trying to figure this out
before someone notices (its not a very often used database).
Please help...
Thanks,
CalgaryDataGrl
Hello,
Try using the Create Database with Attach_Rebuild_Log option. See the below
eg:-
USE [master]
GO
CREATE DATABASE [Test] ON
(FILENAME = N'D:\Data\Test_data.mdf')
FOR ATTACH_REBUILD_LOG
GO
Thanks
Hari
"CalgaryDataGrl" <calgarydatagrl@.gmail.com> wrote in message
news:1171323042.569709.53480@.l53g2000cwa.googlegro ups.com...
>I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
>
|||On 12 Feb, 23:30, "CalgaryDataGrl" <calgarydata...@.gmail.com> wrote:
> I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
Please don't delete log files. That's a great way to lose data.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||On Feb 13, 5:30 am, "CalgaryDataGrl" <calgarydata...@.gmail.com> wrote:
> I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
You should have kept a backup (copy the files into a separate
directory) before making drastic changes so that you can revert to
original state in case things just work out the way you wanted (in
this situation).

HELP! Lost LDF file, multiple MDF files, no backups!

I am desperate...
I have a database (I didn't build this one...) where there are 4 MDF
files, and in trying to clear out the two LDF files, which where
initially set to autogrow and were larger than the actual database,
and backup of the transaction log didn't shrink it, I detached the
database, deleted the LDF files, and tried to reattach, which, when
there is a single MDF file, it works!! I cannot reattach this
database!!
Here is the error:
Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
aborted.
Device activation error. The physical file name 'd:\yadayada_01.ldf'
may be incorrect.
Device activation error. The physical file name 'd:\yadayada_02.ldf'
may be incorrect.
I've tried everything I can think of... trying to figure this out
before someone notices (its not a very often used database).
Please help...
Thanks,
CalgaryDataGrlHello,
Try using the Create Database with Attach_Rebuild_Log option. See the below
eg:-
USE [master]
GO
CREATE DATABASE [Test] ON
(FILENAME = N'D:\Data\Test_data.mdf')
FOR ATTACH_REBUILD_LOG
GO
Thanks
Hari
"CalgaryDataGrl" <calgarydatagrl@.gmail.com> wrote in message
news:1171323042.569709.53480@.l53g2000cwa.googlegroups.com...
>I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
>|||On Feb 12, 6:09 pm, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> Hello,
> Try using the Create Database with Attach_Rebuild_Log option. See the bel
ow
> eg:-
> USE [master]
> GO
> CREATE DATABASE [Test] ON
> (FILENAME = N'D:\Data\Test_data.mdf')
> FOR ATTACH_REBUILD_LOG
> GO
> Thanks
> Hari
>
Hi Hari,
I'm getting an error:
Server: Msg 102, Level 15, State 1, Line 3
Incorrect syntax near 'ATTACH_REBUILD_LOG'.
Any thoughts?
Stacy|||Are you on SQL Server 2005?
You should probably contact product support to help walk you through this
correctly - and you should get yourself a decent backup strategy. Send me
mail through the blog link below if you want help with this.
Paul Randal
Principal Lead Program Manager
Core Storage Engine, Microsoft SQL Server Team
http://blogs.msdn.com/sqlserverstor...ne/default.aspx
"CalgaryDataGrl" <calgarydatagrl@.gmail.com> wrote in message
news:1171556088.308708.76810@.p10g2000cwp.googlegroups.com...
> On Feb 12, 6:09 pm, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> Hi Hari,
> I'm getting an error:
>
> Server: Msg 102, Level 15, State 1, Line 3
> Incorrect syntax near 'ATTACH_REBUILD_LOG'.
> Any thoughts?
> Stacy
>|||On 12 Feb, 23:30, "CalgaryDataGrl" <calgarydata...@.gmail.com> wrote:
> I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
Please don't delete log files. That's a great way to lose data.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||On Feb 13, 5:30 am, "CalgaryDataGrl" <calgarydata...@.gmail.com> wrote:
> I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
You should have kept a backup (copy the files into a separate
directory) before making drastic changes so that you can revert to
original state in case things just work out the way you wanted (in
this situation).

HELP! Lost LDF file, multiple MDF files, no backups!

I am desperate...
I have a database (I didn't build this one...) where there are 4 MDF
files, and in trying to clear out the two LDF files, which where
initially set to autogrow and were larger than the actual database,
and backup of the transaction log didn't shrink it, I detached the
database, deleted the LDF files, and tried to reattach, which, when
there is a single MDF file, it works!! I cannot reattach this
database!!
Here is the error:
Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
aborted.
Device activation error. The physical file name 'd:\yadayada_01.ldf'
may be incorrect.
Device activation error. The physical file name 'd:\yadayada_02.ldf'
may be incorrect.
I've tried everything I can think of... trying to figure this out
before someone notices (its not a very often used database).
Please help...
Thanks,
CalgaryDataGrlHello,
Try using the Create Database with Attach_Rebuild_Log option. See the below
eg:-
USE [master]
GO
CREATE DATABASE [Test] ON
(FILENAME = N'D:\Data\Test_data.mdf')
FOR ATTACH_REBUILD_LOG
GO
Thanks
Hari
"CalgaryDataGrl" <calgarydatagrl@.gmail.com> wrote in message
news:1171323042.569709.53480@.l53g2000cwa.googlegroups.com...
>I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
>|||On Feb 12, 6:09 pm, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
> Hello,
> Try using the Create Database with Attach_Rebuild_Log option. See the below
> eg:-
> USE [master]
> GO
> CREATE DATABASE [Test] ON
> (FILENAME = N'D:\Data\Test_data.mdf')
> FOR ATTACH_REBUILD_LOG
> GO
> Thanks
> Hari
>
Hi Hari,
I'm getting an error:
Server: Msg 102, Level 15, State 1, Line 3
Incorrect syntax near 'ATTACH_REBUILD_LOG'.
Any thoughts?
Stacy|||Are you on SQL Server 2005?
You should probably contact product support to help walk you through this
correctly - and you should get yourself a decent backup strategy. Send me
mail through the blog link below if you want help with this.
--
Paul Randal
Principal Lead Program Manager
Core Storage Engine, Microsoft SQL Server Team
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
"CalgaryDataGrl" <calgarydatagrl@.gmail.com> wrote in message
news:1171556088.308708.76810@.p10g2000cwp.googlegroups.com...
> On Feb 12, 6:09 pm, "Hari Prasad" <hari_prasa...@.hotmail.com> wrote:
>> Hello,
>> Try using the Create Database with Attach_Rebuild_Log option. See the
>> below
>> eg:-
>> USE [master]
>> GO
>> CREATE DATABASE [Test] ON
>> (FILENAME = N'D:\Data\Test_data.mdf')
>> FOR ATTACH_REBUILD_LOG
>> GO
>> Thanks
>> Hari
> Hi Hari,
> I'm getting an error:
>
> Server: Msg 102, Level 15, State 1, Line 3
> Incorrect syntax near 'ATTACH_REBUILD_LOG'.
> Any thoughts?
> Stacy
>|||On 12 Feb, 23:30, "CalgaryDataGrl" <calgarydata...@.gmail.com> wrote:
> I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
Please don't delete log files. That's a great way to lose data.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||On Feb 13, 5:30 am, "CalgaryDataGrl" <calgarydata...@.gmail.com> wrote:
> I am desperate...
> I have a database (I didn't build this one...) where there are 4 MDF
> files, and in trying to clear out the two LDF files, which where
> initially set to autogrow and were larger than the actual database,
> and backup of the transaction log didn't shrink it, I detached the
> database, deleted the LDF files, and tried to reattach, which, when
> there is a single MDF file, it works!! I cannot reattach this
> database!!
> Here is the error:
> Error 1813: Could not open new database 'dbname'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'd:\yadayada_01.ldf'
> may be incorrect.
> Device activation error. The physical file name 'd:\yadayada_02.ldf'
> may be incorrect.
> I've tried everything I can think of... trying to figure this out
> before someone notices (its not a very often used database).
> Please help...
> Thanks,
> CalgaryDataGrl
You should have kept a backup (copy the files into a separate
directory) before making drastic changes so that you can revert to
original state in case things just work out the way you wanted (in
this situation).

Help! ISQL and DOS batch files

Hi all,

Can anyone help me?? I'm just a newb :D

Please consider the following:

I need to be able to query a db on server A, in a batch file, return the result (DateTime value) into a variable, and then use that date as a parameter in a query that I will query on server b.

I have the following code:

isql -E -d firstDB -S ServerA -Q "select max(load_date) from mydates"

How would I pipe the results of the above query into a variable?

I cannot create a linked server between the two servers. (Permissions)

Thanks in advance!My first suggestion would be to use either DTS or Perl instead of batch files. They simplify problems like this a bunch.

My next suggestion would be to use OSQL.EXE if you must use a batch file. It is better suited for many reasons than ISQL.EXE is.

You can send the OSQL.EXE output to a text file using the -o parameter. Once you get the data into a text file, you'll need to find a way to harvest it for use in the next query... This is where a scripting language like what exists in DTS or Perl really helps.

-PatP|||Thx, Pat.

I am also familiar with OSQL, but I've never used DTS. Looks like I have some reading to do this weekend :p

In the meantime, it's hokey, but I think I'm gonna BCP the data into the pubs db on the server as a temporary solution.

Thanks, I wouldn't have thought of it.|||If all you need is 1 parameter, then this would do:

osql -E -d firstDB -S ServerA -Q "select 'select * from other_server_table where load_date = ' + (select '''' + convert(char(10), max(load_date), 101) + '''' from mydates)" -o script.SQL

osql -E -d secondDB -S ServerB -i script.SQL|||Can you use OPENQUERY or is that also restricted? Can you use sp_Oacreate? See this link for an example of retrieving a single value with an ADODB connection and T-SQL.

http://www.davidpenton.com/testsite/scratch/dbo.sp_ExecuteAdodbScalar.txt|||If all you need is 1 parameter, then this would do:

osql -E -d firstDB -S ServerA -Q "select 'select * from other_server_table where load_date = ' + (select '''' + convert(char(10), max(load_date), 101) + '''' from mydates)" -o script.SQL

osql -E -d secondDB -S ServerB -i script.SQLNow that's just plain deviant ;)

I thought I was the only one that did perverse things like that, although I've been known to create whole scripts (breaking the 8K limit was my biggest challenge) that way!

It still isn't something I'd try to teach a newcomer, but it is a great thing to have lurking in one's bag of tricks.

-PatP|||rdjabarov, that was wild!! :) That is exactly the approach I am going to use! My query was a little too long, but I just seperated it into columns, and used "" as a col seperator. And voil! This way, I can also archive my query, as I try to avoid hard coding wherever possible. I'll have to comment a lot, but it's a whole lot less hokey than what I was planning to do!!!

vaxman- I cannot use sp_Oacreate - permissions. :(

Pat - Thanks for the suggestions, I'm still going to look into DTS, as it looks on first glance as a pretty powerful tool.

WooHoo! Thanks everyone!!|||Not really elegant, but running
isql -E -d firstDB -S ServerA -Q "select 'set MyVariable='+convert(varchar(15), max(load_date), 111) from mydates" -o myBat.bat

call myBat.batsql

Monday, March 19, 2012

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I a
m
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........
Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

Help! How can I attach a DB with Corrupted Log Files

I have a backup of a Database files that its log files are damaged ( so I
can't attach it to SQL Server) please tell me if there is a way to attach a
database when its log files are corrupted? ( this DB has two ndf files so I
couldn't use the sp_attach_single_db_file)Look at
Syntax
sp_attach_single_file_db [ @.dbname = ] 'dbname'
, [ @.physname = ] 'physical_name'
in BOL
"Par" <beatles1692@.yahoo.com> wrote in message
news:#$q3$tcdDHA.656@.tk2msftngp13.phx.gbl...
> I have a backup of a Database files that its log files are damaged ( so I
> can't attach it to SQL Server) please tell me if there is a way to attach
a
> database when its log files are corrupted? ( this DB has two ndf files so
I
> couldn't use the sp_attach_single_db_file)
>|||You might try to
1. save off the good mdf and ndf files.
2. recreate the database with the same structure.
3. detach the new empty db,
and try using THAT log to re-attach the originals...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.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
"Par" <beatles1692@.yahoo.com> wrote in message
news:%23$q3$tcdDHA.656@.tk2msftngp13.phx.gbl...
> I have a backup of a Database files that its log files are damaged ( so I
> can't attach it to SQL Server) please tell me if there is a way to attach
a
> database when its log files are corrupted? ( this DB has two ndf files so
I
> couldn't use the sp_attach_single_db_file)
>|||This may be of interest:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
--
Andrew J. Kelly
SQL Server MVP
"Par" <beatles1692@.yahoo.com> wrote in message
news:%23$q3$tcdDHA.656@.tk2msftngp13.phx.gbl...
> I have a backup of a Database files that its log files are damaged ( so I
> can't attach it to SQL Server) please tell me if there is a way to attach
a
> database when its log files are corrupted? ( this DB has two ndf files so
I
> couldn't use the sp_attach_single_db_file)
>

Wednesday, March 7, 2012

Help! "Remove files older than 1 week" is not there!

Help!
When I use the Enterprise Manager and create a Database Maintenance Plan
there is an option which will allow me to "Remove files older than 'X'
days".
The only problem is that the drop-down box that is supposed to let me choose
"days, hours, weeks" etc is completely blank! This means that this function
is unavailable to me, thus my hard drive keeps filling up! Please help!
How can I fix this?
I have included a screen shot of this problem.
Michaaael
begin 666 EnterpriseManager.jpg
M_]C_X `02D9)1@.`!`0```0`!``#_VP!#``8$!08%! 8&!08'!P8("A *"@.D)
M"A0.#PP0%Q08&!<4%A8:'24?&ALC'!86("P@.(R8G*2HI&1\M, "TH,"4H*2C_
MVP!#`0<'!PH("A,*"A,H&A8:*"@.H*"@.H*"@.H*"@.H*"@.H*"@.H* "@.H*"@.H*"@.H
M*"@.H*"@.H*"@.H*"@.H*"@.H*"@.H*"@.H*"C_P `1" &)`?@.#`2(``A$!`Q$!_\0`
M'0`!``(#`0$!`0````````````4&`P0'" D"`?_$`&$0``$#`P("! @.)!P<(
M!0D)`0$"`P0`!1$&$A,A!Q0BE146,4%35I32%R,R4515M-'3-T)A=I*3U#-2
M<76#D>0D-#9S=*2SPP@.E@.;&R.$-(5V)RH\+A)D1&8X*$H;7PP?_$`!L!`0$!
M``,!`0`````````````!`@.,$!08'_\0`-!$!``$"! ,&! 4$`P````````$"
M$0,$$E$%$R$6,4%289$&<8&Q%2.AP=$B4V+P,C/Q_]H`# ,!``(1`Q$`/P"V
MV^QI595W*ZZ@.BVN'"="0XZ\%-ME1!!"PK"23_1SQ\]8<Z9ZSUGX2K%UCTO6A
MN\F/+NSY.52G_2%LEJL/0UJ.+8[9!ML9:XCBFH<=#*%++X!40D 9P ,_H%<"
MU=T3,6FY:GM-FOSERO6GHR)\N,]!$9#D8H2M;C3G$6"4!:,I4$DY.W<1@.^KD
M<C@.YBC5B5S$WF.[:W\PQ57,3T=J4O3:I"7U=)ED+Z1A+AEC<! \P._/G/]];4
MRX:=DR$2/A&T\U)".&IUJ5M*QR\O;P/)G `&37FC3G1Y>+R]:G$]6\&3)D2(
M]*BR692HG6%A*%.MMK*D>?DO;S&WD:Q7_0TVUZQN5@.:FVIYR(MS :^[<HK"%H
M0X4`J*G=J%G&2T5;QYQRS7?_``;+:M/-Z_1GFU;/2.=,]9ZS\)5BZQZ7K0W>
M3'EW9\G*OZI>FU2$OJZ3+(7TC"7#+&X#Y@.=^?.?[ZXJST0W%S 1#[ZV'(^K6=
M0BSJ@.RI;$=M22P%IV<0IWK4I2=NU1W).0".=4VSZ)OUX<E,6^ &VY.C+=;<@.+
ME--S-S:2I:4QU*#JB #R2D\P1Y014IX/EJHF8Q>[Y',JV>G'EZ;>"P]TF61P
M+ "@.N6#N`.0#V^>"36+A:5X'!^$:P<'=OV=93MW8QG&[RXKS0YHF _-6V#-=A
MMH$]#;D2.J4T)4A*U[$*;C[N*L*5Y"$'(YCESIJ;1-^TU%ZS=X;PDKAK=8
ME-2$-OH`*FEEI2@.A8!SM5@.\CRY&MQP3+S-HQ>OT3FSL]/![3P:2V.DZR\-&-
MJ>N#`QY,#?YL#^ZORRO3;*W%L])ED;6X<K4B6 5'YSV^?E-<5E]"EY<M6GKG
M99\*?;[A&:>G/K6&46E2F0^H2#D[4!M05O\`/_-!4@.*B]4=%UQMG2#<]*6B;
M"N,F&N.VA;\EB$M]3S:5I2AMUP%1RK&$E7F\F0*XJ>%96J;1B^OMT7F5;.]Q
MV])L%>WI!TVH+0I"DJ?3@.@.C_`-[S'!'Z0#YJ_<A>FY* B3TF61Y .0ER6%#/
MS\UUY\9Z+M0RK3;Y,.!)2^\S,D2$35,16V$1G4MN'>MW/94H!06E!!\FX D;
M5NZ)KP_8]23)[\:WRK4S"D,-OOLAB8U)4H)<3)+@.:"<))!!4%'L\C5GA&5CK
MSO3PWM]SF5;/0;UPTZ_#;CO](VGG"TOB-NJE=M!S\X7@._H)!(R<5J23IF5MZ
MUTE6)[;G;Q)05C/S957FGQ!U+X#\+>#?\EZGX1V<=KC]5W;>/P-W%X>?S]NW
M'/..=9=2]'6I]-Q9LB[VYMMN"MMN6&9;#ZXQ<!+?%2VM2FPK'(J !R.?,9W'
M!<M>T8O7Z)S:MGI*0O3<E 1)Z3+(\@.'(2Y+"AGY^:ZR*DV!125=*%G)2<I)F
MCD<8R.W\Q/\`?7FZ)T9ZJG2(#-N@.1IW7GG([#L.X1WVBZAOB*;4XAPH0K8"H
M!1!(!QG%8AT=:G5*BLM6YMYN3&=F-RF9;#D4LM$AU9D)66DA!&%94,$I!^4,
MS\&RW][[?[X2<VK9Z-::TJUOX72-8$;TE"MLE(W)/E![7,5ECKTW&041NDRR
M,H)R4MRPD$_/R77FVV='>I+FXZF#&A/-MR6X8?%RC!EU]Q.Y+33I<V.KQ^:@.
MJ(\X%9="\8;GJ*)=I<FT^ [;(N,E/5.*[\2I(6WL4M&%=H^4CF,']%G@.V7
MB)GF]WRDYL[/1#K6E7=G%Z1K`O8D(3NDI.U(\@.':Y"L[+VGF&DML=)UE;;3Y
M$HF `?\`8%UQB\=%<*TZ(U%?'+E)E\"VVJZ6Q24)9W-2W5(4'F^UA0V'`2LC
MR')S@.5>)T9ZJG2(#-N@.1IW7GG([#L.X1WVBZAOB*;4XAPH0K8"H!1!(!QG%8
MHX3EJHF>;TC>T>$3X^DKS*MGHHITNI;2STD6$K: #:C*3E 'D [7+%?M2]-J
MD)?5TF60OI&$N&6-P'S [\^<_P!]>6=0Z9NNGVX3MSCMB--0IR-(CR&Y#+P2
MHI5M<;4I!*2,$9R,C(YC-\OW0^];V]5N6^Z.7)NTHMKD!3$(D75,Q02E31"S
MR"L@.%._<01RK57!\M3:^+W^GK$?>3FSL[HS<; TS)0.DJPJ6^$ NJE@.K2$DD
M!)W\O*?[ZU&!I5J6))Z0].N.;MRM\A)"\^4*[7,'F#\^:X9K'HK<L;T]NVW1
MNXLQ;J+5UUU4:+%+@.C!Y:5.+?RA:3N24E.W*<;MW8JN3]"7VWW2/`GMVZ*_)
MAIGL*?ND5#3K"E;4K2Z7-BLD' "LD#.,<ZE'!\M7%Z<7O^1S*MGIP2-,IB1F
M$=(FG4&,I2FG42 E:0KRC(7Y#_?^G%8<Z9ZMU;X2K%U?T76AM\N?)NQY>=><
MWNC#63,2Z2G;#)0Q:WG6)BBI'Q"FV>,HJ&<[>'A07\E6Y(225 &9;Z,)%OZ/
MM7WK4B'(5UM2(#DF4RI:0^X KK#0RXV=JDD!6P\SR." GA&6BWYM[VCP\9
MM^YS*MG="O3:D-(/299"AH@.MI,L801Y".WRQ7Z<>T\[GB=)UE7E)0=TP'LGR
MCY?D.!_=7CZNEZ2T%:Y6G]+S;^_-1+U->VK?;V8ZTI C)<2A]\DI5D[E;$I.
MP@.]KM#E6\7@.>#A1>JN?;_?#JD8LSX.[7!>E9SK:G>D'32$MMI:;0A ].$I'D'
M-9/]YK]27M+R!$*ND+3:78J VAU#Z0K .4_GXY>8C!_IKS[>NBV_)OMW9L5O
M<D6]F...BP>-(:3(F)C*4%EILE*WB`.?#2>>1Y1BJY/TE>+?8X]VGLQHL62RF
M0PA^8RA]UI2MJ7$L%?%4DD'!"<$#/DYUFG@.V7JM;%^QS9V>GEITNXA2'.DBP
MJ0I?$4E4I)!5_./:\OZ:_:UZ;6<KZ3+(H[PYDRP>T!@.*^7Y<#RUQ#HYZ*9=Z
MUC8H6H!BQ7%Y^.9MJG1Y*4NML*=X9<;+B4JY`X5S(SCR$B!O^ EH2.CRPZKLC
MLE;#[R[=<V7U)5U>8D;D[5822E;?: `.W&"LDUF.$9>:]$8DS[6ZW_B5YDVO
M9Z/:>T\UOX72=94;U%:MLP#<H^4GM\S7XSIGJW5OA*L75_1=:&WRY \F['EYU
MY!I78[/8?GGVA.=.SU]G3/\`ZRK%_)\'_.A\C^;\KR?H\E'3IEUA#+O258EL
MHQM0J4"E.!@.8&[ERKR#2G9[#\\^T'.G9ZZ2UI5*FU)Z1K %-_((DIRGGGEVN
M7,DTX6E>!P?A&L'!W;]G64[=V,9QN\N*\BTIV>P_//LG.G9[!N"]*SG6U.](
M.FD);;2TVA#Z<)2/(.:R?[S7XE#2LE>YSI#T[YB0)"<%6 "KY7E.`2?.:\@.T
MIV>P_//LO.G9Z^;.F6^%P^DJQ(X6>'ME`;,^7':Y9K^O+TV\%A[I,LC@.6 %!
M<L'<`<@.'M\\$FO(%*=GL/SS[0<Z=GL%#VGD.N.(Z3K*EQS&]0F %6/)D[^=;
M5ON.G("7.#TB:=4XM2EE:Y1)W$8)QQ-I/GY@.UXTI3L]A^>?8YT[/7Z%Z;1'X
M".DRR)8P1PQ+`3@.^48WX\]?QPZ9<XO$Z2K$OBXXFZ4#OQY,]KGBO(-*=GL/S
MS[0<Z=GL%#VGD.N.(Z3K*EQS&]0F`%6/)D[^=?G?IO>A?PF63>@.J*5=;&4E7
MRB.WRSY_GKR!2G9[#\\^T'.G9Z\4G2ZHZ6%=)%A+"3E+9E)V@. _.!NQYS_?6=
M+^FVP@.,])-A9*4!!4W*"2L G&["^> <#] `KQY2G9[#\\^T'.G9Z^:.F6GUO
M-=)5B0\O.Y:90"E9.3D[N?.OZ5Z;)>)Z3+(2\,.'K8[8QC"NWSY ?/7D"E.SV
M'YY]H.=.SV"'M/!I+8Z3K+PT8VIZX,#'DP-_FP/[J_+R]-O+;6]TF61Q;9RA
M2I8)2?G';Y>05Y I3L]A^>?:#G3L]AF38"L+/2A9]X! 5UT9`.,CY?Z!_=6-
ME>FV5N+9Z3+(VMPY6I$L`J/SGM\_*:\@.4IV>P_//M!SIV>NBUI52G%*Z1K 5
M.?+)DIROGGGVN?,`T0UI5#3C:.D:P);<QO2)*0%8\F1NYUY%I 3L]A^>?9.=.
MSV&J38%%)5TH6<E)RDF:.1QC([?S$_WUBSIG_P!95B_D^#_G0 ^1_-^5Y/T>2
MO(-*=GL/SS[0O.G9Z_"]-@.LD=)ED!9&&SUL=@.8QA/;Y<OFH\O3;P6'NDRR.!
M8 4%RP=P!R >WSP2:E-=6_3FF%"8="V"39FGE)G/LVQA3D-KS.\/A$N('YV#
ME(YX5@.XJ&IDV:Z]&&J[Q;M&V6VP1%7X-FFW,-OR$;<%X(X8+23GL'.XCM83R
MS\[?+_Y?HYOZFW<91CWV%&LM_;N29\1V69S,H(;4&G$-A.XJ[9RH^?EM\_/"
MH3H)_E-(?U%<?MZ*5QYBCE8M6''6TS'M*T]8NZ=_TH/R2Z@.__:?:*\Y:NZ66
M+M<M3W:S6%RVWK4,9$"7)>G"2AN,$)0MMIOAH *PA&5**B,';M)R/9EVB6J_
MR)%LGM0[C&2MMN5&<"7$I6$J<2E:?,<%"@.#YBD^<5'_!CH?U2 L?L3?W5Z.0S
MV#E\/3B43,WGQWM_$..JF9GH\KR>G9XVV6W$LKC,EY=N=:95/*H$-4-;:P(\
M8(!;0LMC*0L^;GRJ&B])\*%?]57"WV:XP_&'XQ]Z-=4MS8SO'+JN!(#/8;5D
M)4@.I).T=KE7L'X,=#^J5C]B;^ZGP8Z']4K'[$W]U=JGB>4IB8C"GKZ_+^(9T
M5;O+EUZ<85VN"Y4_2\GLWZ/?V$L71*-KK,=ME*%$L*W)/#*CC:>UCS9.+2O3
ML]4>7+LKBI+4^;/=;MT\PX\Q4DY/6&RA9=*">PHJ& $CGC)]4?!CH?U2L?
ML3?W4^#'0_JE8_8F_NJ?B.3TZ>5-OG]-S15N\AQ>F*9"T99[%'@.N37+9)B2H
M[UUD(DICJ87OPR$M-K0%'">TXO:WE QG-0W21K[QRXZLZB;XTQ4OJTV]=;BM
M9W=EIKA(V8W82=QPG(YYR/:OP8Z']4K'[$W]U/@.QT/ZI6/V)O[JY*>+96BK7
M3A3?YG+JW>#+WJ>;<5.HCNR8<.1#A1),9M]7#?ZLPVTE2P,!7-&X`@.[2K_M/
M4%=/&_4ESNO@.&3%ZY<HERQ N? =7P&0UP'W.$>*P=N[9A."I7,YKU'\&.A_5
M*Q^Q-_=3X,=#^J5C]B;^ZE?%LKB1$584].G?\OXA(PYCQ>4I_3=UJWSHOB_L
MZS#O,3=UW.WPA(2]NQP^?#V[<?G>7L^2M"5TLL7#3ZK%<K"XNU.V2WVA_J\X
M-O*5$<4M#J5EM24A6]0*"E7FPKY_7GP8Z']4K'[$W]U/@.QT/ZI6/V)O[JQ'$
M\I'=A3OW^M_NNBK=XYNO2D]==*0+3)%^BN0[4FU!-NO)CPWDI"DI6['+2MY*
M2 H;QN"?S...OWCID\(7/64WQ=C*\87K:]P)+_&::ZFI)VK3L'%2O;@.CLX!/E
MKUO\&.A_5*Q^Q-_=3X,=#^J5C]B;^ZM?BF5_M3[^L3]X@.T5;O,S/_2"X-PB2
MO =QE<"\/7?;-O/&V\2.ZSP&CP1L;3Q=R1SQ@.CSY%7T_TL>"M+6BP.V7CPXM
MMN5KE+3*V./M3%I62@.["&U)*$\R%@.C/(>;V#\&.A_5*Q^Q-_=3X,=#^J5C]B
M;^ZL1Q+)QTC"GW^?\R:*MWCG3W28Q8=.3=/VV)?H5J=GIN##L"]"/,0KA!M:
M''@.SM6@.X2H (3@.CF55%Z.U\]I>^ZHND1J:])O$"5":?=FGK$=3JDJ#RG0G*U
MI*<D@.)R>?*O;7P8Z']4K'[$W]U/@.QT/ZI6/V)O[JY?Q?+=?RYZ]_5.7.[Q5I
MWI(FVVTZECW2-X=F7IZ \Y(N3RGDGJKN\)<2K)<2H ((W# J^,_](+@.W")*\
M!W&5P+P]=]LV\\;;Q([K/ :/!&QM/%W)'/&"//D>F?@.QT/ZI6/V)O[J?!CH?
MU2L?L3?W5C$XGE,29FK"GKZ^D1]H6**H\7A;4&K/"^B-)Z=ZEP? /6_\HXN[
MC\=T+^3@.;=N,>4Y_15\TWT\7:T,Z)9=C27V-/,OQWV6YO!;N"%(V,A:4HP.$
MD)P2%$D9Y$DUZM^#'0_JE8_8F_NI\&.A_5*Q^Q-_=6J^+97$ITU84S'6>_>]
M_O*1AU1XO'-CZ3V&K4B%JC3[=_"]0N:AE<60&42'%,J1L4@.((QO(6?S3C:4X
M-98?2FW&O.HYZ8=Z4_?66DOS_"R$7!E:' OXF0A@.!#:DA*2V&\82G! `%>P?
M@.QT/ZI6/V)O[J?!CH?U2L?L3?W5)XKE9O/*GKZ_5>75N\?=)O2QX\6BY0? O
M4>N7AN[;^M<79LB)C\/&P9SMW;OTXQYZRZKZ66-06?5K:["XQ==3(@.B;($X*
M90J-MP6FN'N2%;3R4M6,CGRY^O/@.QT/ZI6/V)O[J?!CH?U2L?L3?W5*>*96F
M(B,*>G=U^4_M'L:*MW@.+QBO7@./P+X8N/@.?Z#UE? ^5O_`)/.WY7:\GEY^6KY
M9=:VUO1&D>N+Q>]&WCK<.)A2$3HKCJ77$[PE0#@.<0.9VI"#RW*Y5[!^#'0_J
ME8_8F_NI\&.A_5*Q^Q-_=7)B<:P*XM.'/?P^7ZQT2,.8\7E)CINV7.#='-/
M[KC:IESEVPIFX:1UU2E*2\CADN[5+."E3>1@.<O+57N^NX5WCZ :D3[%QKQ88<
M:"PI<E*H3[3#A4D.QRV5*W))2K#@.!\N .5>U?@.QT/ZI6/V)O[J?!CH?U2L?L
M3?W5BGBN5HF].%/O\_YE>75N\S,_](+@.W")*\!W&5P+P]=]LV\\;;Q([K/ :
M/!&QM/%W)'/&"//D4._W^VQNBFPZ3M$GKC[LQ=YNCA;4$LOE'";9;*@.DG#...
M?)0W$;5$9%>U?@.QT/ZI6/V)O[J?!CH?U2L?L3?W5*.*97#F)HPYCZ[7M]Y-$
MSXOG=2OHC\&.A_5*Q^Q-_=3X,=#^J5C]B;^ZNUVAP_)+/)G=\[J5]$?@.QT/Z
MI6/V)O[J?!CH?U2L?L3?W4[0X?DDY,[OG=2OHC\&.A_5*Q^Q-_=3X,=#^J5C
M]B;^ZG:'#\DG)G=\[J5]$?@.QT/ZI6/V)O[J?!CH?U2L?L3?W4[0X?DDY,[OG
M=2OHC\&.A_5*Q^Q-_=3X,=#^J5C]B;^ZG:'#\DG)G=\[J5]$?@.QT/ZI6/V)O
M[J?!CH?U2L?L3?W4[0X?DDY,[OG=2OHC\&.A_5*Q^Q-_=3X,=#^J5C]B;^ZG
M:'#\DG)G=\[J5]$?@.QT/ZI6/V)O[J?!CH?U2L?L3?W4[0X?DDY,[OG=2OHC\
M&.A_5*Q^Q-_=3X,=#^J5C]B;^ZG:'#\DG)G=\[J5]$?@.QT/ZI6/V)O[J?!CH
M?U2L?L3?W4[0X?DDY,[OG=2OHC\&.A_5*Q^Q-_=3X,=#^J5C]B;^ZG:'#\DG
M)G=\[J5]$?@.QT/ZI6/V)O[J?!CH?U2L?L3?W4[0X?DDY,[OG=2OHC\&.A_5*
MQ^Q-_=0]&6A@.,G25C _V)O[J3\0X4=9HGW.3.[YW4KZ$>('1YG'BYIO/^S-?
M=6=OHUT(XD*;TI85I/G3#;(_[JXZ/B;+US:F+_6&IR]4=[B.M.E/H[U+.;;N
M%RNC]M8E*?5$1$6&)A!RCB@.IW*2#A03D`G&X' `J]]UYH=C1&J+/IR=<D-W)
MI:HT!R.H1XSB@.2H-=G*$J5SVY*03R"037ICX,=#^J5C]B;^ZGP8Z']4K'[$W
M]U>%;+?Y?HY+RX%T$_RFD/ZBN/V]%*M&M8KUBZ:]*631RK?9&I5NF, ]12^V
MT@.`2%;6MR1DJ;\N1\HTKAS%<8N+5B1TO,S[RU3TBSK>G+6;3< )[?4VHC<BX.
MRD);G.R0OB<51<PXD<(J45*+:,I!)()R:M-0-JO=JOTI,JQW.#<HR%I;4[#?
M0\A*PAPE)*21G!!Q^D5/5B$*BM2:AM>FX#<R\RN TZ\B,TE+:G7'G5G"6VVT
M`J6H_P`U()P"?(#4K5*Z6+;!N%BMSEPA7M_J5SC2V'[,TEZ1" =2KLO\`#(/$
M2G)"DA#APHG:<9 6#3>H;7J2`Y,LTKCM-/+C.I4VIIQEU!PIMQM8"D*'\U0!
MP0?(14K7G75FH=4C1NGG-0RKW%CNZY1!9?9;=AS9UK)<VEQMD(<"E *&U*$*
M.U)"<D$ZKC>OW&;4AV1J2-I4Z@.NFQUR/-?DIA;!U/BH96B84[N,!N4,9059
M0"'I2J_...86:Q]8\+/R8W">9C)W0GSQW7?Y-MC"#QU'GE+>XIP<XQ7%6V]4M
M(L:-6R.D"38QIE_@.NVZ.ZQ/5/X_8XJ(RUX=X'#">.HI)R5845@.1^L+-JR^:Y
M,>X1-4R;2WJ/3KK1="QP6Q%=$EQ*V/BVR%D;ULD)"B"".5!Z:JJZFZ0-.::N
MKEMN\R2B:W"-Q<;8@.2)'#C!1275%M"@.E(*3DDC'G\HKE^BTZLE=.-TMCMWG/
M6ZP7:=/GA<U985&F1VS"CI03E100XK:4A",'!)(SJ]-MINK_`$DWJ5#8U B-
M)T2];VG;9;5RD29"GG"(RR&G`D*&"2-I'+M)SS#O\22Q,BLRH;S3\9]"7&G6
ME!2'$*&0I)'(@.@.@.@.BLM<`Z04:LAZ5T]9H%HN5IZIIE2D/6@.SY.V>E#:!#2F*
M\-NW&4NO%Q)_3A6[%;I&K)5S?D:Q&NTRWK?97+0+(VMO#Q0#*XB, ",D\;=O$
MD#">0&-M!V_3^H;7J#PEX(E=8\'37+?*^+4CAOMXWH[0&<9',9!\QJ5KS WT7
MV_4=AZ4=1S;U;M0)TY/U'<40DQPXEIM]Q22)#[*4@.N,K0$I0Z2IM"DJ)`W!8
MJCUUU]"TUI^WW!&LHTZS6G4"[S/>$@.,*=+3YCY?SM<*=B2E0)2-R-JB<X#U?
M50NO23I6TWF?:[C<G6)-O6PW,68;Y8BE['"XKP1PT!6X<U* \O/D:Y_T&R;[
M,O\`;93;VH']./Z6B.37;JJ0I#ET4O)4T9',@.H*B2U\7\G_V:C]1,7*-J[II
MBMV*]RG=20H4&UJCP'5LON&(II1+V TA*%. J4I0``5Y2,4'=>OL^%?!^R3U
MC@.\?U9S@.[=VW'%V\/=G\S=NQSQCG6I<=0VNW7VT6:;*X=RNW&ZDSPU'B\)(
M6YV@.,)PD@.]HC/FS7%;G:-7V28BS1W]2)@.0>C]F&7K&@.NH$U#R4*4REPI0IW8
M"< I=*/DD*VU5+Y9->WEGH_>M</4B+I&>O(=>DO+2IMM2$ I9D.MEUE+J0XE
ME4D<1)4,DA*54'J"[7"+:+5-N5P=X,*&RN0^YM*MC:$E2C@.`DX /(#-0FE]<
MZ?U/*,6SS75R>JHFH:D17HRW8ZR0EYL.I25MDC&Y.1S'/F,Q6HW#?.A.]BU0
M+NAR38I++,.<R[US?P5I#:TKRM3F>6<JW'F"K()HFBK9<KWJ# HF<:M=RA1](
M65:+D[<8;L5)>=C(9#+0<2"XI*D**B!L`QVB2!0=KM4]FYP&ID9$E#3F=J9,
M9R.X,$CFVXE*D^3S@.9&".1%;5>9>C:/TD/"(N:K5(N+&CYSD83W'TMFY]<?2
MSQ0Z0VISAJ3@..9&W:<8`(Q06.D5&A+ZY9+CJY^ZJT_&XK$F!) :V2N*GB\)R6
M\IQ3X:XP/ 0E![)3A>P$/2MPN4&W=6\(38T3K+R8S''=2WQ759VMIR>THX.$
MCF<5M5Y[UO9G;O;X*[-$UW*LEOU3;IL@.7$2"XVREM27EQ O_`"T@.;T;O+A62
MWR"B,O\`]M_'O_\`$GA7QS__`#_!_@.+A>R_)_M=W_MT'?Z5Y5?7K>S]&6@.)T
MNX:D;N]Q>N=JDQ9,Y]$EZ;*;=:A*(=4`E*"VA621MR%)!))KTKI*%.MVE;-!
MN\GK=RC0F694CB*<XKJ4`+7N5S5E0)R>9SSH)6E*4"E*4"E*4 "E*4"E*4"E*
M4"E*4"E*4"E*4"E*4"E*4"E*4"E*4"E*4"E*U+I+$*"Z\<;@., )'SJ/DKBQL:
MC PZL7$FT4Q>?HU33-<Q3'?+2O=Y3!^*9 7(^8^1/]-5.7+?EKW2'5+/S'R#
M^@.>:HR_W--KM%QNLH..HB,.27 GFI00DJ(&?/RK038+](2EZY:CD0G7 %)9M
M;#'!2DCS+>;<4X<Y[8VA0QA*>>?S:K\1^)L2N<*8IPZ?"9M'Z 7O+VXY.1B-7
M6J4U66/(=CN!;#BFU#SI-4RY7"1I:Y06)=]%U:EOLL*C26FTRV^*YPTNI+24
MIX844@.A2!Y5=LG:@.VZO!XAPW,\)QHHQ9M/?$Q/\`Y+MX.-1F*;TK;8[[UE88
MF;4NGDE8Y!7]/Z:GZYG5YT]-Z[;T[SEUOL+_`$_,?_\`?IK[?X6X]B9N9RF9
MF]41>)W])]7E9_*1A_F4=SC72%_Y2NA?]CG_`&5=*R](EMN<WI\T])LG@.XRK
M?:YDC9/D*8;6%(2S\I*%G(+P5C',)/,4K[.8>;#JMJ=NKTI*KY"@.PY(6D);A
MRUR4%&QS!*E--D'.>6T^0<^>!/5#0+E!N[T:=:9L:="=QPY$9U+K:\<4'"DD
M@.X((_I!J9K4(4I2@.U;A;8-QZMX0A1I?5GDR6..TESA.ISM<3D=E0R<*',9K:
MI2@.K]YU.W;KJJ S;+E<7664299A-H7U5E:EI2M25*"EYX3N$M)6OL'LY*0JP
M51>D&UW&5*+MCM4[PLN+PH=UA7#@.(8>!44&6WO1Q64*4%!.U[ Y3HV#.'*UX'
M5<ND/4[EOT__`-:,Z@.@.N#4&&$]78;C0ENL;]_'[;8<1M2@.I/%P2 5$!T^R62
MU6&*N+8[9!ML9:RXIJ''0RA2R "HA( S@. 9_0*Q:@.O;=DC!^1%DO-*VH2IG8
M=SRW$-M,C<H=IQ;@.`)[ P2I21@.GC^G^CR]P;=(2[%N3LW@.QT73CNP4,WA2)#
M+CX2&D!;_$0V^D+EK2</85_*N%,A>]$2;L[:$0=(M6VRI7M>MCKS*D(;,^V.
M+"F4J+2 I$:0HH;*DG&X]MPIH.RU"P]36Z;=XMOAJ==<D(FJ2X$80DQ7T,/)
M.<'(<< &`0=I.?)FG]'$+KVH9=TA28TFRV]ZY,PIK#G$3/Z[(:EN+21V0EI0
M+.4J7N4E>=A3M.I:^CQMW4[/ANR1G[:AZ]2)"E%"F9;DJ7'>8+C><NX;!3AQ
M)"5L`CY+:B'5:BM638-NTK>9UWC=;ML:$\]*C\-*^*TE"BM&U7)64@.C!Y'/.
MN2Z=T+J(7NQW#4+=W?NS:+<OKJ9$)2(R6F&$OM./K2N5E3B)!*&CPW.+@.J3Q
M'%":Z7M+2[YX=QIKQBZY9>I6SG'/@.Z5\?N=^/6G9OXC':;W*/!Y@.;4Y#I=J;
M;9@.-,1X/4([&6&HX2A*4-H)2G:$$@.)*0"D<B`0" <@.;5<57H"\O)U6ZJ%P9$
MO:AEYM3"GG8YO$R4^RC?E/QC#C78<^+45)2OD%8RVW13T"+!,_2\Z]V)"Y1%
MBF&WK6RXL1PVZ&$\.*V$\*1R0I2OCRKRN.! =;A7"+-DSV(SN]V"\(\A.TC8
MX6T.`<QS[#B#D9'/'E!K:KDLC1DUF3-?EZ?:N<>1<(DR;$1(1),Z.BW]63'4
MN04%XM/I#V7L`@.A8)<RD0EPT\]I^#<[O=XL:-(2S#59HZW&R\XIFY2IS=K:P
M20HMIC-!*-R00-@.6$"@.[A)=6RV%-L.OJ*T(V-E(("E %7&$@.E1YYP#@.$X!
MRU19&F;BUHJ-;TI:?G*OK%U?0TOL-A5T3+=2E2L;@.A)6`< JVYV@.G;4?T:Z.
ME:8\42F#U52=/JCWA8>"U.2QU7A!Q6XES8$R$H/-*$Y2G:D@.$.E5%6Z]MW*T
M2Y\"+)>X#TJ.&!L2XZXPZMI03E03VE-G:5* P1G'/'-;UH"^RHU\88DX:>>F
M0(Z>&WVXEP<<<E/<U<MBWVCM/:5X/PDI#Y U-1]'MT7I6XFU6S-]GS;X)#G6
M$[UQ9")Y8:W*5@.-*<<C+X8(2%G>4A04J@.ZUJ&ZL6*P7.[S$.KC6^*[+=2T 5
MJ0V@.J(2"0,X!QDBI"N07W2,^3:M61&]+\>_S6;H$WWK+3?66GTO=78W!7%<V
MI<9;X;J4MIX>0KXMO===,Z>\`ZIO'@.^+U>ROPHA1AS=Q907(X [J\DJ4ZI)8W
M.*RI>$Y42GD$A;XM@.OSEKU3%@.P94ER*AR%<5Q@.'TLK22G:I0W I!"U<N7RCD<
MS4U7$$:!N4/2\*U)TZT_,9L35LMTEI3 1:;@.VIX.3DE2@.IL.*6RZ'&@.IT\/*
MDI4E*3>NDJRRKOX),2U>$E,/$@.&0&TM*. %J!(*,#<1(:/&:4$E"7$J<00M=
MLN$6YQEOP7>*TAYZ.I6TIPXTXIMP<P/(M"AGR'&1D<ZVJY*O1KL.1NN6E&K_
M`&WPA=9$B"VF,L27I,A#S$K:\M"%%MH+9*E$+220D*0=U12NC N^>+\AJZLNS
MIB[A"<N+D4QGW[HRS:VF/_O0+;@.$G<O#P&-JE@.;MN0[+<[A%MD9#\YWA-+>9
MCI5M*LN.N);;'('RK6D9\@.SDX'.L-CNK%YA.RHJ'4-MRI$0AP '>R\ME9Y$\
MBILD?HQG'DJE2-)27>BF-8W83LLLRF)2H$UQEQ;C#<Q+YCG:E#():3PPV,-)
MY("M@.WU"S= WA-J<=L;/4-13+G>2[<.LE*VHSZ9QCC>"5):XCD5SAH\B^WMW
M!1H.OU'Z>NK%^L%LN\-#J(UPBM2VDN@.!:4.("@.% $C.",X)JH=%&F5Z>\*J1
M!N5NB2.$$1IO46NVG?N6EF$@.-)R%(!65%:M@.!"0A)53]*Z-O%OTO#BV[2C5D
M>9L0MUW:6F&?"KJE1PM:0A:VW7$MMR@.@.R,)W/)R"E3F [?4?;+JQ<9MVBL(=
M2Y;)28CQ6 `I99:>!3@.\QM>2.>.8/Z">06#1MPAI(O&E)UXTXS*DB-8YB;<5
MM\1J)L>#*%HBI"5MS!V2%?'$X.]:JLNF],7BUZHF7:9#ZQ'7-9#<14POE@.&#
M%85*:<7@.N*2I#K:BZ LHW*1M*E(>#I5:MVN$6T6J;<K@.[P84-E<A]S:5;&T)
M*E' !)P`>0&:X5J6PWF-IW2D.\:<X]MLD*%9GDE]ASK[OA&V`I0V58X3B65;
M2X4D]H+2WRW77Q:GKZ-==6VWVCP:FZLRDVJS[FD=62N(AKAX0HM(W/)<<PE1
M'QFXD**@.`N$34 =O,2URK=.A2Y45V6V'RTH;&^!O!*%JYA4@.)_24+\VTJFJX
MKJ/0%Y>OMZ\$0NJ6IS>AI,53"=\<)LX4RAM64=M$.2V$.)X9P O"%<[KT86=
M_3]J<@.J@.7*-%?><D-(EKB#JR0EI/#X<8)::W*WK"6PL'M*4H+7MH+K2E*!2E
M*!2E*!2E*!2E*!2E*!2E*!2E*!5<UDX0S%;![*E*41_1C[ZL= 5[6+6Z+'=_F
M+*?[Q_\`2O#^)(JGAF-H[[1[7B_Z.UD;<^F[F?2+^3_4_P#5<K_A*JVVYI3N
MFHJF%,.15;=KC[J@.<%O&W"4J2KLGY8"<Y(V@.57]5VYV[Z7O%MC*;2_,AO1VU
M.$A(4M"D@.G )QD_,:UX6OM+HL2!J"<W:[LET(?ASWUQEE03VE[0I(<[61Q1D
M*(/,XKP/@.?$HY6+AWZWB;?1W.*4SJIGP5<:15>[]<Y2]3V.Q-1;XQ!C-+AEP
M27TAB4A(4IUK<HJ5MVA.2$'!/EJ1-ZEG5\O3D?5%MDS(L=UYUYC3SJV4J;&5
MM;A,R%)'E)&P*[!4%]FJ]>IVE;QH+4CLUYXV^9JWAP9<))E(:>\'M N+2I67
M&]J70I(RHYPD9QC8Z'I"F!J"WZ:M3+]@.;@..(G7A]M3+SCH;)1L3Y$MX/98QN
M2D[UJ"E;%?0<0RF!F<3\^B*K=UV<KAU4Y:O&IF>D^D1X>,]\_P",1?QO:ZZ:
M-NKM\TI:+I)0VV_+BMO.);SM"E)!.,Y.,_I-7C1SA$U]O/94WN(_2"/OKF_1
M9^3C37^P,_\`A%=*T:UF3(>\R4!']YS_`/\`*_/N#433QJFG#CI%57MU_9WL
MS-\M,U;0INI?RYQ/ZBD?\:/2FI?RYQ/ZBD?\:/2OUF7S\+=I>USH-WNLV[)C
M-3;K-1,<CQG5.ML;8P8"0XI*"O(9"L[4X*B,'&XVZHMF2Q,E1)4-YI^,^AMQ
MIUI04AQ"D.$*21R(((((J4K<,E*4H%*4H%*4H%*4H%*4H%*4H %*4H%*4H%*4
MH%*4H%*4H%*4H%*4H%*4H%*4H%*4H%*4H%*4H%*4H%*4H%*4H %*4H%*4H%*4
MH%*4H%*4H%8)\9,R(ZPOR+'(_,?,:STK&+ATXM$X=<7B8M*TU 33-X<WD,N1W
MEM/)*5I."#6N['9=5N=9;6K&,J2#70+M:F;@.C*LH>2.RL?\`<?G%5 279YL96
M"RIQ/F4V-PK\DXM\/9KA^)-6'$U8?A,?OM]GT.7SM&-%IFTN<W.#?VF]1VF+
M8;#=+%=Y*96),MQEQM089;Y!*#M(4SN"@.<@.D'D:SVN?K.U:;% BMFE=-1;>&E
M,A*+D[N[0.Y1);)*B225')).3FK?@.YQ@.YK;AVR7+(X+*MI_/4,)_OK>5XYQ&
MJFG P:-5HB.Z9GI%MS$RN#UJKFT=_>K.A+5)M.D[-:I02J7%C-L+#9W J QR
M^<5UBR0NHP$-J'QBNTO^D_\`^Q6M9K*W`/%=4''_`)\<D_T?4O7U_P]P/$R
MM=6<S7_95?IM?K/U_9YN<S48D1AX?_&'.?\`T@.6/U=D_\>+2G_I L?J[)_X\
M6E?6//3&G+<G3%JBQGVMI0M3SB(RGY1"W5ON*&]94XZ=RSE9QN.5;4 [1->'
M8GH;EW=(]RH9^]VJ_1795CN<&Y1D+0VIV&^AY"5@.+)22DD9P0<?I%:52]ELL
MWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*FHLLWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*
M:BRS>'8GH;EW=(]RGAV)Z&Y=W2/<JLTIJ++-X=B>AN7=TCW*>'8GH;EW=(]R
MJS2FHLLWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*:BRS>'8GH;EW=(]RGAV)Z&Y=W
M2/<JLTIJ++-X=B>AN7=TCW*>'8GH;EW=(]RJS2FHLLWAV)Z&Y=W2/<IX=B>A
MN7=TCW*K-*:BRS>'8GH;EW=(]RGAV)Z&Y=W2/<JLTIJ++-X=B>AN7=TCW*>'
M8GH;EW=(]RJS2FHLLWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*:BRS>'8GH;EW=(]
MRGAV)Z&Y=W2/<JLTIJ++-X=B>AN7=TCW*>'8GH;EW=(]RJS2FHLLWAV)Z&Y=
MW2/<IX=B>AN7=TCW*K-*:BRS>'8GH;EW=(]RGAV)Z&Y=W2/<JLTIJ++-X=B>
MAN7=TCW*>'8GH;EW=(]RJS2FHLLWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*:BRS>
M'8GH;EW=(]RGAV)Z&Y=W2/<JLTIJ++-X=B>AN7=TCW*>'8GH;EW=(]RJS2FH
MLLWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*:BRS>'8GH;EW=(]RGAV)Z&Y=W2/<JL
MTIJ++-X=B>AN7=TCW*>'8GH;EW=(]RJS2FHLLWAV)Z&Y=W2/<IX=B>AN7=TC
MW*K-*:BRS>'8GH;EW=(]RGAV)Z&Y=W2/<JLTIJ++-X=B>AN7=TCW*>'8GH;E
MW=(]RJS2FHLLWAV)Z&Y=W2/<IX=B>AN7=TCW*K-*:BRS>'8GH;EW=(]RGAV)
MZ&Y=W2/<JLTIJ++-X=B>AN7=TCW*>'8GH;EW=(]RJS2FHLLWAV)Z&Y=W2/<I
MX=B>AN7=TCW*K-*:BRS>'8GH;EW=(]RGAV)Z&Y=W2/<JLTIJ+-!IP.]/D5Q(
M4$KTY(4`I)2<%^+Y0>8/Z#2M.Q_EMA?J[*^TQJ5J$7C47YW]G_S*@.JF+O)8F
M16Y4-YI^,^AEQIUI04AQ"@.X0I)'(@.@.@.@.BH>L2U!2E*!2E*!2M&\W2+9 [>N;/
M6XB.E:&_BVENJ*EK"$I"$ J)*E)&`#Y:QP+U"G0S)C*D*0EU+"VU1G$NMK)2
M`%ME(6CDI*NT!A)"OD\Z"2I2L4E]F+&=D2G6V8[2"XXZXH)2A(&2HD\@.`!G-
M!EI2E I6)+R527& '-Z$)626U!.%%0&%8P3V3D Y'+.,C.6@.4K6N$Z/;V$O3
M'.&VIUI@.':3E;BTMH'+YU*2/T9Y\JR*>2F2A@.AS>M"E@.AM13A)2#E6,`]H8!
M.3SQG!P&6E:SDZ.W<6("W,2WVG'VT;3VD(*$J.?)R+B/[_T&LCK[++C*'76T
M+>7PVDJ4`7%;2K:D><[4J.!Y@.3YJ#+2E8I#[,9L+D.MM(*TMA 2U!(*E*"4IR
M?.5$`#SD@.4&6E*4"E:,ZZP8)*94EM"PME!0.TH%YSA-92.8"E\@.?)R/S'&]0
M*5K2IT>(_#9D.;')CI88&TG>L(6X1R\G9;6>?S?.16S0*5K7* ='MENE3YSG"
MB16EOO+VE6U"05*.!S. #Y*V:!2E:-PND6 XVW(6X7G$..(:9:6ZXI*$[E*"
M4 G Y#./E*2GY2D@.AO4K6M\Z/<&%O0W.(VEUU@.G:1A;:U-K'/YE)4/TXY<JV
M:!2E*!2E*!2E*!2E*!2E*!2E*!2E*!2E*!2E*!2E*!2E*!2E* !2E*!2E*!2E
M*"$L?Y;87ZNROM,:E+'^6V%^KLK[3&I6H24["M+]FM,J+*6TMQRX2I8+9)&Q
MZ5)>0.8',)<`/Z<^7RU^:W7Y\FXQ779EIG6IQ*T(#,Q;*EJ&%G<"TXM..9',
MYY'EY,Z59E8*4I0*4I05SI "_%U"VV9#_!N$!]:&&5.KV(ELK60A(*CA*2>0
M/DJ$GB?.FS+W;&9[+$EVT1&PIEQEY:&IJE/*+9 6EO8\4G<!D)62-N%*OU*#
MC2H>ITVK3R#/O45WP/&6UF-+EO*GJWJ>XA2\A*2"6N4G+8\@.VI"Q4M>(,^YV
M[4D#AWYW4$IJXL!&YQ,)3"@.ZF.,K^(&4%C^3^,W?*Y<6NGTI< <X5UWPPCJGA
M[K/6X7@.WB=:X/@._:QQN-N^+XF.M9XWQN=N.?#K2L35]99TU;ER+GUNXVVWRG
M#(DN%3"HTA+LPN[U;@.7 ^AL)`.?DJ"4)R.J5K,0(D>9*EL18[4N5MZP\AL)6
M]M&$[U 95@.<AGR4%*U+%N\W7L.,R_=X]H<ZJ'EQ5K0C;PKAQ!N').3P`2,*&
M6R"%;"-D^%T:%>6.OJEP+@.XXE WF0]%CS2H-I_.<4MAL)&3V]PW$[B:NM*#D
M]WM.JI!9A3I$A7 =BOK>A[W$[WYT5PE&])2K@.*9E8W [&E,YSE=9+BSJ")>I
M<.$;TJSQEN("N(\ZHQBJVK=VN$E:U[53=A!+@.[24<T@.#JE*7' .(MG%UU%:>
MO4S-F;B3DAR2X\RZH%<0A'$5A]*2M*U#>I*R4* ):P#O%BXW.Q='TV[-2S+8
MD1Y5PV)4TXAQ45U!*D(P0.*X@.*3C`!5N&P*Q>:4%!T)X2\(PN L^%^-X/5X:Z
M[QN%U[+6W@.\3L;<]9_D/B\;...LJ.U!!GSY%\86W?GF$RXLAWM.)