December 28, 2006 at 10:15 pm
These are general questions pertaining to SQL select statements and unforeseen performance issues that I may not be aware of.
I know that INSERT, UPDATE, and DELETE statements are logged but I am under the assumption that SELECT statements are not. It makes sense to me that this would be the case because no database modifications are taking place. Am I correct in this assumption?
Next, I have a scenario where one or more applications will be performing nearly continuous SELECT statements on a single SQL Server database. The statements are very simple and just return scalar values. Are there any performance issues that I should be aware of with a scenario like this?
Thanks to all who can shed some light on the subject for me.
--pkoanui
January 1, 2007 at 8:00 am
This was removed by the editor as SPAM
January 1, 2007 at 12:35 pm
No logging for SELECTs, you are correct in that.
For the continuous selects, likely the data will remain in cache in memory, if it's the same or similar data, and you should be ok. You have to test, and test under load. You might consider perhaps caching on the client if that's possible or the new query notification in SS2K5 if you're using that.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply