Hi ,
I am testing AG in Sql Server 2016.
1 Primary+2 Secondary (HA+DR).
Failover AG's are working fine with in HA but failing while failover to DR.
I verified that NT AUTHORITY Having sufficient permissions and having proper DNS Prefix.
Still getting issue.
Hi All.
I am trying t troubleshoot a pending memory issue, I have the result of the dbcc memorystatus but unsure of what to look out for which is a red flag. Any help would be appreciated on what to look out for within the result.
Process/System Counts Value ---------------------------------------- -------------------- Available Physical Memory 675840000 Available Virtual Memory 140699899572224 Available Paging File 2910547968 Working Set 13029924864 Percent of Committed Memory in WS 100 Page Faults 28557579 System physical memory high 0 System physical memory low 0 Process physical memory low 1 Process virtual memory low 0 (10 row(s) affected) Memory Manager KB ---------------------------------------- ----------- VM Reserved 36220988 VM Committed 12722268 Locked Pages Allocated 0 Large Pages Allocated 0 Emergency Memory 1024 Emergency Memory In Use 32 Target Committed 12722272 Current Committed 12722272 Pages Allocated 12200128 Pages Reserved 960 Pages Free 33552 Pages In Use 8260712 Page Alloc Potential 6463376 NUMA Growth Phase 2 Last OOM Factor 0 Last OS Error 0 (16 row(s) affected) Memory node Id = 0 KB ---------------------------------------- ----------- VM Reserved 36220924 VM Committed 12722248 Locked Pages Allocated 0 Pages Allocated 12200128 Pages Free 33552 Target Committed 12722248 Current Committed 12722248 Foreign Committed 0 Away Committed 0 Taken Away Committed 0 (10 row(s) affected) Memory node Id = 64 KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 20 Locked Pages Allocated 0 (3 row(s) affected) MEMORYCLERK_SQLGENERAL (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8600 (6 row(s) affected) MEMORYCLERK_SQLBUFFERPOOL (node 0) KB ---------------------------------------- ----------- VM Reserved 13014908 VM Committed 369804 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 4425824 (6 row(s) affected) MEMORYCLERK_SQLQUERYEXEC (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 64 (6 row(s) affected) MEMORYCLERK_SQLOPTIMIZER (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 992 (6 row(s) affected) MEMORYCLERK_QUERYDISKSTORE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 200 (6 row(s) affected) MEMORYCLERK_SQLUTILITIES (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 240 (6 row(s) affected) MEMORYCLERK_SQLSTORENG (node 0) KB ---------------------------------------- ----------- VM Reserved 1664 VM Committed 1664 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8608 (6 row(s) affected) MEMORYCLERK_SQLCONNECTIONPOOL (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 1464 (6 row(s) affected) MEMORYCLERK_SQLCLR (node 0) KB ---------------------------------------- ----------- VM Reserved 6300288 VM Committed 6768 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 11232 (6 row(s) affected) MEMORYCLERK_SQLSERVICEBROKER (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 448 (6 row(s) affected) MEMORYCLERK_SQLHTTP (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) MEMORYCLERK_SNI (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 48 (6 row(s) affected) MEMORYCLERK_SNI (node 64) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) MEMORYCLERK_SNI (Total) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 64 (6 row(s) affected) MEMORYCLERK_FULLTEXT (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 296 (6 row(s) affected) MEMORYCLERK_SQLXP (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) MEMORYCLERK_BHF (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 288 (6 row(s) affected) MEMORYCLERK_SQLQERESERVATIONS (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 1024 (6 row(s) affected) MEMORYCLERK_XE_BUFFER (node 0) KB ---------------------------------------- ----------- VM Reserved 13056 VM Committed 13056 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 0 (6 row(s) affected) MEMORYCLERK_XTP (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 1600 (6 row(s) affected) MEMORYCLERK_HOST (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 24 (6 row(s) affected) MEMORYCLERK_SOSNODE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 34888 (6 row(s) affected) MEMORYCLERK_SOSNODE (node 64) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 2432 (6 row(s) affected) MEMORYCLERK_SOSNODE (Total) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 37320 (6 row(s) affected) MEMORYCLERK_SOSOS (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 192 (6 row(s) affected) MEMORYCLERK_SOSMEMMANAGER (node 0) KB ---------------------------------------- ----------- VM Reserved 29824 VM Committed 29672 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 0 (6 row(s) affected) MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (node 0) KB ---------------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 232 (6 row(s) affected) MEMORYCLERK_FSAGENT (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) MEMORYCLERK_FILETABLE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) MEMORYCLERK_XE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 7008 (6 row(s) affected) MEMORYCLERK_HADR (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 248 (6 row(s) affected) MEMORYCLERK_SQLLOGPOOL (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 2616 (6 row(s) affected) MEMORYCLERK_LWC (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 32 (6 row(s) affected) MEMORYCLERK_FSCHUNKER (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 48 (6 row(s) affected) CACHESTORE_OBJCP (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_SQLCP (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 6272 (6 row(s) affected) CACHESTORE_PHDR (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 3744 (6 row(s) affected) CACHESTORE_XPROC (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_TEMPTABLES (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_NOTIF (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_VIEWDEFINITIONS (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_XMLDBTYPE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_XMLDBELEMENT (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_XMLDBATTRIBUTE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_STACKFRAMES (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_STACKFRAMES (node 64) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_STACKFRAMES (Total) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_BROKERTBLACS (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 48 (6 row(s) affected) CACHESTORE_BROKERKEK (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_BROKERDSH (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_BROKERUSERCERTLOOKUP (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_BROKERRSB (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_BROKERREADONLY (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 32 (6 row(s) affected) CACHESTORE_BROKERTO (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) CACHESTORE_EVENTS (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_SEHOBTCOLUMNATTRIBUTE (node 0) KB ----------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 232 (6 row(s) affected) CACHESTORE_SYSTEMROWSET (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 544 (6 row(s) affected) CACHESTORE_CONVPRI (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 48 (6 row(s) affected) CACHESTORE_FULLTEXTSTOPLIST (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 32 (6 row(s) affected) CACHESTORE_SEARCHPROPERTYLIST (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) CACHESTORE_COLUMNSTOREOBJECTPOOL (node 0) KB ----------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 32 (6 row(s) affected) CACHESTORE_XML_SELECTIVE_DG (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) USERSTORE_SCHEMAMGR (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 6152 (6 row(s) affected) USERSTORE_DBMETADATA (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 5328 (6 row(s) affected) USERSTORE_TOKENPERM (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 1400 (6 row(s) affected) USERSTORE_OBJPERM (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 368 (6 row(s) affected) USERSTORE_SXC (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 64 (6 row(s) affected) USERSTORE_SXC (node 64) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 8 (6 row(s) affected) USERSTORE_SXC (Total) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 72 (6 row(s) affected) USERSTORE_QDSSTMT (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 48 (6 row(s) affected) OBJECTSTORE_LBSS (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 200 (6 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 Pages Allocated 976 (6 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 Pages Allocated 56 (6 row(s) affected) OBJECTSTORE_SNI_PACKET (Total) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 1032 (6 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 Pages Allocated 576 (6 row(s) affected) OBJECTSTORE_LOCK_MANAGER (node 0) KB ---------------------------------------- ----------- VM Reserved 65536 VM Committed 65536 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 7661032 (6 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 Pages Allocated 24 (6 row(s) affected) OBJECTSTORE_LOCK_MANAGER (Total) KB ---------------------------------------- ----------- VM Reserved 65536 VM Committed 65536 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 7661056 (6 row(s) affected) OBJECTSTORE_SECAUDIT_EVENT_BUFFER (node 0) KB ------------------------------------------ ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 16 (6 row(s) affected) OBJECTSTORE_XACT_CACHE (node 0) KB ---------------------------------------- ----------- VM Reserved 0 VM Committed 0 Locked Pages Allocated 0 SM Reserved 0 SM Committed 0 Pages Allocated 88 (6 row(s) affected) Buffer Pool Value ---------------------------------------- ----------- Database 554081 Simulated 138435 Target 32751616 Dirty 32 In IO 72916 Latched 1 Page Life Expectancy 37 (7 row(s) affected) Procedure Cache Value ---------------------------------------- ----------- TotalProcs 63 TotalPages 1420 InUsePages 0 (3 row(s) affected) Global Memory Objects Pages ---------------------------------------- ----------- Resource 392 Locks 957630 XDES 52 DirtyPageTracking 4 SETLS 4 SubpDesc Allocators 4 SE SchemaManager 444 SE Column Metadata Cache 324 SE Column Metadata Cache Store 5 SQLCache 210 Replication 2 ServerGlobal 52 XP Global 2 SortTables 3 (14 row(s) affected) Query Memory Objects (internal) Value ---------------------------------------- ----------- Grants 0 Waiting 0 Available 35483 Current Max 35483 Future Max 35483 Physical Max 1193558 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 1867 Current Max 1867 Future Max 1867 (5 row(s) affected) Remote Query Memory Objects (internal) Value ---------------------------------------- ----------- Grants 0 Waiting 0 Available 596779 Current Max 596779 (4 row(s) affected) Query Memory Objects (default) Value ---------------------------------------- ----------- Grants 0 Waiting 0 Available 252738 Current Max 252738 Future Max 252738 Physical Max 1182123 Next Request 0 Waiting For 0 Cost 0 Timeout 0 Wait Time 0 (11 row(s) affected) Small Query Memory Objects (default) Value ---------------------------------------- ----------- Grants 0 Waiting 0 Available 13302 Current Max 13302 Future Max 13302 (5 row(s) affected) Remote Query Memory Objects (default) Value ---------------------------------------- ----------- Grants 0 Waiting 0 Available 591061 Current Max 591061 (4 row(s) affected) Optimization Queue (internal) Value ---------------------------------------- -------------------- Overall Memory 10445881344 Target Memory 326426624 Last Notification 0 Timeout 6 Early Termination Factor 5 (5 row(s) affected) Small Gateway (internal) Value ---------------------------------------- ----------- Configured Units 16 Available Units 16 Acquires 0 Waiters 0 Threshold Factor 380000 Threshold 380000 (6 row(s) affected) Medium Gateway (internal) Value ---------------------------------------- ----------- Configured Units 4 Available Units 4 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) Optimization Queue (default) Value ---------------------------------------- -------------------- Overall Memory 10445881344 Target Memory 326426624 Last Notification 0 Timeout 6 Early Termination Factor 5 (5 row(s) affected) Small Gateway (default) Value ---------------------------------------- ----------- Configured Units 16 Available Units 16 Acquires 0 Waiters 0 Threshold Factor 380000 Threshold 380000 (6 row(s) affected) Medium Gateway (default) Value ---------------------------------------- ----------- Configured Units 4 Available Units 4 Acquires 0 Waiters 0 Threshold Factor 12 Threshold -1 (6 row(s) affected) Big Gateway (default) Value ---------------------------------------- ----------- Configured Units 1 Available Units 1 Acquires 0 Waiters 0 Threshold Factor 8 Threshold -1 (6 row(s) affected) Memory Pool Manager KB ---------------------------------------- ----------- Reserved Current 0 Reserved Limit 4317624 (2 row(s) affected) Memory Pool (internal) KB ---------------------------------------- ----------- Allocations 8231456 Predicted 8231456 Private Target 0 Private Limit 0 Total Target 12090144 Total Limit 12576872 OOM Count 0 (7 row(s) affected) MEMORYBROKER_FOR_CACHE (internal) KB ---------------------------------------- ----------- Allocations 7670088 Rate -704 Target Allocations 7365248 Future Allocations 0 Overall 10201056 Last Notification 2 (6 row(s) affected) MEMORYBROKER_FOR_STEAL (internal) KB ---------------------------------------- ----------- Allocations 71176 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_RESERVE (internal) KB ---------------------------------------- ----------- Allocations 0 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_COMMITTED (internal) KB ---------------------------------------- ----------- Allocations 488592 Rate 0 Target Allocations 469168 Future Allocations 0 Overall 10201056 Last Notification 2 (6 row(s) affected) MEMORYBROKER_FOR_HASHED_DATA_PAGES (internal) KB --------------------------------------------- ----------- Allocations 0 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_XTP (internal) KB ---------------------------------------- ----------- Allocations 1600 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) Memory Pool (default) KB ---------------------------------------- ----------- Allocations 27560 Predicted 2391800 Private Target 0 Private Limit 0 Total Target 12090144 Total Limit 12576872 OOM Count 0 (7 row(s) affected) MEMORYBROKER_FOR_CACHE (default) KB ---------------------------------------- ----------- Allocations 21232 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_STEAL (default) KB ---------------------------------------- ----------- Allocations 6328 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_RESERVE (default) KB ---------------------------------------- ----------- Allocations 0 Rate 0 Target Allocations 2270272 Future Allocations 2364240 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_HASHED_DATA_PAGES (default) KB -------------------------------------------- ----------- Allocations 0 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) MEMORYBROKER_FOR_XTP (default) KB ---------------------------------------- ----------- Allocations 0 Rate 0 Target Allocations 318776 Future Allocations 0 Overall 10201056 Last Notification 0 (6 row(s) affected) Memory Broker Clerk (Buffer Pool) Pages ---------------------------------------- ---------------------- Total 553664 Simulated 138352 Simulation Benefit 0 Internal Benefit 0 External Benefit 0 Value Of Memory 0 Periodic Freed 0 Internal Freed 0 (8 row(s) affected) DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Good Morning Experts,
The log file of primary replica database in AG is full and it cannot be shrunk. Could you please let me know how to fix this?
Kiran
Env:
SQL Server 2016 ent edition.
Windows 2016
We are currently using the ASynchronous mode in our AG.
We want to use Synchronous.
However, if the lag between the primary and secondary increases, we would like to use automation to switch again from Synchronous to ASynchronous. I could not find any option in the flexible failover policy.
I can use the DMV (sys.dm_hadr_database_replica_states) to query the column Secondary_Lag_Seconds through a job.
However a job is a polling mechanism.
Looking for some event based automation which will check in a real time if there is latency and switch back and forth between the Sync and Async.
Hi all,
We are using an SQL svr 2016 Standard version, and the AlwaysOn feature is limited to 2 nodes only. My question is, how many databases can we replicate between these two nodes ? is there a limited number per availabilty group ?
Thanks,
Hi,
Could anyone help me with the below query.
The maximum number of databases can be added to a single Availability Group ?
I have around 100 databases and need to be into single AG because of the application design. Would it be possible to add all of them into single AG?
Thank You,
Udham Singh
Hello,
your help will be highly appreciated.
I want to configure in Azure Always-on structure with DR scenario. How do you recommend building this?
I was thinking about this configuration:
primary site:
2 DC's: one primary one secondary
1 FSW server
1 internal LB for the Listener
2 SQL nodes: one primary one secondary.
DR site:
1 node Secondary DC replica
2 SQL Secondary replicas
1 internal LB for the listener.
few questions:
1. all 4 of the SQL nodes will be in the same cluster or should I divide them to another cluster?
if I'm using the same cluster should I configure the DR nodes for manual failover and primary nodes for automatic?
2. in the primary site the SQL nodes will be in sync mode and the SQL nodes in the DR site will be configured in an async mode or not?
3. I have 3 applications running, should I use 1 availability group or 3?
My main question is if the above configurations suitable for HADR? have I missed something?
Thanks all!
From the URL below about "How Synchronization Works on a Secondary Replica" , It describes that "Once the hardened log on the secondary database has caught up the end of log on the primary database, the state of the secondary database is set to SYNCHRONIZED. "
My question is how does the secondary database know that it has caught up the end of log on the primary database?
Suppose there are five transaction log records in primary database, and three of them transfered to the secondary database, how does the secondary database confirm that there are two remains log records haven't arrive? Even if all of the five records transfered to the secondary database, how does it know there is no log records left in the primary database ?
Please click the Mark as Answer button if a post solves your problem!
if a connection, say from SSMS connection , connect to the alwayson listener and specify applicationIntent=Readonly.
how do make sure the connection is really connect/redirect to a read-only replica??
Any view to show it ?
From the URL below we know that "The SQL Server service is down" is a candidate for automatic-failover.
And from the URL below , and we that database damage would preventing automatic failover. It explained the reason why automatic failover wouldn't happen:"When the secondary drops a connection (loss of network, database LDF is damaged, …) the state is updated to ‘not synchronized’, preventing automatic failover"
So it mean that when disconnection happen between the primary and secondary replica, the state is updated to ‘not synchronized’, and from the secondary URL , we know that "SYNCHRONIZED IS THE ONLY STATE ALLOWING AUTOMATIC FAILOVER !!! ", so state in ‘not synchronized’ would preventing automatic failover" , I admit it make sense..
My question:
"The SQL Server service is down" wouldn't cause the disconnection happen between the primary and secondary replica? and the state wouldn't be updated to ‘not synchronized’ after the disconnection ? If both database damage and "The SQL Server service is down" would cause disconnection between primary and secondary replica ,and cause the state is updated to ‘not synchronized’, why "The SQL Server service is down" can be the candidate for "automatic failover" , however database damage wouldn't?
Please click the Mark as Answer button if a post solves your problem!
I'm hoping someone can help bring some sanity to what I'm experiencing.
I have 2 SQL Server 2016 instances clustered with windows clustering. There are 11 user databases on the instance, all set up in their own availability group. All 11 availability groups are set up the same. They are set up for asynchronous
commit, manual failover, non-readable secondary. There is *not* an availability group listener set up for any of the groups. Basically, we purposefully set these up to need manual intervention for anything. All of the applications have connection
strings pointing to the primary node ONLY.
Last weekend, we had some maintenance on our primary node and it was bounced. During that time, there are a flurry of login attempts by all applications to our secondary node. This was surprising, but we assume the cluster was routing connections
during the downtime. After the primary node came back online, most of the applications stopped trying to connect to the secondary node.
However, we're still seeing one application that will attempt to connect to the secondary node several times per day. It's very random...there will be 3 attempts, then a few hours later 1 attempt, then a few hours later 10 attempts, etc. This behavior
has persisted through an application reboot. The application logs are not showing any failed login errors or really any errors that correlate to the attempted login time.
The only theory we have is that SQL Server (or the windows cluster or the application itself querying) is making the availability group known to the application and for some reason the application is trying to connect there.
I've reached out to the application vendor who claims that the application will only try to connect to the host configured in the connect string....
Anyway, if anyone out there could give me something to try I would be very grateful.
I have a job on my live enviroment DB and the job has failed again this morning reporting SQL error 824 (Soft I/O error, where the OS could read the page but SQL has treated it as corrupt) - SQL Server detected a logical consistency-based I/O error: incorrect checksum it occurred during a read of page (1:9545681) in database ID 5 at offset 0x0000123615a000 in file 'D:XXX\XX.mdf'
I have had a look and ran DBCC CHECKDB with all_errormsgs and saw the error didn't mention CHECKSUM failure but outputed the repair level needed to repair this error is 'repair_allow_data_loss'.
Is there anything else that can be done other than running the repair SQL has recommended as I don't want any data loss?
Thanks!
I have Microsoft Azure Backup Server installed on a VM joined to my domain. I have SQL server 2017 configured with basic availability groups. I have installed the backup agent on both SQL servers. When I try to create a protection group
I can see the SQL servers and the cluster. If I open the object SQLc1
All SQL servers
SQL2
Database1
Databse2
I can check mark the databases and add them to a protection group but SQL2 won't always be the primary replica. I can also open
SQLc1 (Cluster)
Cluster Group
Database1
Database2
I can't select the databases under the cluster for backup. Is this a limitation of MABS or Basic Availabilty Groups? How should I configure this so that my database gets backed up?
Thanks
Hi Everyone,
I have got requirement to add one of the database in HA mode.The existing database is a standalone db and no WSFC is configured for that.
In my prod db, Always on mode is not enabled.we don't have any new env for that but can use existing HA environment.
But I have few environments where WSFC is configured (three node cluster) and availability groups is configured as well.
Just want to understand if I take backup of sql server 2012 db and restore into sql server 2014 and configure HA mode.Is it possible?
If not,is there any way to do it?
Please advice.
Regards,
Manisha K
We are planning to upgrade to sql 2016 enterprise edition and at the same time set up fail over cluster. Here's the basic requirements.
A load server where all the daily etls run to load data from OLTP to OLAP (data warehouse).
A reporting server - after the daily load on the load serve a differential backup is taken and restored to the reporting server. The end users and report portal connects to this server.
Please advise what makes sense for fail over clustering. I read a lot of stuff on always on high availability and fail over clustering, which is only confusing me, so I wanted to put my questions on this forum to get some simple answers.
I assume we can do an active passive fail over clustering for the reporting server, which if goes down, the passive node take over and the reports continue to show valid most current data seamlessly. I assume the passive node is read only. in this architecture, I understand we do not require 2 licenses of sql server for the reporting server fail over cluster. Please correct me if I am wrong.
Do we also have an option to have a similar configuration for the load server, where if during the load, the active node goes down, the passive node takes over and the etl continues seamlessly loading on the passive node, until the active node comes back up again. Is this possible or just my imagination? if possible, is this active active configuration, do we need two copies of SQL server license?
Do these configurations need shared storage or individual storage?
Any advise is highly appreciated.
Thanks in advance.
I have a four node WSFC 2008r2 with many SQL FCI. The earliest version of my SQL FCIs is SQL 2008R2.
I intend to evict two out of four nodes from WSFC, format them, and rebuild them with the exact the same configuration, names etc, and add them back in the WSFC. Then I will Add all the SQL FCIs to the cluster one bye one, on both servers.
Is it necessary to remove each instance from each node via the Cluster Node Removal Process prior to evict them from WSFC?
HI ,
I have taken a VSS SQL server database backup.
My requirement is to restore the database with a different name, all files to different location with all files renamed.
Is it possible to do it.
I am able to change the file location and name during pre-restore but unable to change the files names(specs ) name as part of pre-restore changes.(using API AddNewtarget and SetRestoreOptions)
I found a vss API IVssComponent::AddDirectedTarget which does the similar things but in most of the forum its used for partial file restore and also no proper documentation found how to use it.
Can somebody answer if we can restore a MSSQL vss component with different name, files to different location with all files renamed.
If yes, how can we achieve the same.
Thanks
Mi2
We want to change the port of our Always on listener, I ran the SQL to update the port to 1433 from a non-standard port. All three of the instances use a non-standard port. But the listener continued to connect on the previously set port.
I checked the setting and it had changed.
I ran this:
ALTER
AVAILABILITYGROUPgroupname
MODIFY LISTENERN'listenername'(PORT=1433);
I checked the setting on the server, it had changed, but you still could only connect to the listening group on the previously set up port.
What am I missing?
Thanks
Hi,
We have configured always on cluster in azure using Resource manager template which is working fine and accessible within in azure network.
Unable to configure the Public IP for the listener as we need the listener accessible from our local network.
Followed the below article but unable to configure it.
https://blogs.msdn.microsoft.com/sql_pfe_blog/2016/08/08/azure-rm-sql-server-alwayson-availability-groups-listener-configuration-with-azure-external-load-balancer/
do we have any troubleshooting steps that we can run ? any step-by-step guide ?