My PLE Counter value is 483.what is the safe side for PLE buffer manager value?












0















Today morning i ran this scripts and i got 483.is that counter value is good ?



select [OBJECT_NAME],
[counter_name],
[cntr_value]from sys.dm_os_performance_counters
where[OBJECT_NAME]like '%Manager%'
AND [counter_name]='page life expectancy'









share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • What is max server memory and total RAM present on system? Anyways this does not looks good

    – Shanky
    Dec 13 '16 at 13:51













  • SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM sys.dm_os_process_memory;i Ran this Scripts and it gives me memory used by sqlserver 8978MB.how do i fix this problem?@Shanky

    – shamim
    Dec 13 '16 at 13:58













  • Is the server running fine? If it is this might be normal for you.

    – Sean Gallardy
    Dec 13 '16 at 14:00











  • pretty much i do not find any problem so far .Can you please tell me if PLE running high what kind of problems i could get ?@Sean Gallardy

    – shamim
    Dec 13 '16 at 14:17











  • I asked you max server memory and you gave me memory consumed by SQL Server. Anyways I assume max server memory is around 9 G in that case 483 seems bit less BUT, PLE fluctuating on SQL Server is quite normal and this can happen many a times when load on system is high. Other question does PLE remains to this value always or it rises up ?

    – Shanky
    Dec 13 '16 at 14:26
















0















Today morning i ran this scripts and i got 483.is that counter value is good ?



select [OBJECT_NAME],
[counter_name],
[cntr_value]from sys.dm_os_performance_counters
where[OBJECT_NAME]like '%Manager%'
AND [counter_name]='page life expectancy'









share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • What is max server memory and total RAM present on system? Anyways this does not looks good

    – Shanky
    Dec 13 '16 at 13:51













  • SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM sys.dm_os_process_memory;i Ran this Scripts and it gives me memory used by sqlserver 8978MB.how do i fix this problem?@Shanky

    – shamim
    Dec 13 '16 at 13:58













  • Is the server running fine? If it is this might be normal for you.

    – Sean Gallardy
    Dec 13 '16 at 14:00











  • pretty much i do not find any problem so far .Can you please tell me if PLE running high what kind of problems i could get ?@Sean Gallardy

    – shamim
    Dec 13 '16 at 14:17











  • I asked you max server memory and you gave me memory consumed by SQL Server. Anyways I assume max server memory is around 9 G in that case 483 seems bit less BUT, PLE fluctuating on SQL Server is quite normal and this can happen many a times when load on system is high. Other question does PLE remains to this value always or it rises up ?

    – Shanky
    Dec 13 '16 at 14:26














0












0








0








Today morning i ran this scripts and i got 483.is that counter value is good ?



select [OBJECT_NAME],
[counter_name],
[cntr_value]from sys.dm_os_performance_counters
where[OBJECT_NAME]like '%Manager%'
AND [counter_name]='page life expectancy'









share|improve this question
















Today morning i ran this scripts and i got 483.is that counter value is good ?



select [OBJECT_NAME],
[counter_name],
[cntr_value]from sys.dm_os_performance_counters
where[OBJECT_NAME]like '%Manager%'
AND [counter_name]='page life expectancy'






sql-server sql-server-2008-r2 performance performance-tuning






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 13 '16 at 13:48









Shanky

14k32039




14k32039










asked Dec 13 '16 at 13:38









shamimshamim

31119




31119





bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • What is max server memory and total RAM present on system? Anyways this does not looks good

    – Shanky
    Dec 13 '16 at 13:51













  • SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM sys.dm_os_process_memory;i Ran this Scripts and it gives me memory used by sqlserver 8978MB.how do i fix this problem?@Shanky

    – shamim
    Dec 13 '16 at 13:58













  • Is the server running fine? If it is this might be normal for you.

    – Sean Gallardy
    Dec 13 '16 at 14:00











  • pretty much i do not find any problem so far .Can you please tell me if PLE running high what kind of problems i could get ?@Sean Gallardy

    – shamim
    Dec 13 '16 at 14:17











  • I asked you max server memory and you gave me memory consumed by SQL Server. Anyways I assume max server memory is around 9 G in that case 483 seems bit less BUT, PLE fluctuating on SQL Server is quite normal and this can happen many a times when load on system is high. Other question does PLE remains to this value always or it rises up ?

    – Shanky
    Dec 13 '16 at 14:26



















  • What is max server memory and total RAM present on system? Anyways this does not looks good

    – Shanky
    Dec 13 '16 at 13:51













  • SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM sys.dm_os_process_memory;i Ran this Scripts and it gives me memory used by sqlserver 8978MB.how do i fix this problem?@Shanky

    – shamim
    Dec 13 '16 at 13:58













  • Is the server running fine? If it is this might be normal for you.

    – Sean Gallardy
    Dec 13 '16 at 14:00











  • pretty much i do not find any problem so far .Can you please tell me if PLE running high what kind of problems i could get ?@Sean Gallardy

    – shamim
    Dec 13 '16 at 14:17











  • I asked you max server memory and you gave me memory consumed by SQL Server. Anyways I assume max server memory is around 9 G in that case 483 seems bit less BUT, PLE fluctuating on SQL Server is quite normal and this can happen many a times when load on system is high. Other question does PLE remains to this value always or it rises up ?

    – Shanky
    Dec 13 '16 at 14:26

















