I got the full story. I think SQL Server memory configuration was changed from 2GB to 2mb? can anyone help me resolve?

Thanks all. now that SP3 has been successfully applied. I will go ahead and change 'sa' to a known password.. Thank you all...

Thank you. I guess not knowing the 'sa' password is not a deal breaker for applying the service pack.

The reason that I am only patching up...

I missed that.. THANK YOU!!!!

Try.. SELECT * FROM sys.server_triggers

I had the same problem and someone else helped me (today) on this forum.. happy turkey day!!!

SELECT * FROM sys.server_triggers WHERE parent_class=0

returns 0 rows as well.... bizzarre!!!!!!!!!!! anyone?

I create the Trigger (see above)

and then run SELECT * FROM sys.triggers WHERE parent_class=0 against the master DB

it returns 0 rows?

Quincy and his trusty assisant Sam Fujiyama to keep him in line 🙂

Thank you one and all.. time to put on my Quincy lab coat and go do some investigating on 'cte's 😀

Thank you!!!

I ran this and it worked:

;WITH cte

AS (SELECT ROW_NUMBER() OVER (PARTITION BY path, sortOrder,id, repname, repfilepath, language_cd, updateddate, repFormat

--add all column names col1,col2,...

ORDER BY ( SELECT 0)) RN

FROM dbo.OOReportFile_TEMP)

DELETE...

not sure what ;WITH cte means..

but I tried this:

Select * (SELECT ROW_NUMBER() OVER (PARTITION BY path, sortOrder,id, repname, repfilepath, language_cd, updateddate, repFormat

--add all column names col1,col2,...

ORDER BY...

Thank you all for your help and guidance

Thank you Gail and Lowell! maybe I'll have to play around with it a little but when I create my DDL trigger like this:

CREATE TRIGGER [Create_Database_Trigger]

ON ALL...

SELECT

DATEADD(D , 0 , DATEDIFF(D , 1 , GETDATE())) AS CreatedSince

, create_date AS CreatedOn

, *

FROM

sys.databases

WHERE

...

The DDL Triggers emails me when Database is created. Doesnt' tell me which Database - just which Instance the database was created in.

I would then have...