You could always use SQL Agent "Tokens" as well. Gert Drapers has some good examples at http://sqldev.com. Although the 2005 token names have changed a bit, but they're still there :)

PingBack from http://www.gadgetgadget.info/?p=23654

I'd actually agree with your approach here and use the TSQL. Usually I only use Tokens for the output files as well. For a more focused backup scheme on a single database, I'll usually use tokens for the dynamic naming. If more than one database is involved (or a dynamic number, such as a hosting server or a development one that is in constant flux), a TSQL script such as what you've got here is the ticket :)

Ticket, Token? Almost sounds like comparing Kerberos to NTLM :) Ack! :)

You could always use the QUOTENAME function to make things a little safer:

SET @sql = 'BACKUP ' + CASE @backup_type WHEN 'LOG' THEN 'LOG' ELSE 'DATABASE' END + ' ' + QUOTENAME(@db_name) + @crlf

SET @sql = @sql + 'TO DISK = ' + QUOTENAME(@full_path_and_filename,'''') + @crlf

SET @sql = @sql + 'WITH' + @crlf

SET @sql = @sql + ' NOINIT,' + @crlf

SET @sql = @sql + ' NAME = ' + QUOTENAME(@filename,'''') + ',' + @crlf

I would like to share some code for doing backups that works a little differently than Tibor's. It is available on http://ola.hallengren.com.

A few months ago, I blogged about a simple procedure to do backup ( http://sqlblog.com/blogs/tibor_karaszi/archive/2007/09/25/tsql-script-to-do-backup-like-maintenance-plans.aspx

A few months ago, I blogged about a simple procedure to do backup ( http://sqlblog.com/blogs/tibor_karaszi/archive/2007/09/25/tsql-script-to-do-backup-like-maintenance-plans.aspx