Good question Greg.

Nonsense. The issue, workarounds, and permanent fixes are perfectly clear.

I would encourage you to check what product versions you are actually running.If you struggle with this task, hire a professional...

Genuinely agree. Thanks for the advice.

I am just saying that I am not interested in the details of how you run your...

@paul-2,

Workarounds do work. But they are temporary and the issue can re occur on...

No. I prefer Jason's approach. Logging every small transaction is just pointless in the context of this article, as I have made clear already. You will just make it harder...

@paul-2,

One thing...

@paul-2,

It seems correct to me. The idea is to capture information about the occasional rogue process that consumes an unusual amount of log space and thus causes a log growth....

Well, I have systems running with SP2 + still facing the issue.

And I know few people who have the same issue even after sp3.

Lemme explain a bit more...

Hi Jason,

Thanks Jason.

My experience has shown that sustained growths typically come from long running transactions. Many times those transactions finish before somebody can get into the system to find what...

Hi Jason,

The reason i felt getting sleeping ones are also better is because we would increase the chances of finding the actual queries. And at times if we have a...

Hi Jason,

The query you used to capture tsqls doesnt capture sleeping connections. Was that intentional? I would prefer to grab the sleeping ones as well so that I grab...

How about this

Select Count(*)

FROM CourtHearing

WHERE datediff(dd,isnull(postponement_date,Hearing_date),getdate()) > 30

This one will not perform well either.

Even when you script it out, the Scripts coming from SSMS will be SQL 2005 compatible by default. Use the option Script for version 'SQL Server 2000'

http://www.databasejournal.com/features/mssql/article.php/3116011/Linked-Severs-on-MS-SQL-Part-3.htm

The bottom of this link should explain it all. Post here for any more doubts

@Keyun21,

'Be made using the login's current security context' means 'The account used in the orginal server will be applied at the target server as well'.

To explain bit more, if you...