SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


cluster failover --memory


cluster failover --memory

Author
Message
muth_51
muth_51
SSC Eights!
SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)

Group: General Forum Members
Points: 943 Visits: 2905
Yes Perry is right. I mean DBCC DROPCLEANBUFFERS. Edited the previous post.
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19982 Visits: 17243
muthyala_51 (3/7/2014)
Yes Perry is right. I mean DBCC DROPCLEANBUFFERS. Edited the previous post.

You need to checkpoint the database(s) before dropping clean buffers. Did you run checkpoint first?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
muth_51
muth_51
SSC Eights!
SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)

Group: General Forum Members
Points: 943 Visits: 2905
Nope. I never ran the checkpoint stmnt.
muth_51
muth_51
SSC Eights!
SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)

Group: General Forum Members
Points: 943 Visits: 2905
any suggestions?
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19982 Visits: 17243
muthyala_51 (3/8/2014)
any suggestions?

For what?
anything now would just be speculation since the instance was restarted

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
muth_51
muth_51
SSC Eights!
SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)

Group: General Forum Members
Points: 943 Visits: 2905
Perry Whittle (3/9/2014)
muthyala_51 (3/8/2014)
any suggestions?

For what?
anything now would just be speculation since the instance was restarted


I am trying to find the exact reason behind why the server behaved like this. Choked for memory even it had enough memory.
Lynn Pettis
Lynn Pettis
SSC-Dedicated
SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)

Group: General Forum Members
Points: 39362 Visits: 38543
Again, anything we say is just speculation. We don't have access to your server and the logs. You need to check the all the logs on the server to try and determine what occurred.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
sqlbuddy123
sqlbuddy123
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2376 Visits: 2243
muthyala_51 (3/9/2014)
Perry Whittle (3/9/2014)
muthyala_51 (3/8/2014)
any suggestions?

For what?
anything now would just be speculation since the instance was restarted


I am trying to find the exact reason behind why the server behaved like this. Choked for memory even it had enough memory.


To know the exact reason you should do a lot of troubleshooting not just shallow look ups. The information you provided was not enough. So pls try to answer the questions by the people so that you can get close to the solution.

--
SQLBuddy
muth_51
muth_51
SSC Eights!
SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)SSC Eights! (943 reputation)

Group: General Forum Members
Points: 943 Visits: 2905
I went through all the logs and grabbed some info for you guys. The following links gives us the exact scenario which happened at that time.....

Error 1: There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.

Error 2: New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 1680 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2917ea9b-d5d4-4a5f-839b-9f363041b685/sql-server-is-not-accepting-connections

http://www.sqlservercentral.com/blogs/aschenbrenner/2011/10/25/troubleshooting-threadpool-waits/

We have a 32 CPU on our production server and max worker threads setting is set to 2048. But according to microsoft recommendation it should be 960.
sqlbuddy123
sqlbuddy123
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2376 Visits: 2243
muthyala_51 (3/10/2014)
I went through all the logs and grabbed some info for you guys. The following links gives us the exact scenario which happened at that time.....

Error 1: There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.

Error 2: New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 1680 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2917ea9b-d5d4-4a5f-839b-9f363041b685/sql-server-is-not-accepting-connections

http://www.sqlservercentral.com/blogs/aschenbrenner/2011/10/25/troubleshooting-threadpool-waits/

We have a 32 CPU on our production server and max worker threads setting is set to 2048. But according to microsoft recommendation it should be 960.


Error 1: Check this

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL+Server&ProdVer=2000.80.760.0&EvtID=17803&EvtSrc=MSSQLServer

Error 2: Try changing max worker threads to default value and test it.

What are your CPU settings on the server ? MAXDOP, CPU Affinity etc .. Do you have CLR , Linked servers hosted on SQL Server ?


--
SQLBuddy
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search