Using any third party tools like Quest Litespeed? Any CLR code or Integration services on this server? These are some of the things that can cause PLE drops.

Try checking out "MSSQL$InstanceName:Buffer Manager", "MSSQL$InstanceName:Memory Manager" and "Memory" perfmon counters. This would be a good place to start. Make sure you capture over a good period...

I've seen this when my service account loses it's "Log on as service" rights.

Might be something to check - could temporarily change the Agent service to use Local System account...

IgorMi (10/4/2013)

PLE min values should not go under 300 seconds. Fluctuating from 14h to 0.1h is still above 300 seconds, but the behavior itslef is not good for the database...

Could also be in an agent job...

We see this behaviour when our Litespeed backups kick off during our maintenance window

Hi,

I had to set this up a few weeks ago (SQL2008R2 to Oracle 11g Subscriber).

Some tips:

- You will need to install the oracle client tools on the distributor and...

haha - wondered if something like this was available 🙂

+1 to what Koen said.

I only explain logic and why I've done it a specific way.

I think it's safe to assume a basic understanding of sql - especially...

The following query will return the instance and...

If you suspect a poorly performing query you could check the execution plan to see what the cardinality estimates are too. If there is skew (estimated 1, actual thousands...

this is what I came up with from your existing structure (after making the insert statements work)

WITH cte

AS

(

SELECTc

,ROW_NUMBER() OVER(ORDER BY c) AS rowid

FROM table1

),

cte2

AS

(

SELECT c

,ROW_NUMBER() OVER(ORDER BY c) AS rowid

FROM...

1 password per instance. We personally have a stored procedure which creates secure passwords up to 15 characters long with varied case / numbers / symbols (excluding certain symbols)....

FIXED:

My sp_addarticle command was missing the @status parameter (with a value of 0).

I don't fully understand why a value of zero made this work though as BOL state...

have you checked C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\Detail.txt for the details?

Shrinking dbs are never a nice task for many reasons - if you absolutely have to do it remember to run your reindexing/update stats afterwards....