Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2011-07-16 : 11:07:46
|
I ran through thishttp://www.sqlteam.com/article/what-data-is-in-sql-server-memoryOne thing i saw in ours were old tables that were at least 3 years old.I am curious why they still remain in memory. When you shutdown SQL Server the memory still retains these in the pool..i was under the impression that got cleared out when you shutdown SQL.If i know the tables are old is it safe to just clear out the tables.Also I see some tables that have indexes but appear as HEAP..Maybe from someone doing select * from table. It is good to go ahead and drop these too.Thanks |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2011-07-17 : 10:09:38
|
Yes I do.I also noticed if i just clear the dbcc dropcleanbuffers that even when i just do open database in SQL Studio all the tables go in the memory, if i go to another database on SQL all the tables still appear in the buffer. I didn't know that when you just look at databases, tables they go to buffer at that time. I thought that the data only writes to buffer when you do a command select * . |
 |
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-07-17 : 13:41:06
|
All forms of queries result in data going into memory. In fact, the query execution engine can ONLY work against the buffer pool, it has no idea what a disk or file is. Hence any query that uses a table will result in some (or all) of that table going into memory.--Gail ShawSQL Server MVP |
 |
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2011-07-18 : 20:38:06
|
Thanks for the information. |
 |
|
|
|
|