Chris,
I have a few comments:
RESTORE VERIFYONLY checks to see that the backup set is complete
and that all volumes are readable. RESTORE VERIFYONLY does NOT
check the structure of the data on the volumes.
I always wondered how this is a "verification" of a restore
if you don't really restore th
Is your DBA talking about shrinking the log file or truncating the log? One
thing to look out for here is the fact that these are two different things,
and lots of SQL people can get confused about this. Truncating a SQL Server
log is not the same as shrinking the physical file that houses the lo
David,
Check this out:
http://www.microsoft.com/sql/techinfo/tips/administration/logfilegrowth.asp
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 04/06/2004
10:40:44 AM:
> Can you reference me an MS SQL doc or something
ngo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004 10:41 AM
To: [EMAIL PROTECTED]
Subject: Re: TDP SQL Transaction log not truncating
Can you reference me an MS SQL doc or something on this? My
SQL DBA's are kind of anti-TSM, so I need as much justification
on this as I can get to g
Can you reference me an MS SQL doc or something on this? My
SQL DBA's are kind of anti-TSM, so I need as much justification
on this as I can get to give to them.
(If this is the way it works and I dio a FULL daily at 3 am and log
backups every hour, then if they do "reindex" at say midnight,
the
I remember having same problem; and yes you are right.
Even if you are doing incremental sql backup; if in between two incremental backups
you run "reindex", next incremental will be similar in size as full backup. Logically
this is still incremental only it is too big.
We ended up running reinde
