-- delete the emails

DECLARE @delete_date datetime

SET @delete_date = dateadd(dd,-1,getdate())

print @delete_date

EXECUTE msdb.dbo.sysmail_delete_mailitems_sp @sent_before='Jun 2 2008 12:11PM'

-- this deletes the logs

EXECUTE msdb.dbo.sysmail_delete_log_sp

GO

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2974180&SiteID=1

according to an earlier post it looks like a network intrusion

My current db's are client specific

To get around the reporting across servers

you just setup a job to import the needed information into a report server

I currently use log shipping on 30+ databases

with both low and high volume sites

The only issue i have with log shipping is when you update stats or rebuild indexes which...

I have had that problem in the past

most of the time if i go to the subscriber and drop it there it works

2k5 lots of time will remove it from...

the identity column should go on regardless of deletes

It doesnt reset if you are using an identity column

i usually run sp_updatestats

then i run sp_change_users_login 'auto_fix'

to fix the mismatched logins

Log shipping has a read only option that i use for report servers

The issue is will kick the users out to restore the database

I do it like this and then call this into a temp table

for each server

--exec sp_diskspace

CREATE PROCEDURE sp_diskspace

AS

/*

Displays the free space,free space percentage

...

I got around the dbcc issue by creating sp's on master that are then called by the linked servers  

Can't you use the new pivot option

USE AdventureWorks;GOSELECT VendorID, [164] AS Emp1, [198] AS Emp2, [223] AS Emp3, [231] AS Emp4, [233] AS Emp5FROM (SELECT PurchaseOrderID, EmployeeID, VendorIDFROM Purchasing.PurchaseOrderHeader) pPIVOT(COUNT...

It appears the replication isnt clearing the command history

after about 2 weeks the number suddenly went from 500,000 to 10

that works on my replication if i run it on the distributor

it is not just the like clause causing issues

several linked server queries take 10 seconds in sql2000

and 5 minutes or more in sql2005

also several queries using temp databases take minutes...

found my own answer

http://msdn2.microsoft.com/en-us/library/ms151313.aspx