That would be a lot of rows to put in an excel and compare or filter on. querying the table directly for duplicates would be so much quicker.

It's weird that...

I tried and it didn't return any rows. I am thinking this may have something to do with the engine? If any knows?

This code executes several 1000 times a day...

shouldn't it be >1 for duplicates?

Corrected Query below. returns no rows

SELECT

tinclude.OrderId,

COUNT(tinclude.OrderId)

FROM

( SELECT v.OrderId FROM dbo.mdv_CustomerFilterCustomerTransDate v WITH (NOLOCK)

WHERE v.TerritoryCode IN (3) AND v.CustomerId = 649 AND ( v.CustomerTransDate...

Not Really. you mean a DISTINCT right after INSERT?

I am inserting into temp table taking values from the select distinct.

Contact your network administrator or check the event log - this could point to data corruption due to a hardware error.

I am worried about DB corruption. It's a production database 450GB in size.

Thanks for the idea. I can try it on dev and see if it works.

When I restore...

Phil's idea works perfect. Replacing the DTS GUID works.

Sorry. I forgot to mention. If I drop and recreate the jobs, they work fine. Interestingly, if I script the job and re-create, it still takes the old login. I restarted...

By inactive i mean the ones that are not used by any server process or user at all. I wanted to get rid of all the unnecessary extended stored procedures since...

Thanks for both replies !! I applied both the solutions and created a stored proc to identify inactive logins.

Sorry, Allen. I forgot to mention, I have the trace file on SQL 7 and fn_trace_gettable is SQL2000.

Any fn or SP on SQL7?

Is it possible to assign security admin, permissions to reset password for any login, w/o knowing the old password. For instance giving sysadmin permissions to sp_password stored procedure and grant...

Thanks to both of you !! It helped.