what service pack you are on and is backup failure time and latch warning time matches?

Latch issues mostly related to HW....

http://support.microsoft.com/kb/310834

http://support.microsoft.com/kb/303640

If you use old system table now they are views in 2005 you get the same behaviour where as if you use new catolog views or tables you don't get...

You can use xp_delete_file  procedure incase of you have issue with cleanup task...

I don't have this kind of issue but I am using 32 bit.

declare @dt datetime

select @dt=getdate()-1

EXECUTE master.dbo.xp_delete_file...

What is the size of the database? If you need only data then you have to use dts or bcp..

If you complete db with schema and data then backup restore...

There is no good help from MS in this reagard but you can use fn_dblog() function...

http://www.novicksoftware.com/UDFofWeek/Vol1/T-SQL-UDF-Volume-1-Number-27-fn_dblog.htm

It is better to use third party tools like Log Explorer, ApexSQL's Log

Navigator..

http://www.lumigent.com/products/le_sql.html

Thanks Anders Pedersen... I was looking at the wrong place....

I think now I know why it is not working...

In sql 2005 all columns will not work with all events... so...

It could be autogrow but not sure...

What was inputbuffer of that SPID when it was locking the FILE?

How to shrink the tempdb database in SQL Server

http://support.microsoft.com/kb/307487

You can schedule both dts packages to run in one job...

if (datepart(dd,getdate()) = 15 )OR (datepart(dd,getdate()) = 1 )

BEGIN

EXEC XP_CMDSHELL 'DTSRUN.... FORTNIGHT DTS PACKAGE..' --OR you can configure the another...

You got it..

If your email id datatype is varchar then you don't need to use RTRIM function...

Enable trace flags 3605 and 1204 which will write the information to sql error log so that you can find what statement is causing the deadlocking...

DBCC TRACEON (3605,1204,-1)

Is your columnid 38 is correct...?

I don't think we have 38 columns in sql trace...

Try scripting the trace script from profiler...

You can use SSIS package to backup and copy the files to ftp location and schedule the package to run as needed...

In SSIS package you have to EXECUTE SQL TASK...

You have to remove all 'GO' statements from your code...

GO statement is batch separator in SQL.