May 2, 2006 at 1:22 pm
So I'm having an issue with one of my servers and I'm new to this job and environment and I want to run SQL Profiler to attempt to figure out what's going wrong. along that line, I have a few questions.
1)are there any good books out there that really tear profiler down and let you get a good grasp of it quickly,
2) I'm now in a shop that can't really take a performance hit on server A while profiler is running, nor does it have the free drive space avail to store the log files, is it better to run from server B saving data to the B or run from A saving to B?
3) the real root of my inquiries come from two records that get inserted into a table. Other portions of my app are expecting the results to come out like this row1: data, row2: data. Instead the occasionally get inserted in reverse and then when they are outputted the app errors out. I figure a profiler trace could help me narrow down my problems on the insert weather it be locking issues or whatnot as I'm rather at a loss. The question is, what would be a decent starting point for events, and such to capture?
Thanks in advance. -Luke.
May 3, 2006 at 3:46 am
Profiler can be a performance hit, so be careful, running it across the network to another server is useful but will hit network traffic. Be as minimal with the events and data as you can be .. sounds to me it's an app issue not a server issue. There should be loads of stuff on any sql server site on profiler and at microsoft. Most sql books cover profiler.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
May 3, 2006 at 11:34 am
try to run SQL Server trace ( as opposed to SQL Profiler which is the client-side implementation)...and see if it is produces less load...
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply