I need a little MSDE 2000 help

I think it would be better to backup to a different file name from the last
backup. that way if the current backup fails, at least you still have
yesterday's backup.

when it succeeds, then you can delete the old and rename the new.

--
http://elsasoft.org



"Ekrem Önsoy" wrote in message

> Change your script as the following:
>
> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
> 'E:\mssql7\backup\mydb.bak' WITH INIT"
>
> It uses WITH NOINIT by default, so using WITH INIT will overwrite the
> older backup file.
>
>
> --
> Ekrem Önsoy
>
>
>
> "Clayton Sutton" wrote in message
>
>> Hey everyone,
>>
>> I have a system that is running MSDE 2000 and we run the following script
>> to back it up:
>>
>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>> 'E:\mssql7\backup\mydb.bak'"
>>
>> The problem is that it appends and fills up my HD. Anyone know what I
>> would need to do to change it to "overwrite"?
>>
>> TIA,
>>
>>
>> Clayton
>>
>
 >> Stay informed about: I need a little MSDE 2000 help 

A recent discussion in one of these groups pointed out that the backup is
written to a temp file and when complete, the old file is deleted and the
new backup file renamed automatically. So, following Ekrem's advice should
preserve the previous backup if the current one fails. (A little bit of
built in safety from the SQL Server guys.)

RLF

"Jesse Hersch" wrote in message

>I think it would be better to backup to a different file name from the last
>backup. that way if the current backup fails, at least you still have
>yesterday's backup.
>
> when it succeeds, then you can delete the old and rename the new.
>
> --
> http://elsasoft.org
>
>
>
> "Ekrem Önsoy" wrote in message
>
>> Change your script as the following:
>>
>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>> 'E:\mssql7\backup\mydb.bak' WITH INIT"
>>
>> It uses WITH NOINIT by default, so using WITH INIT will overwrite the
>> older backup file.
>>
>>
>> --
>> Ekrem Önsoy
>>
>>
>>
>> "Clayton Sutton" wrote in message
>>
>>> Hey everyone,
>>>
>>> I have a system that is running MSDE 2000 and we run the following
>>> script to back it up:
>>>
>>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>>> 'E:\mssql7\backup\mydb.bak'"
>>>
>>> The problem is that it appends and fills up my HD. Anyone know what I
>>> would need to do to change it to "overwrite"?
>>>
>>> TIA,
>>>
>>>
>>> Clayton
>>>
>>
>
>
 >> Stay informed about: I need a little MSDE 2000 help 

I would say it's worth testing this behavior yourself before you rely on it.

--
http://elsasoft.org



"Russell Fields" wrote in message

>A recent discussion in one of these groups pointed out that the backup is
>written to a temp file and when complete, the old file is deleted and the
>new backup file renamed automatically. So, following Ekrem's advice should
>preserve the previous backup if the current one fails. (A little bit of
>built in safety from the SQL Server guys.)
>
> RLF
>
> "Jesse Hersch" wrote in message
>
>>I think it would be better to backup to a different file name from the
>>last backup. that way if the current backup fails, at least you still
>>have yesterday's backup.
>>
>> when it succeeds, then you can delete the old and rename the new.
>>
>> --
>> http://elsasoft.org
>>
>>
>>
>> "Ekrem Önsoy" wrote in message
>>
>>> Change your script as the following:
>>>
>>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>>> 'E:\mssql7\backup\mydb.bak' WITH INIT"
>>>
>>> It uses WITH NOINIT by default, so using WITH INIT will overwrite the
>>> older backup file.
>>>
>>>
>>> --
>>> Ekrem Önsoy
>>>
>>>
>>>
>>> "Clayton Sutton" wrote in message
>>>
>>>> Hey everyone,
>>>>
>>>> I have a system that is running MSDE 2000 and we run the following
>>>> script to back it up:
>>>>
>>>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>>>> 'E:\mssql7\backup\mydb.bak'"
>>>>
>>>> The problem is that it appends and fills up my HD. Anyone know what I
>>>> would need to do to change it to "overwrite"?
>>>>
>>>> TIA,
>>>>
>>>>
>>>> Clayton
>>>>
>>>
>>
>>
>
>
 >> Stay informed about: I need a little MSDE 2000 help 

Thanks guys for all of your input. I will give it a try! Have a great
Xmas.


Clayton



"Jesse Hersch" wrote in message

>I would say it's worth testing this behavior yourself before you rely on
>it.
>
> --
> http://elsasoft.org
>
>
>
> "Russell Fields" wrote in message
>
>>A recent discussion in one of these groups pointed out that the backup is
>>written to a temp file and when complete, the old file is deleted and the
>>new backup file renamed automatically. So, following Ekrem's advice
>>should preserve the previous backup if the current one fails. (A little
>>bit of built in safety from the SQL Server guys.)
>>
>> RLF
>>
>> "Jesse Hersch" wrote in message
>>
>>>I think it would be better to backup to a different file name from the
>>>last backup. that way if the current backup fails, at least you still
>>>have yesterday's backup.
>>>
>>> when it succeeds, then you can delete the old and rename the new.
>>>
>>> --
>>> http://elsasoft.org
>>>
>>>
>>>
>>> "Ekrem Önsoy" wrote in message
>>>
>>>> Change your script as the following:
>>>>
>>>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>>>> 'E:\mssql7\backup\mydb.bak' WITH INIT"
>>>>
>>>> It uses WITH NOINIT by default, so using WITH INIT will overwrite the
>>>> older backup file.
>>>>
>>>>
>>>> --
>>>> Ekrem Önsoy
>>>>
>>>>
>>>>
>>>> "Clayton Sutton" wrote in message
>>>>
>>>>> Hey everyone,
>>>>>
>>>>> I have a system that is running MSDE 2000 and we run the following
>>>>> script to back it up:
>>>>>
>>>>> osql -Usa -P -n -Q "Backup Database MyDB To Disk =
>>>>> 'E:\mssql7\backup\mydb.bak'"
>>>>>
>>>>> The problem is that it appends and fills up my HD. Anyone know what I
>>>>> would need to do to change it to "overwrite"?
>>>>>
>>>>> TIA,
>>>>>
>>>>>
>>>>> Clayton
>>>>>
>>>>
>>>
>>>
>>
>>
>
>
 >> Stay informed about: I need a little MSDE 2000 help