What is max server memory and total RAM present on system? Anyways this does not looks good

– Shanky
Dec 13 '16 at 13:51







What is max server memory and total RAM present on system? Anyways this does not looks good

– Shanky
Dec 13 '16 at 13:51















SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM sys.dm_os_process_memory;i Ran this Scripts and it gives me memory used by sqlserver 8978MB.how do i fix this problem?@Shanky

– shamim
Dec 13 '16 at 13:58







SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM sys.dm_os_process_memory;i Ran this Scripts and it gives me memory used by sqlserver 8978MB.how do i fix this problem?@Shanky

– shamim
Dec 13 '16 at 13:58















Is the server running fine? If it is this might be normal for you.

– Sean Gallardy
Dec 13 '16 at 14:00





Is the server running fine? If it is this might be normal for you.

– Sean Gallardy
Dec 13 '16 at 14:00













pretty much i do not find any problem so far .Can you please tell me if PLE running high what kind of problems i could get ?@Sean Gallardy

– shamim
Dec 13 '16 at 14:17





pretty much i do not find any problem so far .Can you please tell me if PLE running high what kind of problems i could get ?@Sean Gallardy

– shamim
Dec 13 '16 at 14:17













I asked you max server memory and you gave me memory consumed by SQL Server. Anyways I assume max server memory is around 9 G in that case 483 seems bit less BUT, PLE fluctuating on SQL Server is quite normal and this can happen many a times when load on system is high. Other question does PLE remains to this value always or it rises up ?

– Shanky
Dec 13 '16 at 14:26





I asked you max server memory and you gave me memory consumed by SQL Server. Anyways I assume max server memory is around 9 G in that case 483 seems bit less BUT, PLE fluctuating on SQL Server is quite normal and this can happen many a times when load on system is high. Other question does PLE remains to this value always or it rises up ?

– Shanky
Dec 13 '16 at 14:26










1 Answer
1






active

oldest

votes


















0














The Page Life Expectancy counter tells you for how many seconds an 8KB data page will remain in the buffer pool, before being flushed out.



A low number can be a sign of memory pressure, but it may also be a sign of nothing.



If your data access patterns involve a lot of report-style queries, reading a lot of data from large tables, this could be normal.



Monitor the value over several days, at different times in the day, and you may find that this is an outlier. I have a customer whose PLE goes to zero every time a certain large index is rebuilt, but it steadily increases after that.



My first sense is to review indexes, and see if a well-placed index can help with large reads. Another best practice is to avoid using SELECT * FROM table if you can help it.



You may need to increase the physical RAM in the server, but that shouldn't be your first reaction.



