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 |
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
 Posted - 2010-01-18 : 10:43:19
|
| Now that pinning is NOT an option, what are the best options for selecting data from heavily accessed lookup tables? I know about the Indexes, partitions, fill factors, etc. Is there a way to keep the tables “in memory” or are we at the mercy of SQL engine? I am looking for an alternate option for pinning a table. ------------------------I think, therefore I am - Rene Descartes |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-01-18 : 11:31:21
|
| Ensure that your queries are written as optimally as possible (so that no more data than is needed is read). Ensure that the indexes are optimal so that SQL's not pulling more data into cache than necessary. Ensure that there's enough memory on the server, and enough of it is assigned to SQL.--Gail ShawSQL Server MVP |
 |
|
|
|
|
|
Pinning a table