The logs are getting full every so often and we do not know why. One of the reasons could be that we are running profiler from time to time.

Thanks.

I found the solution:

exec sp_msforeachdb ' use[?];

DECLARE @DBName VarChar(150);

SET @DBNAME = db_name();

DUMP TRAN @DBNAME WITH TRUNCATE_ONLY'

I am concerned because ghost cleanup is running on databases that does not have any activity what so ever. These are dead dbs and yet ghost cleanup is running on...

Is there any one who knows this?

Thanks.

Yes, that's what I meant. That is certainly great information. Thanks for your time.

Thanks for the articles. So there is no way of knowing whether the object is cached or not. But what I can look for is consistency whether the same object...

Hello Leo,

What do you mean by cache reads and writes. It is misleading.

Thanks.

Thanks Grant, that helps.

That helped! Thanks.

I found a solution which is not perfect but doable:

SELECT Name, LastWaitType, Crdate,

CASE WHEN Last_Batch > Login_Time

THEN Last_Batch ELSE Login_Time END AS [LastTouched]

FROM SysDatabases o

LEFT JOIN SysProcesses s

ON...

But how would you use sp_msforeachdb with Niconecy's code?

That is for only one database, but what if i want to find the search string on all databases on a particuar instance?

Thanks.

Thanks that helped.

Thank you.

Thanks for your response. Exactly how would I do it?