Stop and restart the job. Make sure that Full and or Diff backup jobs are not running while you are attempting to run this transaction log backup job..

Thansk!!

Ok- while using the Wizard, the first step should prompt you to specify the location of the backup. Specify 'to disk' and then add the disk you want the database...

We use SQL Litespeed 2005 version 4.8 from Quest Software. It supports different levels of compression of your backup file, encryption and also Object level recovery...and above all is easy...

Look below for the difference in the way you use the dbcc showcontig command

--DBCC SHOWCONTIG(TABLE_PROD_RES)

DBCC SHOWCONTIG scanning 'TABLE_PROD_RES' table...

Table: 'TABLE_PROD_RES' (1241211622); index ID: 1, database ID: 5

TABLE level scan...

try to query the system tables like dbo.backupfile and dbo.backupset on the msdb database.

Thanks!!

Is the rowcount on the primary table consistent? Try to create the temp table without the identity key and see for the number of rows, I guess it will be...

I ran the above statements you mentioned before running the jobs. I am not sure if I was able to view the job properties before enabling the above procedures. Do...

1.Create the mirror database by restoring with NORECOVERY a recent full backup available of the principal database (in your case the production database). The mirror database must have the same...

use this : DBCC SHOWCONTIG(tablename)

In the results check for the logical scan fragmentation, which ideally should be 0.01%

Thanks!!

Any views will be appreciated..Thanks!!

Why don't you try this for updating the statistics

UPDATE STATISTICS DaveTable(anames)

WITH FULLSCAN, NORECOMPUTE

GO

Thanks!!

How long does it take to run this job? Determine the time when there are least number of jobs running, then schedule this job. As you have tried already. Discuss...

Also try Network Data Mover, this was used by a colleague of mine to rebuild a crashed server :w00t: .They pulled all the files overnight 😎

Try ROBOCOPY

Thanks!!

Include all the stored procs that you would use in the maintenance jobs and the once with notification too. Simple recovery would be enough and if you don't update it...