The error checking seems to work better than the @@error after exiting out of a xp_cmdshell DOS task concerning a failed or successfull attempt.
--@backupfile is just the file name being used
DECLARE @cmdstr2 nvarchar(4000),@retval2 int
SET @cmdstr= 'copy /Y '+@BackupFile+ 'f:\db_dump\db_name\'
EXEC @retval2 = master..xp_cmdshell @cmdstr
IF (@retval2 = 0)
BEGIN
Print 'The file '+@BackupFile+ ' was moved to f:\db_dump\db_name\ successfully.'
END
ELSE
BEGIN
--Page Block goes here to page the DBA....
Print ' The Move failed contact The Red Ranger'
Return
END 
When doing bulk data changes it may be beneficial to disable indexes prior to starting the operation. Fortunately, SQL's rich metadata makes this very easy to automate in a robust fashion.
2018-05-18 (first published: 2015-10-19)
4,928 reads
If you think about it carefully, you’ll realise, that index maintenance is necessary and that it makes sense, and that SQL Server is not doing this task automatically according to the book.
2011-08-18
5,492 reads
Far too often, people who are not trained database administrators somehow end up responsible for a database. They lack the proper training and knowledge to maintain their database, and problems begin to develop. Here’s a primer for all those involuntary DBAs who need a crash course in database maintenance best practices.
2008-08-13
6,696 reads
This script will change the owner of the stored procedure to dbo. It must be run in the same database as the stored procedures.
2001-10-28
1,626 reads
Ever wanted to know whether your triggers are enabled or not? The ObjectProperty command allows you to select information about the status of objects in your database, returning 1 for True and 0 for False. The example below determines whether a single trigger is disabled. SELECT ObjectProperty(object_id('Trigger_Name'), 'ExecIsTriggerDisabled') There are a number of other useful […]
2001-10-28
1,377 reads