You can use
Caching a DataTable Object
The code in these examples suspends all other threads in a critical section running in IIS, and prevents other threads from accessing the cached object until it is completely built. This addresses the thread synchronization issue; however, the code is still not correct because it is caching an object that is not thread safe.
To address thread safety, you can cache a DataTable object that is created from the SPListItemCollection object. You would modify the previous example as follows so that your code gets the data from the DataTable object.
private static object _lock = new object();
public void CacheData()
oDataTable = (DataTable)Cache["ListItemCacheName"];
if(oDataTable == null)
oListItems = DoQueryToReturnItems();
oDataTable = oListItems.GetDataTable();
Cache.Add("ListItemCacheName", oDataTable, ..);
Now you can get single item without requesting to SQL Server to get item from SharePoint list. You can use this
Cache in every where like a session.