|
|
Posted by Hugo Kornelis on 06/11/06 20:19
On Sat, 10 Jun 2006 12:51:23 +0000 (UTC), Erland Sommarskog wrote:
>Greg D. Moore (Strider) (mooregr_deleteth1s@greenms.com) writes:
>> "Hugo Kornelis" <hugo@perFact.REMOVETHIS.info.INVALID> wrote in message
>> news:5hmi82pfl02iqnhelegm0v515dbdm1qpid@4ax.com...
>>> BACKUP LOG <databasename>
>>> TO DISK = 'x:\y\z\logbackup.bak'
>>> WITH COPY_ONLY;
>>
>> Is this a SQL 2005 specific command? I've never seen it before.
>
>Yes, that's a new addition (which I neither I had noticed until Hugo
>posted about it). It appears to be a "NO_TRUNCATE light". That is,
>NO_TRUNCATE also waives the requirement that the database should be
>accessible etc and is mainly intended for emergency situations.
Hi Erland,
That's right. The major advantage of COPY_ONLY over NO_TRUNCATE is (IMO)
that this option also works on full and incremental backups. It's a
great way to quickly get a backup of a DB to do some tests or
trouble-shooting on without disrupting the backup schema.
--
Hugo Kornelis, SQL Server MVP
Navigation:
[Reply to this message]
|