InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 12:24:01 GMT20http://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxYou may also try to run a query with a huge IN clause....Wed, 09 Jan 2013 18:40:35 GMTbarsukhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspx[quote][b]Oracle_91 (1/8/2013)[/b][hr]Hi Gus,I am just testing/learning memory concepts over here. not to throttle any productions systems :-)[/quote]Ah! That makes sense then.Yeah, learning how to deliberately overload the data cache vs the plan cache vs crushing the O/S space, etc., are all useful things. Good idea. Gives you a better idea of what can do those kinds of things, so you can fix it when it happens in the wild.Try some things like loading too many big tables into active queries, all at the same time.Try firing off a bunch of hyper-complex queries all at once.Try non-deadlock long locks.Wed, 09 Jan 2013 11:08:48 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxHi Gus,I am just testing/learning memory concepts over here. not to throttle any productions systems :-)Tue, 08 Jan 2013 09:53:28 GMTOracle_91http://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspx[quote][b]Oracle_91 (1/7/2013)[/b][hr]Hi Thank you.I am looking for T-sql script which will use up memory so that i can monitor which process is eating up most of memory.[/quote]Whichever part your script targets.I guess I'm a bit lost here. If you deliberately overload memory, what you'll see eating up memory is the thing you used to overload it.Bend your finger backwards till it hurts (a little bit). If you then look at your hand to figure out what's causing the pain, it'll be you bending your finger backwards. In other words, you already know the cause, because you deliberately picked it and implemented it.I'm not seeing the benefit to this, unless what you're doing is testing some sort of monitoring tool to see if it correctly identifies the problem and says (metaphorically), "Hey, check it out, you're bending your finger backwards! You should stop doing that." On the other hand, if the monitoring software says, "Possible stubbed toe detected. Suggested handling: Amputate at hip", then you've found out something useful, and know that you can dispense with using that monitoring software.But that doesn't seem to be what you're doing here.Tue, 08 Jan 2013 06:56:58 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspx[quote][b]Oracle_91 (1/8/2013)[/b][hr]Do you have any steps to reproducing the error?[/quote] NO.but see if these link can help you [url]http://blogs.msdn.com/b/karthick_pk/archive/2012/06/22/a-significant-part-of-sql-server-process-memory-has-been-paged-out.aspx[/url][url]http://support.microsoft.com/kb/918483[/url]Tue, 08 Jan 2013 02:12:40 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxNothing. Just wanted to reproduce the issue and see the performance counters. Doing some reading Memory.... Do you have any steps to reproducing the error?Tue, 08 Jan 2013 00:52:38 GMTOracle_91http://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspx[quote][b]Oracle_91 (1/7/2013)[/b][hr]“A significant part of SQL Server process memory has been paged out. This may result in performance degradation".[/quote] ANy reason why you ONLY need this particular error msg?:w00t:Mon, 07 Jan 2013 23:34:28 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxI have had Apache cause that several times for me. I have even had malware scanners cause it.Mon, 07 Jan 2013 23:08:33 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxHi Gus,I wanted to reproduce the below errormsg. I was able to inflate the sql memory. But i need someother process or exe which blot the memory and results in below error message. how to do it?“A significant part of SQL Server process memory has been paged out. This may result in performance degradation".Mon, 07 Jan 2013 23:03:11 GMTOracle_91http://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxHi Thank you.I am looking for T-sql script which will use up memory so that i can monitor which process is eating up most of memory.Mon, 07 Jan 2013 20:19:08 GMTOracle_91http://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxI'm not entirely clear on what you're asking.Do you need a way to monitor SQL Server memory use?OrDo you need a T-SQL script that will consume a huge amount of memory so you can test a monitor?If you need a way to monitor memory use, you have a number of options. Partially, it depends on budget. RedGate (owners of this site) have a monitoring tool. So do SolarWinds, and several other companies. Search for "monitor server memory use" online and you'll find plenty of solutions for this.If you need a script that will use a ton of memory, that's pretty easy to do. Open a connection, start a transaction, update a single row in a table, but don't commit the transaction or close the connection. Repeat this till the memory is as loaded up as you like. Make sure you aren't using SSMS on the server to do this, because you'll get SSMS eating more memory for the connections than you will get SQL Server eating memory for the transactions. Should use a ton of RAM in a sort of DDOS manner.Alternatively, create a few varchar(max) datatype variables, and load strings into them till SQL Server dies, or you get the RAM load you're looking for.Lots of ways to eat up a lot of RAM.Mon, 07 Jan 2013 13:12:08 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1403810-360-1.aspxHi 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.Mon, 07 Jan 2013 12:28:50 GMTOracle_91