July 20, 2016 at 8:42 am
Hi - I've received reports to advise that one of our applications has a delay in displaying up to date data when switching betweens screens.
I'm at the very starting point of investigating this issue but just wanted some pointers in terms of what to look at from a SQL standpoint.
It's quite possible this could be an application issue but just wanted to eliminate SQL as a starting point.
Any help/advice very much appreciated.
Regards
Dax
July 20, 2016 at 8:53 am
Hmm it would be impossible to help without first understanding, what is the relationship between these two screens and the database?
Is it a read and/or write of the same table between these two different screens?
Is it a read and/or write of different tables that are somehow replicated and displayed between these two screens?
when you say there is a delay does that imply that the data does eventually get "replicated" to the other screen and that data integrity is 100%?
What is the time delay?
July 20, 2016 at 9:36 am
It's about capturing metrics. If you suspect that an action on the app is delayed by other actions on the database, you'd focus on queries against the database during the time in question. The best way to capture queries using 2008 servers is trace (although extended events are available, they're harder to use). Here's an intro to trace.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply