SQL Server Memory usage is high
Hello,
One of our production SQL cluster is eating up more memory on server.
Here are the server specifications :
OS : Windows 2008 R2 Enterprise
SQL : SQL Server 2008 SP2 standard edition ( 2 node cluster )
Memory : 16 GB ( 8 Gb to SQL and rest to OS )
CPU : 8
This server is heavily used by CLR and linked server events.
I have seen the memory usage of databases , it's not using more than 7 GB and leaving 1 GB free in sql memory area ( from our Idera SQL dm
monitoring tool ). I'm suspecting CLR events are causing these spikes.
When i look at the task manager sqlserver.exe is using 15.7 Gb ( close to 16 GB )
Not sure how to see which process are using the memory.
Also we are seeing the below error messages in error log very frequently
10/27/2014 15:23:52,spid1s,Unknown,AppDomain 85 (xxxxxx) is marked for unload due to memory pressure.
I have looked at some blogs in internet, i didnt get any correct info. I have seen this is kind of bug in SQL 2005 32-bit system but we are
using 64 bit system.
http://support.microsoft.com/kb/969962
Can anyone please help me on this ?
Thanks in advance
Continuation of DBCC memorystatus output
CACHESTORE_TEMPTABLES (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 40
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_NOTIF (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_VIEWDEFINITIONS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_XMLDBTYPE (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_XMLDBELEMENT (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_XMLDBATTRIBUTE (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_STACKFRAMES (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 8
(7 row(s) affected)
CACHESTORE_STACKFRAMES (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 8
(7 row(s) affected)
CACHESTORE_STACKFRAMES (Total) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 16
(7 row(s) affected)
CACHESTORE_BROKERTBLACS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 48
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERKEK (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERDSH (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERUSERCERTLOOKUP (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERRSB (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERREADONLY (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 32
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERTO (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_EVENTS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_CLRPROC (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 40
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_SYSTEMROWSET (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 1856
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_CONVPRI (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 48
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_FULLTEXTSTOPLIST (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 32
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SCHEMAMGR (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16432
MultiPage Allocator 856
(7 row(s) affected)
USERSTORE_DBMETADATA (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 5592
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_TOKENPERM (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 3856
MultiPage Allocator 3960
(7 row(s) affected)
USERSTORE_OBJPERM (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 2328
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SXC (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 656
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SXC (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SXC (Total) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 664
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LBSS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 128
MultiPage Allocator 608
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 2008
MultiPage Allocator 56
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 56
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (Total) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 2008
MultiPage Allocator 112
(7 row(s) affected)
OBJECTSTORE_SERVICE_BROKER (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 424
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (node 0) KB
VM Reserved 32768
VM Committed 32768
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 4048
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 24
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (Total) KB
VM Reserved 32768
VM Committed 32768
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 4072
MultiPage Allocator 0
(7 row(s) affected)
Buffer Pool Value
Committed 1024000
Target 1024000
Database 793462
Dirty 36258
In IO 0
Latched 0
Free 171398
Stolen 59140
Reserved 0
Visible 1024000
Stolen Potential 913660
Limiting Factor 17
Last OOM Factor 0
Last OS Error 0
Page Life Expectancy 262733
(15 row(s) affected)
Process/System Counts Value
Available Physical Memory 69021696
Available Virtual Memory 8762135273472
Available Paging File 12716019712
Working Set 15196917760
Percent of Committed Memory in WS 100
Page Faults 897824874
System physical memory high 0
System physical memory low 0
Process physical memory low 0
Process virtual memory low 0
(10 row(s) affected)
Procedure Cache Value
TotalProcs 4573
TotalPages 53712
InUsePages 27
(3 row(s) affected)
Global Memory Objects Pages
Resource 412
Locks 509
XDES 219
SETLS 8
SE Dataset Allocators 16
SubpDesc Allocators 8
SE SchemaManager 1169
SE Column Metadata Cache 991
SQLCache 893
Replication 2
ServerGlobal 52
XP Global 2
SortTables 3691
(13 row(s) affected)
Query Memory Objects (internal) Value
Grants 0
Waiting 0
Available 756700
Current Max 756700
Future Max 756700
Physical Max 756700
Next Request 0
Waiting For 0
Cost 0
Timeout 0
Wait Time 0
(11 row(s) affected)
Small Query Memory Objects (internal) Value
Grants 0
Waiting 0
Available 12800
Current Max 12800
Future Max 12800
(5 row(s) affected)
Optimization Queue (internal) Value
Overall Memory 6723993600
Target Memory 5965963264
Last Notification 1
Timeout 6
Early Termination Factor 5
(5 row(s) affected)
Small Gateway (internal) Value
Configured Units 32
Available Units 32
Acquires 0
Waiters 0
Threshold Factor 380000
Threshold 380000
(6 row(s) affected)
Medium Gateway (internal) Value
Configured Units 8
Available Units 8
Acquires 0
Waiters 0
Threshold Factor 12
Threshold -1
(6 row(s) affected)
Big Gateway (internal) Value
Configured Units 1
Available Units 1
Acquires 0
Waiters 0
Threshold Factor 8
Threshold -1
(6 row(s) affected)
Memory Pool Manager Pages
Reserved Current 0
Reserved Limit 913664
(2 row(s) affected)
Memory Pool (internal) Pages
Allocations 59136
Predicted 248311
Private Target 0
Private Limit 0
Total Target 972800
Total Limit 972800
OOM Count 0
(7 row(s) affected)
MEMORYBROKER_FOR_CACHE (internal) Pages
Allocations 55358
Rate 0
Target Allocations 779847
Future Allocations 0
Overall 820800
Last Notification 1
(6 row(s) affected)
MEMORYBROKER_FOR_STEAL (internal) Pages
Allocations 3778
Rate 0
Target Allocations 728267
Future Allocations 0
Overall 820800
Last Notification 1
(6 row(s) affected)
MEMORYBROKER_FOR_RESERVE (internal) Pages
Allocations 0
Rate 0
Target Allocations 820800
Future Allocations 189175
Overall 820800
Last Notification 1
(6 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Similar Messages
-
SQL Server Memory Usage Peaks to 95% and its not releasing SQL 2012
We are currently running SQL 2012 64 bit, Lock Pages Enabled, 128 GB. We allocated Max Memory 112000, Min Memory to 0. We have a SQL Maintenace Job which backs up (Full Backup) of our server around 11PM at that time the SQL Server memory peaks to almost
96% even during full business hours we are constantly in the range of 56 to 60% but after 11PM within 10 minutes of the job it peaks to 95 or 96 Percentage and even after the job completes it's not releasing the memory back. I have to manually shut the sql
service and then restart at that time it comes back to normal.
Any suggestions/any help really appreciated.Here are the details Memory is at 96% I still didn't restart...Please any help appreciated...The memory detals is for 24 hours I restarted the service around 11AM before I posted my previous message..
Memory Used by SqLServer: 119329
Locked Pages Used SQLServer : 105969
Total VAS in MB : 8388607
Process Physical Memory Low : 0
Process Virtual Memory Low : 0
Max Memory set to :112000
Out of 128 Memory Last 24 hours the memory usage in %
Percent Memory Used - Total Memory is 128.0 GB
Last 24 Hours
DATE / TIME
Memory Used
19-Dec-14
11:46 PM
96.24659602
20-Dec-14
12:46 AM
96.24578349
20-Dec-14
1:46 AM
96.25146739
20-Dec-14
2:46 AM
96.24345652
20-Dec-14
3:46 AM
96.27311834
20-Dec-14
4:46 AM
96.28947067
20-Dec-14
5:46 AM
96.18931325
20-Dec-14
6:46 AM
96.09323502
20-Dec-14
7:46 AM
96.07915497
20-Dec-14
8:46 AM
96.07906977
20-Dec-14
9:46 AM
96.0784111
20-Dec-14
10:46 AM
96.07415009
20-Dec-14
11:46 AM
26.03422141
20-Dec-14
12:46 PM
33.57474359
20-Dec-14
1:46 PM
39.466561
20-Dec-14
2:46 PM
41.85940742
20-Dec-14
3:46 PM
43.89071274
20-Dec-14
4:46 PM
45.80877368
20-Dec-14
5:46 PM
46.49493281
20-Dec-14
6:46 PM
46.68486468
20-Dec-14
7:46 PM
46.69701958
20-Dec-14
8:46 PM
46.69994736
20-Dec-14
9:46 PM
57.5012455
20-Dec-14
10:46 PM
96.25695419
I verified its a sqL job and still my memory is 95%
It peaeked at 10:46PM and here are the details of the SQL job which started at 10:30
Progress: 2014-12-20 22:30:04.39
Source: Check Database Integrity Task Executing query "USE [DATASTORE] ".: 50% complete End Progress Progress: 2014-12-20 22:43:06.10
Source: Check Database Integrity Task Executing query "DBCC CHECKDB(N'DATASTORE') WITH NO_INFOMSGS ".: 100% complete End Progress
Progress: 2014-12-20 22:43:06.11 Source: Check Database Integrity Task Executing query "USE [ETL_Proc] ".: 50% complete
End Progress Progress: 2014-12-20 22:46:52.56 Source: Check Database Integrity Task Executing query "DBCC CHECKDB(N'ETL_Proc')
WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 20% complete End Progress
Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".
: 40% complete End Progress Progress: 2014-12-20 22:46:52.64
Source: Back Up Database Task Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 60% complete
End Progress Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 80% complete End Progress
Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 100% complete End Progress
Progress: 2014-12-20 22:46:55.63 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ReportServer] TO DISK = N'P:\SQL...".: 100% complete
End Progress Progress: 2014-12-20 22:46:56.55 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ReportServerTempDB] TO DISK = N'...".: 100% complete End Progress Progress: 2014-12-20 22:46:57.35
Source: Back Up Database Task Executing query "BACKUP DATABASE [dbamaint] TO DISK = N'P:\SQL_Bac...".: 100% complete End Progress
Progress: 2014-12-20 22:51:13.08 Source: Back Up Database Task
Executing query "BACKUP DATABASE [DATASTORE] TO DISK = N'P:\SQL_Ba...".: 100% complete End Progress
Progress: 2014-12-20 22:51:52.72 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ETL_Proc] TO DISK = N'P:\SQL_Bac...".: 100% complete End Progress Progress: 2014-12-20 22:51:54.87
Source: Rebuild Index Task Executing query "USE [ReportServer] ".: 0% complete End Progress Progress:
2014-12-20 22:51:54.88 Source: Rebuild Index Task Executing query "ALT... The package executed successf... The step succeeded. -
Hi,
How to find out the current utilization of Ram in sql server? and how to restrict the ram for sql server windows 2008r2 with 64bit os?Hi,
How to find out the current utilization of Ram in sql server? and how to restrict the ram for sql server windows 2008r2 with 64bit os?
Hi,
Below query will give you memory utilized by SQL server
select
(physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
(locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
(total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
process_physical_memory_low,
process_virtual_memory_low
from sys. dm_os_process_memory
You can restrict only buffer pool by putting limit on MAX Server memory using below query
sp_configure 'show advanced options' ,1
go
reconfigure
go
sp_configure 'max server memory MB',xxx --value you want to put
go
reconfigure
Please note that even if yu put cap on max server memory still SQL server can consume more memory that max limit and this memory will be direct memory allocation done by windows for features like SQLCLR,XML,Stack threads, Linked servers.
More details
http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Hi All,
I am not sure if this is a fair ask or no but this is something i want to learn much internals about sql server memory and how sql server responds to memory pressure and i wanted to see that practically.
Environment : windows 2003, 4 GB physical RAM, SQL server 2005 sp4.
Checking in if someone has some demo tsql scripts which can blow up memory so that i can setup the memory counters and monitor sql server memory usage.
Did anyone has done this earlier?
Thanks in advance.Why do I see “A significant part of sql server process memory has been paged out. This may result in performance degradation.” By SQL Server In spite of having above mechanism to detect the system level memory pressure and scale
SQL Server memory?
There are couple of situations where SQL Server Process working set might be paged out by Windows despite these memory resource notification mechanism.
1.If windows is not sending the correct notifications to all listening processes at the right moment and thresholds
2.If SQL Server is not responding fast enough to the low memory resource notification from Windows
3.Conditions in Windows where working sets of all processes are trimmed
4.Windows might decide to trim a certain percentage of working set of various or specific processes
Above is from
A significant part of SQL Server process memory has been paged out.
Please use Marked as Answer if my post solved your problem and use
Vote As Helpful, if a post was useful to help other user's find a solution quicker. -
Hi Experts,
Can anyone please tell me how can we check SQL server memory usages?
Thanks in AdvanceHi Experts,
Can anyone please tell me how can we check SQL server memory usages?
Thanks in Advance
Can use Perfmon.DMV is the best.Will work for 2008 and above
select
(physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
(locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
(total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
process_physical_memory_low,
process_virtual_memory_low
from sys. dm_os_process_memory
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
SQL 2012 Memory usage analysis
We have this clustered SQL Server, win 2008 R2 + SQL 2012 Standard SP2,
Server RAM is 64GB, maximum memory is set at 50GB, and minimum memory is set at 10GB.
When I check memory usage, it seems
CLR takes more memory than Buffer Pool, is it normal? Or does it show memory allocation issue? Thanks a lot!
The "total server memory" and "target server memory" performance counters are both 50GB.
Please kindly see below screen shots below:Hi Vivian,
I would assume you are asking question related to SQL Server 2012 memory the whole discussion would change if it is SQL Server 2008 r2 memory
You are not drawing correct information from first query.
CLR has Reserved 6 G but ONLY committed 12 MB. And that too you are looking at virtual memory which is 6TB for SQL Server process so of course CLR can reserve there is actually no issue with it. A committed memory is actually what SQL Server is using
reserved in simple language is what SQL Server thinks it might need in near future.
As you said Target and total memory are same its good.
For both 2012 and 2008 r2 below query will give total memory utilization by SQL Server instance
select
(physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
(locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
(total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
process_physical_memory_low,
process_virtual_memory_low
from sys. dm_os_process_memory
If you want to see Breakdown of memory utilized by various clerks in 2008 r2
select
type,
(SUM(single_pages_kb)/1024) Single_page_allocator_memory,
(SUM(multi_pages_kb)/1024) multi_page_allocator_memory,
(sum(awe_allocated_kb)/1024) [AWE API memory]
from sys.dm_os_memory_clerks
group by type
order by Single_page_allocator_memory desc
For 2012
select type,
(SUM(pages_kb)/1024) as Memory_Utilized
(sum(awe_allocated_kb)/1024) as Memory Allocated by AWE API
from
sys.dm_os_memory_clerks
group by type
order by Memory_Utilized desc
Starting from 2012 Max server memory controls much more than buffer pool
Max server memory controls SQL Server memory allocation, including the buffer pool, compile memory, all caches, qe memory grants, lock manager memory, and CLR memory (basically any “clerk” as found in dm_os_memory_clerks). Memory for thread stacks, heaps,
linked server providers other than SQL Server, or any memory allocated by a “non SQL Server” DLL is not controlled by max server memory
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
JVM performance in case of JVM memory usage is high
Hi All
Here is some query about JVM performance in case of JVM memory usage is high.
I have a server of 16GB. For JVM 12GB and for OS 4GB.
Let say, My Application creating many Unnecessary Objects and consumes very high memory.
Also, there is a gaurenty that limit of memory is it never exceed 2GB.
No, in worst scenario memory used by JVM is 2GB.Ok.
I have free memory available for JVM is 10GB(16GB - 2GB - 4GB(any OS memory usage)).
Now, for any Application processing I have 10GB.
So, does it affect application processing for which I have 10GB.
I mean does JVM performance decreses in high JVM memory usage even I have occupied more memory to JVM.Hi All
Here is some query about JVM performance in case of JVM memory usage is high.
I have a server of 16GB. For JVM 12GB and for OS 4GB.
Let say, My Application creating many Unnecessary Objects and consumes very high memory.
Also, there is a gaurenty that limit of memory is it never exceed 2GB.
No, in worst scenario memory used by JVM is 2GB.Ok.
I have free memory available for JVM is 10GB(16GB - 2GB - 4GB(any OS memory usage)).
Now, for any Application processing I have 10GB.
So, does it affect application processing for which I have 10GB.
I mean does JVM performance decreses in high JVM memory usage even I have occupied more memory to JVM. -
What is difference between 32 bit and 64 bit sql server memory management
What is difference between 32 bit and 64 bit sql server memory management
Thanks
ShashikalaThis is the basic difference...check if helps:
A 32-bit CPU running 32-bit software (also known as the x86 platform) is so named because it is based on an architecture that can manipulate values that are up to 32 bits in length. This means that a 32-bit memory pointer can store a value between 0 and
4,294,967,295 to reference a memory address. This equates to a maximum addressable space of 4GB on 32-bit platforms
On the other hand 64-bit limit of 18,446,744,073,709,551,616, this number is so large that in memory/storage terminology it equates to 16 exabytes. You don’t come across that term very often, so to help understand the scale, here is the value converted to
more commonly used measurements: 16 exabytes = 16,777,216 petabytes (16 million PB)➤ 17,179,869,184 terabytes (17 billion TB)➤ 17,592,186,044,416 gigabytes (17 trillion GB)➤
As you can see, it is significantly larger than the 4GB virtual address space usable in 32-bit systems; it’s so large in fact that any hardware capable of using it all is sadly restricted to the realm of science fiction. Because of this, processor manufacturers
decided to only implement a 44-bit address bus, which provides a virtual address space on 64-bit systems of 16TB. This was regarded as being more than enough address space for the foreseeable future and logically it’s split into an 8TB range for user mode
and 8TB for kernel mode. Each 64-bit process running on an x64 platform will be able to address up to 8TB of VAS.
Please click the Mark as answer button and vote as helpful if this reply solves your problem -
SQL Server memory Configuration - SCOM 2012 R2
Hi,
The following article http://technet.microsoft.com/en-us/library/gg682077#BKMK_SupConfigSQLDBconfig states the following about SQL Server memory configuration for SCCM:
When you use a database server that is co-located with the site server, limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory.
When you use a dedicated SQL Server, limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory.
The question is:
Is there any advice (from technet articles) about SQL Server memory configuration for SCOM 2012 R2?
Thanks in advance!Hi There,
Read the 5th point below
General SQL Server recommendations for System Center 2012 R2
This information describes general recommendations for SQL Server regardless of what System Center component you are deploying.
You will need a minimum of four computers to deploy all System Center components. Aside from performance reasons, not all system components can coexist on the same computer. For more information, see Component
Coexistence for System Center 2012 R2.
For testing purposes only, one SQL Database Engine Services instance may be used for all components, but is not recommended in a production setting due to performance concerns.
Reporting Services instances cannot be shared between System Center components.
SQL_* collations are being deprecated for their Windows equivalents.
Limit the memory of each SQL Server instance such that the Total Memory setting allows a minimum of 1 GB (2GB preferred) of free memory after all services are running.
System Center components requiring the most disk resources are Service Manager, Operations Manager and Configuration Manager.
Disks used should be formatted to a 64K allocation unit size.
Disks used should be configured to allow 20% free space after all calculations for monitoring. Set growth upper limits to not exceed this space limit.
Pre-sizing is preferred - use auto-grow if needed as it uses more resources.
Set Pre-size to 8GB/2GB as a minimum. 20-30% of the database file size is a rule of thumb.
Set Auto-grow to 500/100 as a minimum.
Refer: http://technet.microsoft.com/en-in/library/dn281933.aspx
Gautam.75801 -
SQL server 2012 service consume high memory
Hi,
I have sql 2012 SP1 installed on my windows server 2012. Have 128 GB ram installed on server.
Now sql server consuming 111GB of ram. Memory set in sql is 120 GB.
No page file set for server.
How to manage sql not to consume to much of ram.
Please suggest as system getting to much slow.
Thanks in Advance
Anuj GuptaHi,
I have sql 2012 SP1 installed on my windows server 2012. Have 128 GB ram installed on server.
Now sql server consuming 111GB of ram. Memory set in sql is 120 GB.
No page file set for server.
How to manage sql not to consume to much of ram.
Please suggest as system getting to much slow.
Thanks in Advance
Anuj Gupta
Rest assured buddy this is not an issue and best part is if OS faces memory crunch anyhow SQL Server will release memory it has taken,will trim down its consumption .So its totally normal behaviour.If you really want to decrease memory consumption set lower
valur for MAX SERVER MEMORY.But will not advise you to do so as it will flush out cache and other plans.
You should set a page file almost double the RAM you have I guess that is the value they recommned.
Sometimes if you have big databse ( 500 G -1 TB)and lots of pages are read memory utilization rises to keep this pages in Buffer cache and it seems SQL Server is utilizing more mmeory but it is doing for your own good to make query faster .Any read/write
would be satisfied from memory instead of bringing data from disk which is costly
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Help me understanding server memory usage
I am trying to determine how much memory our weblogic server needs and
am seeing what seems to me to be strange memory growth patterns in the
server. I am running weblogic6.1sp4(with CR093850) on solaris 2.7.
I have written an emulator for testing performance and stability of
our system. The emulator has sleeps in it between actions so it is
emulating a real end user interaction with the system, it is not
trying to emulate a super heavy load.
I configured weblogic server to have a high max heap to begin with(1.5
gig) and thought I could turn 10 emulators on and let them run for a
while to get all my entity bean cached filled up, then I could see
what the size of my server was at that point and expect that to be
close to what it will need. Is this an appropriate way to determine
size?
However, when I do this and try to let my emulators run for 24 hours,
I never make it past 13 hours. The weblogic server never stops
growing and of course I eventually end up with all the emulators
exiting with 'out of memory' errors from the server.
The process grows slowly at first, even seems pretty well behaved for
the first 2-4 hours. Then the process size starts to grow a little
more rapidly, then there is some drastic up and downs then eventually
it just stays high. During the spikes the CPU usage spikes as well
even though the load from my emulators has not increased.
If our code had a small memory leak I would expect to see a steady,
constant slow growth problem, but that is not whats happening, it
starts out small growth but then becomes more spiky.
I have max-beans-in-cache and max-beans-in-free-pool said reasonably
low on my entity beans that are used in this test. There are only 8
entity bean types being used in this test run. 1 stateful session
bean type and 3 stateless session beans.
Has anyone else seen this odd behavior? Has anyone had success in
setting a reasonable heap size?
any insight would be greatly appreciated!
KellyHi Kelly,
That looks pretty much like a memory leak. You could use a memory
profiler like OptimizeIt, or at least search though the code for
appearances of static public Hashtable
- that's where ever-growing "caches" live.
Regards,
Slava Imeshev
"Kelly Kingdon" <[email protected]> wrote in message
news:[email protected]...
I am trying to determine how much memory our weblogic server needs and
am seeing what seems to me to be strange memory growth patterns in the
server. I am running weblogic6.1sp4(with CR093850) on solaris 2.7.
I have written an emulator for testing performance and stability of
our system. The emulator has sleeps in it between actions so it is
emulating a real end user interaction with the system, it is not
trying to emulate a super heavy load.
I configured weblogic server to have a high max heap to begin with(1.5
gig) and thought I could turn 10 emulators on and let them run for a
while to get all my entity bean cached filled up, then I could see
what the size of my server was at that point and expect that to be
close to what it will need. Is this an appropriate way to determine
size?
However, when I do this and try to let my emulators run for 24 hours,
I never make it past 13 hours. The weblogic server never stops
growing and of course I eventually end up with all the emulators
exiting with 'out of memory' errors from the server.
The process grows slowly at first, even seems pretty well behaved for
the first 2-4 hours. Then the process size starts to grow a little
more rapidly, then there is some drastic up and downs then eventually
it just stays high. During the spikes the CPU usage spikes as well
even though the load from my emulators has not increased.
If our code had a small memory leak I would expect to see a steady,
constant slow growth problem, but that is not whats happening, it
starts out small growth but then becomes more spiky.
I have max-beans-in-cache and max-beans-in-free-pool said reasonably
low on my entity beans that are used in this test. There are only 8
entity bean types being used in this test run. 1 stateful session
bean type and 3 stateless session beans.
Has anyone else seen this odd behavior? Has anyone had success in
setting a reasonable heap size?
any insight would be greatly appreciated!
Kelly -
Hi,
We have a core sql database server, which have 256 GB physical memory ,and give maximum physical memory to sql server 240000 MB, sql server service startup account has locked memory privilege.
We found that the free memory is 12094108 KB,but the Page Life Expectancy counter is low,about 300.
Does anybody give some advice why sql server don't (or can't) use free memory, and how to find which parts inside sql server took up these free memory?
Many thanks.
SQL Server Version:
Microsoft SQL Server 2012 - 11.0.5532.0 (X64)
Jul 14 2014 15:00:27
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
And this is a clustered sql instance and as a primary node of ag.
Attachments are some dmv results.logdate processinfo
text
2014/9/12 3:10 AM Server
Microsoft SQL Server 2012 - 11.0.5532.0 (X64)
Jul 14 2014 15:00:27
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2014/9/12 3:10 AM Server
(c) Microsoft Corporation.
2014/9/12 3:10 AM Server
All rights reserved.
2014/9/12 3:10 AM Server
Server process ID is 9692.
2014/9/12 3:10 AM Server
"System Manufacturer: 'HP', System Model: 'ProLiant DL980 G7'."
2014/9/12 3:10 AM Server
Authentication mode is MIXED.
2014/9/12 3:10 AM Server
Logging SQL Server messages in file 'X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\Log\ERRORLOG'.
2014/9/12 3:10 AM Server
The service account is 'XX\SQLAccount'. This is an informational message; no user action is required.
2014/9/12 3:10 AM Server
Registry startup parameters:
-d X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\DATA\master.mdf
-e X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\Log\ERRORLOG
-l X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\DATA\mastlog.ldf
2014/9/12 3:10 AM Server
Command Line Startup Parameters:" -s ""SQLInstance"""
2014/9/12 3:10 AM Server
"SQL Server detected 8 sockets with 8 cores per socket and 16 logical processors per socket, 128 total logical processors; using 128 logical processors based on SQL Server licensing. This is an informational message; no user action is required."
2014/9/12 3:10 AM Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Detected 262133 MB of RAM. This is an informational message; no user action is required.
2014/9/12 3:10 AM Server
Using locked pages in the memory manager.
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
This instance of SQL Server last reported using a process ID of 13236 at 2014/9/12 3:09:42 (local) 2014/9/11 19:09:42 (UTC). This is an informational message only; no user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 1: CPU mask: 0x00000000ffff0000:0 Active CPU mask: 0x00000000ffff0000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 2: CPU mask: 0x000000000000ffff:1 Active CPU mask: 0x000000000000ffff:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 3: CPU mask: 0x00000000ffff0000:1 Active CPU mask: 0x00000000ffff0000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 4: CPU mask: 0x0000ffff00000000:0 Active CPU mask: 0x0000ffff00000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 5: CPU mask: 0xffff000000000000:0 Active CPU mask: 0xffff000000000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 6: CPU mask: 0x0000ffff00000000:1 Active CPU mask: 0x0000ffff00000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 7: CPU mask: 0xffff000000000000:1 Active CPU mask: 0xffff000000000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Lock partitioning is enabled. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Software Usage Metrics is disabled.
2014/9/12 3:10 AM spid21s
Starting up database 'master'.
2014/9/12 3:10 AM Server
CLR version v4.0.30319 loaded.
2014/9/12 3:10 AM spid21s
Resource governor reconfiguration succeeded.
2014/9/12 3:10 AM spid21s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014/9/12 3:10 AM spid21s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014/9/12 3:10 AM spid21s
"SQL Trace ID 1 was started by login ""sa""."
2014/9/12 3:10 AM Server
Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2014/9/12 3:10 AM spid21s
Server name is 'CLSSQLInstance\SQLInstance'. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid21s
The NETBIOS name of the local node that is running the server is 'SVRXXXXHP980'. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid27s
A self-generated certificate was successfully loaded for encryption.
2014/9/12 3:10 AM spid27s
Server is listening on [X.X.X.X <ipv4> 1433].
2014/9/12 3:10 AM spid27s
Server is listening on [ X.X.X.X <ipv4> 1433].
2014/9/12 3:10 AM spid27s
Started listening on virtual network name 'ClsSQLInstance'. No user action is required.
2014/9/12 3:10 AM spid28s
A new instance of the full-text filter daemon host process has been successfully started.
2014/9/12 3:10 AM spid27s
Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
2014/9/12 3:10 AM spid27s
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLInstance].
2014/9/12 3:10 AM spid27s
Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\ClsSQlInstance\MSSQL$SQLInstance\sql\query ].
2014/9/12 3:10 AM spid21s
Database mirroring has been enabled on this instance of SQL Server.
2014/9/12 3:10 AM spid32s
AlwaysOn: The availability replica manager is starting. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid23s
Starting up database 'mssqlsystemresource'.
2014/9/12 3:10 AM spid33s
Starting up database 'msdb'.
2014/9/12 3:10 AM spid36s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid41s
Starting up database 'CXXDB'.
2014/9/12 3:10 AM spid38s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid42s
Starting up database 'XXbDB'.
2014/9/12 3:10 AM spid37s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid23s
The resource database build version is 11.00.5532. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid41s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid41s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid36s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid36s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid37s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid42s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid39s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid38s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid38s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid23s
Starting up database 'model'.
2014/9/12 3:10 AM Server
Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
2014/9/12 3:10 AM Server
Dedicated admin connection support was established for listening remotely on port 58313.
2014/9/12 3:10 AM spid27s
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014/9/12 3:10 AM Server
SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn: The local replica of availability group 'AGGroup' is starting. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
"The state of the local availability replica in availability group 'AGGroup' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For
more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
2014/9/12 3:10 AM Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ XXXX] for the SQL Server service.
2014/9/12 3:10 AM Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ xxxx ] for the SQL Server service.
2014/9/12 3:10 AM spid23s
Clearing tempdb database.
2014/9/12 3:10 AM spid23s
Starting up database 'tempdb'.
2014/9/12 3:10 AM spid53
AlwaysOn: The local replica of availability group 'AGGroup' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid53
"The state of the local availability replica in availability group 'AGGroup' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error.
For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
2014/9/12 3:10 AM Server
"The state of the local availability replica in availability group 'AGGroup' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For
more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
2014/9/12 3:10 AM spid42s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid39s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid36s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid41s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid37s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
383 transactions rolled forward in database 'XXDB' (10:0). This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid48s
0 transactions rolled back in database 'XXDB' (10:0). This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
CHECKDB for database 'XXDB' finished without errors on 2011-07-27 00:25:13.070 (local time). This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid49s
Server is listening on [ X.X.X.X <ipv4> 5022].
2014/9/12 3:10 AM spid49s
Server is listening on [X.X.X.X <ipv4> 5022].
2014/9/12 3:10 AM spid49s
Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
2014/9/12 3:10 AM spid49s
The Database Mirroring endpoint is now listening for connections.
2014/9/12 3:10 AM spid49s
Service Broker manager has started.
2014/9/12 3:10 AM spid21s
Launched startup procedure 'sp_MSrepl_startup'.
2014/9/12 3:10 AM spid36s
CHECKDB for database 'XXDB' finished without errors on 2011-07-27 00:25:50.283 (local time). This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid42s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [C5253E8A-298A-45D8-9568-1184EC4CC3A4] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid41s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [76DBB6D1-8A06-44DC-9357-6ACCC9AE00B7] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [AB354017-E987-4B96-853E-6C292C9011BD] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid190
Failed to verify Authenticode signature on DLL 'D:\Program Files\Microsoft SQL Server\MSSQL11.SQLInstance\MSSQL\Binn\msxmlsql.dll'.
2014/9/12 3:10 AM spid39s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid47s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [6752FE19-1AEC-4DB6-AC63-2F8A6A2E67C8] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid47s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid47s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid247s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid247s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid257s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid257s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid275s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid303s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid303s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid303s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid275s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid347s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid362s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid362s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid362s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid347s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid364s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid427
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid427
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid347s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid53
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014/9/12 3:10 AM spid565
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid565
Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid565
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid565
Using 'xplog70.dll' version '2011.110.5058' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid605
"SQL Trace ID 2 was started by login ""XX\SQLAccount""."
2014/9/12 3:11 AM spid701
"SQL Trace ID 3 was started by login ""XX\SQLAccount""."
2014/9/12 3:11 AM spid701
SQL Trace stopped. Trace ID = '3'. Login Name = 'XX\SQLAccount'.
2014/9/12 3:11 AM spid360s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:11 AM spid360s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required. -
SQL Server, RAM Usage, Networking Admin
We have a VM Guest configured as follows: dedicated Sql 2008 Sp3 (x64) running on Windows 2008 R2 x64, 32GB RAM. Per Task Manager (if it is to be believed) the sql server process has allocated 20GB of RAM. The Networking Manager says
that sql grabs every bit of memory you give it. He has a hard time believing that sql really needs that much memory.
a. I pointed out that we can cap the (buffer pool) memory and that sql, while reserving it, will not use the RAM unless it is actually needed. (In other words, that 20GB was needed at one point in time).
b. I also pointed out that sql is not too quick to return the memory even it is no longer needed.
c. I look for hard page faults on the server as an initial indication that RAM may be taxed.
d. I told him there is no easy way to estimate the amount of RAM that a given sql server needs
In your opinion, are the statements a-d relatively factual or way off base?
TIA,
edm2
P.S. Recently he indicated that if we raise the Sql RAM limit on a box then Sql will take it all and, despite, what is commonly said, large amounts of RAM costs lots of money. Let us say this matter has been a point of contention between us for
some time and we are still on opposite sides of the railroad track.Hello,
Per Task Manager (if it is to be believed) the sql server process has allocated 20GB of RAM. The Networking Manager says that sql grabs every bit of memory you give it. He has a hard time believing that sql really needs that much memory.
You're correct, don't trust task manager. If the server is not configured (max server memory) then yes, SQL Server will gobble up all available memory if it needs to (it on allocates memory if it already doesn't have room).
a. I pointed out that we can cap the (buffer pool) memory and that sql, while reserving it, will not use the RAM unless it is actually needed. (In other words, that 20GB was needed at one point in time).
You sir are 100% correct!
b. I also pointed out that sql is not too quick to return the memory even it is no longer needed.
Yes and no. SQL Server can and will respond to the windows low memory flag and give back memory if possible (for example, it won't give it back if using locked pages in memory [LPIM]). Low memory is different in versions of windows but it's always around
100 MB which IMHO is way too late. Couple that with the fact it's a VM and it's memory could already be paged out by the host and no one would ever know means a crash could happen.
c. I look for hard page faults on the server as an initial indication that RAM may be taxed.
That would be true for a physical system. While it still sort of is true for a VM, we have no way of knowing if the host has that memory paged which would also cause issues (slowness, etc). Still doesn't hurt to watch though :)
d. I told him there is no easy way to estimate the amount of RAM that a given sql server needs
SQL Server will always happily take as much memory as you give it, to a point. If at one point it used 20 GB that's a good start. SQL Server wants everything to be in memory, because that has the fastest access time. So take into account the sizes of your
databases, any CLR or items that run outside of the database (or are hosted), all of the queries that want to live in cache as well so they only have to be compiled once, etc.
In your opinion, are the statements a-d relatively factual or way off base?
See above :)
P.S. Recently he indicated that if we raise the Sql RAM limit on a box then Sql will take it all and, despite, what is commonly said, large amounts of RAM costs lots of money. Let us say this matter has been a point of contention between us for
some time and we are still on opposite sides of the railroad track.
I feel you. Things to look for inside of SQL Server for memory pressure are lazy writes/second, free list stalls, a large increase in general IO of the server (could just mean the workload changed, tbh), etc. Also, depending on how the Guest is setup and
the Host is configured will have a lot to do with performance. For example, if the guest can cross numa nodes and ends up accessing tons of foreign memory, if dynamic memory for the guest is used and constantly swapped. None of those will manifest itself in
the counters but will surely have a negative impact on SQL Server.
So, to be fair to you, you're correct in that (Depending on how the Host/Guest is configured) adding more RAM may or may not help (or make things worse if the memory is all paged on the host). To be fair to him, SQL Server on a physical box magically makes
things run faster since they'll mostly be in memory.
Sean Gallardy | Blog |
Twitter -
Microsoft Jdbc driver for SQL Server memory leak
I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
Appreciate your helpI'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
Appreciate your help -
SQL Server Memory And Di Object
Hello Experts
I'm doing a loop which use some DI Objects. This loop occurs more than 80 000 times.
In this loop I manage a BusinessPartner Di Object like that
private static SAPBobsCom.BusinessPartners myPartners;
while(...)
myPartners = (SAPBobsCom.BusinessPartners)Di.GetBusinessObject(oBusinessPrtners);
myPartners.GetbyKey(...)
//treatments
//Sometimes
myPartner.Add()
myPartner.Update()
//Always
System.runtime.....releaseComObject(myPartner)
GC.Collect();
GC.WaitForPendingFinalizers();
It works fine but the sqlServer Process take more and more Memory and arrive to 1 200 mb RAM.
I have to re-start the SQL Server Service to erase memory, no DBCC query work.
have you any Idea to stop this memory grow ?
Thanks a lot for Ideas...Hi Julien,
The amount of memory that SQL Server takes should level out. When you run an intensive process the memory manager will start taking chunks of memory to boost performance. Typically it won't release this memory unless the server is low on physical memory and another application requires more memory. However, when you next run the process, SQL will use up the RAM that is already available to it before requesting more. This should mean that your process will not take any significant extra memory next time it is run (assuming the same workload at the time).
SQL will typically only have a 100MB footprint when it has just been started. On a production system, I would expect to see 1-2GB of memory being used by SQL on an average SBO site (more for larger sites and more if the client uses large XL Reporter reports or query intensive addons like Fixed Assets).
Although SQL Server 2000 was a little prone to leaking memory, I have not known this to be the case in SQL 2005.
Have you tested running your script twice in a row?
Kind Regards,
Owen
Maybe you are looking for
-
I create a RFC Receiver CC, I got the following trace error in XSMB_MONI in receiver call adapter phase： - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP"> <Trace level="2" type="T">old values in cache (no lock found) - start r
-
Can we let Macpro Firewire out the 3rd display?
My mac pro has only 1 graphcis card and its connected to 2 display monitor. I also have a firewire video output that I can choose output the video via firewire in Logic Pro. I don't know if we can just let mac pro output the video via firewire in all
-
Dear All , I need to post undelivery cost for a single PO and i receive the invoice after final delivery . How can i enter the following unplanned delivery costs for this PO ? Thanks Dash
-
Hello, We have the topology in Attachement. and we have problem with SVI and VPC The configuration: N5K1: vpc domain 100 peer-switch role priority 100 system-priority 1024 peer-keepalive destination 192.168.21.1 peer-config-check-bypass d
-
RequestFocus() work only once? why???
i have a JDialog called setting. When user press a button, setting is showed with this code. setting.setCenter(); setting.focusFirstBlank(); setting.setVisible(true); which focusFirstBlank() is public void focusFirstBlank(){ if(Smtp.getText().trim().