|
|
| Nikolami 2005-07-04, 8:23 pm |
| I used DBCC SHRINKFILE (database_log) but their was no change in size of log
file.
(SQL Server 2000 and database log file is 50Gb)
Please help, thanks in advance.
Nix
| |
|
| did you hear "Nikolami" <nikolami@nyc.com> say in
news:dac4ij$23h$1@ss
405.t-com.hr:
> I used DBCC SHRINKFILE (database_log) but their was no change in size
> of log file.
> (SQL Server 2000 and database log file is 50Gb)
>
> Please help, thanks in advance.
> Nix
>
>
>
did you truncate the log prior to shrinking the database? If not you will
not be changing the "active" portion of the log. Either truncate the log
or, if you're desperate, set the recovery model to simple, and try it
again.
HTH
| |
| Nikolami 2005-07-04, 8:23 pm |
| What you meen "truncate the log prior to shrinking the database" how to do
that.
Thx,
Nix
"Neil" < neilmcse@nospamforyo
u.com> wrote in message
news:Xns9689A93A6417
0neilmcsehotmailcom@
207.46.248.16...
> did you hear "Nikolami" <nikolami@nyc.com> say in
> news:dac4ij$23h$1@ss
405.t-com.hr:
>
>
> did you truncate the log prior to shrinking the database? If not you will
> not be changing the "active" portion of the log. Either truncate the log
> or, if you're desperate, set the recovery model to simple, and try it
> again.
>
> HTH
| |
|
| What he meant is
BACKUP LOG YourDatabaseName
WITH TRUNCATE_ONLY
Search for BACKUP LOG in BOL for more details.
"Nikolami" wrote:
> What you meen "truncate the log prior to shrinking the database" how to do
> that.
> Thx,
> Nix
>
> "Neil" < neilmcse@nospamforyo
u.com> wrote in message
> news:Xns9689A93A6417
0neilmcsehotmailcom@
207.46.248.16...
>
>
>
| |
|
| did you hear "=?Utf-8?B?UnVza2k=?=" <Ruski@discussions.microsoft.com> say
in news:BD9C9A56-BA14-42A4-A9A3- 7715840BED4A@microso
ft.com:
>
> What he meant is
>
> BACKUP LOG YourDatabaseName
> WITH TRUNCATE_ONLY
Bingo. As I mentioned either this or set the recovery mode to simple
temporarily. But since you have 50Gb of t-logs a backup is wiser. You
should also schedule these (tlog backups) to occur with a bit more
frequency so the logs don't exceed drive space. If you have any other
questions, go ahead and hit me off line.
| |
| Hari Prasad 2005-07-05, 3:23 am |
| Hi,
Read the below links to understand Transaction log architecture and
shrinking.
http://msdn.microsoft.com/library/d...ar_da2_1uzr.asp
http://support.microsoft.com/kb/272318/
Thanks
Hari
SQL Server MVP
"Nikolami" <nikolami@nyc.com> wrote in message
news:dac4ij$23h$1@ss
405.t-com.hr...
>I used DBCC SHRINKFILE (database_log) but their was no change in size of
>log file.
> (SQL Server 2000 and database log file is 50Gb)
>
> Please help, thanks in advance.
> Nix
>
| |
| Steen Persson \(DK\) 2005-07-05, 7:23 am |
| ...and if I'm not mistaken, you need to do a FULL backup after you've changed
to recovery model in order to truncate the log.
Regards
Steen
Neil wrote:
> did you hear "=?Utf-8?B?UnVza2k=?=" <Ruski@discussions.microsoft.com>
> say in news:BD9C9A56-BA14-42A4-A9A3- 7715840BED4A@microso
ft.com:
>
>
> Bingo. As I mentioned either this or set the recovery mode to simple
> temporarily. But since you have 50Gb of t-logs a backup is wiser. You
> should also schedule these (tlog backups) to occur with a bit more
> frequency so the logs don't exceed drive space. If you have any other
> questions, go ahead and hit me off line.
| |
| Nikolami 2005-07-05, 9:23 am |
| The point is!
I use Veritas Backup Agent for SQL.
After backup procedures, you must (veritas wrote) shrink log file if you
want more space for bigger file.
After log backup i must shrink log file.
After shrink log file their was no change in size of log file.
What mistake i do???
Pls help!!!
Thx to all.
"Steen Persson (DK)" <spe@REMOVEdatea.dk> wrote in message
news:Ohjkv$TgFHA.1948@TK2MSFTNGP12.phx.gbl...
> ..and if I'm not mistaken, you need to do a FULL backup after you've
> changed to recovery model in order to truncate the log.
>
> Regards
> Steen
>
>
> Neil wrote:
>
>
| |
| Neil MacMurchy 2005-07-05, 9:23 am |
| did you hear "Steen Persson \(DK\)" <spe@REMOVEdatea.dk> say in
news:Ohjkv$TgFHA.1948@TK2MSFTNGP12.phx.gbl:
> ..and if I'm not mistaken, you need to do a FULL backup after you've
> changed to recovery model in order to truncate the log.
no, but you really SHOULD. setting the recovery method to simple is
actually setting the "truncate log on checkpoint" option. All you really
need is a commit and a checkpoint and the log is truncated. If you were
to set the recovery to simple and then run the Shrink thru SEM, it will
shrink and truncate the log. It's also a little like tight-rope walking
without a net - fairly simple, if you don't fall. If you switch recovery
methods you SHOULD do a backup for safety sake - the truncation of the
log is just a side benefit (the backup will commit and checkpoint the log
as part of the operation, so the truncation happens there as well).
--
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs
| |
| Neil MacMurchy 2005-07-05, 9:23 am |
| did you hear "Nikolami" <nikolami@nyc.com> say in news:dae0n6$bmu$1
@ss405.t-com.hr:
> The point is!
> I use Veritas Backup Agent for SQL.
> After backup procedures, you must (veritas wrote) shrink log file if
you
> want more space for bigger file.
> After log backup i must shrink log file.
> After shrink log file their was no change in size of log file.
>
> What mistake i do???
> Pls help!!!
>
> Thx to all.
if you are doing a full backup thru the agent, you will need to add in a
transaction log backup as weel to truncate the log.
--
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs
|
|
|
|