(Read more here about PLE and NUMA nodes: http://www.sqlskills.com/blogs/paul/page-life-expectancy-isnt-what-you-think/)






share|improve this answer
























  • today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

    – shamim
    Dec 14 '16 at 13:09











  • Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

    – Randolph West
    Dec 21 '16 at 14:56











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f158036%2fmy-ple-counter-value-is-483-what-is-the-safe-side-for-ple-buffer-manager-value%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














The Page Life Expectancy counter tells you for how many seconds an 8KB data page will remain in the buffer pool, before being flushed out.



A low number can be a sign of memory pressure, but it may also be a sign of nothing.



If your data access patterns involve a lot of report-style queries, reading a lot of data from large tables, this could be normal.



Monitor the value over several days, at different times in the day, and you may find that this is an outlier. I have a customer whose PLE goes to zero every time a certain large index is rebuilt, but it steadily increases after that.



My first sense is to review indexes, and see if a well-placed index can help with large reads. Another best practice is to avoid using SELECT * FROM table if you can help it.



You may need to increase the physical RAM in the server, but that shouldn't be your first reaction.



(Read more here about PLE and NUMA nodes: http://www.sqlskills.com/blogs/paul/page-life-expectancy-isnt-what-you-think/)






share|improve this answer
























  • today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

    – shamim
    Dec 14 '16 at 13:09











  • Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

    – Randolph West
    Dec 21 '16 at 14:56
















0














The Page Life Expectancy counter tells you for how many seconds an 8KB data page will remain in the buffer pool, before being flushed out.



A low number can be a sign of memory pressure, but it may also be a sign of nothing.



If your data access patterns involve a lot of report-style queries, reading a lot of data from large tables, this could be normal.



Monitor the value over several days, at different times in the day, and you may find that this is an outlier. I have a customer whose PLE goes to zero every time a certain large index is rebuilt, but it steadily increases after that.



My first sense is to review indexes, and see if a well-placed index can help with large reads. Another best practice is to avoid using SELECT * FROM table if you can help it.



You may need to increase the physical RAM in the server, but that shouldn't be your first reaction.



(Read more here about PLE and NUMA nodes: http://www.sqlskills.com/blogs/paul/page-life-expectancy-isnt-what-you-think/)






share|improve this answer
























  • today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

    – shamim
    Dec 14 '16 at 13:09











  • Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

    – Randolph West
    Dec 21 '16 at 14:56














0












0








0







The Page Life Expectancy counter tells you for how many seconds an 8KB data page will remain in the buffer pool, before being flushed out.



A low number can be a sign of memory pressure, but it may also be a sign of nothing.



If your data access patterns involve a lot of report-style queries, reading a lot of data from large tables, this could be normal.



Monitor the value over several days, at different times in the day, and you may find that this is an outlier. I have a customer whose PLE goes to zero every time a certain large index is rebuilt, but it steadily increases after that.



My first sense is to review indexes, and see if a well-placed index can help with large reads. Another best practice is to avoid using SELECT * FROM table if you can help it.



You may need to increase the physical RAM in the server, but that shouldn't be your first reaction.



(Read more here about PLE and NUMA nodes: http://www.sqlskills.com/blogs/paul/page-life-expectancy-isnt-what-you-think/)






share|improve this answer













The Page Life Expectancy counter tells you for how many seconds an 8KB data page will remain in the buffer pool, before being flushed out.



A low number can be a sign of memory pressure, but it may also be a sign of nothing.



If your data access patterns involve a lot of report-style queries, reading a lot of data from large tables, this could be normal.



Monitor the value over several days, at different times in the day, and you may find that this is an outlier. I have a customer whose PLE goes to zero every time a certain large index is rebuilt, but it steadily increases after that.



My first sense is to review indexes, and see if a well-placed index can help with large reads. Another best practice is to avoid using SELECT * FROM table if you can help it.



You may need to increase the physical RAM in the server, but that shouldn't be your first reaction.



(Read more here about PLE and NUMA nodes: http://www.sqlskills.com/blogs/paul/page-life-expectancy-isnt-what-you-think/)







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 13 '16 at 18:37









Randolph WestRandolph West

2,538215




2,538215













  • today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

    – shamim
    Dec 14 '16 at 13:09











  • Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

    – Randolph West
    Dec 21 '16 at 14:56



















  • today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

    – shamim
    Dec 14 '16 at 13:09











  • Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

    – Randolph West
    Dec 21 '16 at 14:56

















today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

– shamim
Dec 14 '16 at 13:09





today morning My PLE was super low and i found agent job was running since 3 hours and taking most of memory .after agent job done i count PLE value is 387 .why PLE runs high sometimes?@Randolph West

– shamim
Dec 14 '16 at 13:09













Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

– Randolph West
Dec 21 '16 at 14:56





Was the Agent Job related to index rebuilds? That will definitely do it. That's also expected behaviour, so once the job is done, and the PLE number climbs again, you're fine.

– Randolph West
Dec 21 '16 at 14:56


















draft saved

draft discarded




















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f158036%2fmy-ple-counter-value-is-483-what-is-the-safe-side-for-ple-buffer-manager-value%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Liste der Baudenkmale in Friedland (Mecklenburg)

Single-Malt-Whisky

Czorneboh