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 |
|
acollins74
Yak Posting Veteran
82 Posts |
 Posted - 2008-01-10 : 09:14:47
|
| Scenerio.Sql Server 2005 SP 2Log ship from Source Server to Target Server - SuccessTarget aka secondary database in read only state - WonderfulAttemp to run proc/query on LS read only database<ultimately report off of> - Results very slow to return; well at least the first time. Subsequent executions respond as expected until the next Log Ship Restore and then slow again.Would this be caused because of caching and has anyone experience this behavior as well? All and any suggestions are welcome. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-10 : 23:33:09
|
| Yes, applying log will clean up procedure cache. |
 |
|
|
acollins74
Yak Posting Veteran
82 Posts |
Posted - 2008-01-14 : 09:05:43
|
| Is there any way to capture the cache or force the cache not to flush? orI thought about potentially pinning tables but thats not an option in 2005. Any thoughts are great.Thanks. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-14 : 23:37:54
|
| Don't think you can control that. |
|
|
|
|
|
|
log shipping, read only, and queries