setup PageHeight and PageWidth properties in the report.

Try something like

select distinct object_name(a.id) table_name, b.collation

 from syscolumns a inner join systypes b on a.xusertype = b.xusertype

 where a.collationid = b.collationid

 and not exists(select * from sysobjects c where a.id = c.id...

A script will do. Call the script in DTS.

Following sample rename aa.txt to a random generated name.

dim fso, sourcefilename, tempfile

set fso=createobject("Scripting.Filesystemobject")sourcefilename="c:\temp\aa.txt"

tempfile=fso.gettempname

fso.copyfile sourcefilename, tempfile

wscript.echo tempfile

Use script to convert to xls first.

Here is a sample. It converts aa.slk to bb.xls, then you can DTS into SQL Server.

Dim wb

set wb = CreateObject("Excel.Application")

wb.Workbooks.Open("C:\temp\aa.slk")

wb.Workbooks(1).Activate

wb.ActiveWorkbook.SaveAs "C:\temp\bb.xls", 1

wb.Workbooks.Close()

Assume data types are the same

Update a

 set jobtargets = b.id

from old_jobtargets a

 inner join new_jobtargets b on a.jobtargets = b.jobtargets

Check sql error log near the moment of crash for historical records.

Setup alert on connection number may be used for ongoing base.

DECLARE @cdr_date datetime

DECLARE @filename varchar(15), @cmd varchar(4000), @sql varchar(2000)

SET @cdr_date = getdate()-1

SET @filename = 'g_' +

 substring(convert(varchar, @cdr_date, 120), 6, 2) +

 substring(convert(varchar, @cdr_date, 120), 9, 2) +

 substring(convert(varchar, @cdr_date, 120),...

One option is

Weekly full backup restore (keep the copy), daily Differential backup restore.

try this

select * from eventtable a

 where exists(select * from eventtable b

 where a.eventlog = b.eventlog

 and datediff(dd, b.eventdate, a.eventdate) > 10)

-- and a.eventdate >= ''

EM can access database remotely. then use right to limit what can be seen for each user.

Try to make records unique.

I had similar case, a unique index in source table killed the problem.

The complete backup on primary database has NO impact on log shipping from data integrity view point.

My experience (similar to it) directs to tempdb default collation out of sync with the restored SQL 7.0 DB. It explains "run just fine when pointing at a DB created...

The default value is in registry

HKEY_LOCAL_MACHINE

  SOFTWARE

    Microsoft

      MSSQLServer

        SQLServerAgent

          JobHistoryMaxRows

A trace in Maintenance job indicates msdb.dbo.sysdbmaintplans is the table to change.

check logshipping concept in Book on-line. It may help you.