Backups & SQL2005Express

Jul 25, 2006 5 Replies

I'm just about to upgrade to SQL2005 Express and last item on the checklist is backups. Currently on MSDE I have script scheduled to run each night that contains osql -U sa -P password -S ssss -Q "BACKUP DATABASE xxxxx TO DISK 'c:\backup\rms.bck'"



This command won't work on my SQL05 test machine. Anyone know what command I would need to achieve a the same result with SQL05



Cheers


SQL Server 2005 Express has a different command line interface...

This l> I'm just about to upgrade to SQL2005 Express and last item on the checklist

In case it helps anyone else, this seems to work for me

sqlcmd -U sa -P password -Q "BACKUP DATABASE [MyDatabase] TO DISK N'c:\Backup.bak' WITH NOFORMAT, INIT, NAME = N'MyDatabase-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10"

Cheers

I am still using MSDE. I use a batch file with an OSQL command line similar to yours.

I notice that the file extension on your backup file has changed from .bck to .bak. Once upon a time, I either read or heard that .bak is an unsupported backup format for RMS. If you want help from Microsoft recovering lost data, your backup file should be .bck. If you use the Admin or Manager programs to create a backup file, you get .bck.

Does simply specifying .bck as part of the filename change the format of the backup file? Can you use .bck in your OSQL statement with SQL Express 2005? Does it really matter?

Tom

"jetspeed" wrote:

we use our own made-up extension. no problems. the way i see it is it's just a file name, it's the data that counts.

I would think just the default program associations would matter..

I'm more a developer than a DBA, but I think that .BAK is the default extension used by incremental backups under the "Full" recovery model. RMS SO Administrator wants a full backup created with the "Simple" Recovery model.

As far as I have seen, as long as the file is a full backup, it's just a file - extension doesn't seem to have any bearing...

Glenn Adams Tiber Creek C> we use our own made-up extension. no problems. the way i see it is it's just

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required