January 4, 2012 at 11:46 am
The HP server that our SQL Server 2008 SP2 instance is running on has been rebooting itself. An HP support article suggests that we enable trace flag -t8038. http://h20000.www2.hp.com/bizsupport/TechSupport/document.jsp?objectID=c02110402&lang=en&cc=us&taskId=101&prodSeriesId=3896111&prodTypeId=3709945
Does anyone have experience with this flag? Is it something I should even try testing in dev? Will it affect applications, because the time won't be kept to the nearest 1ms?
January 4, 2012 at 12:06 pm
Have you read through this: http://blogs.msdn.com/b/psssql/archive/2009/05/29/how-it-works-sql-server-timings-and-timer-output-gettickcount-timegettime-queryperformancecounter-rdtsc.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 4, 2012 at 12:12 pm
GilaMonster (1/4/2012)
Have you read through this: http://blogs.msdn.com/b/psssql/archive/2009/05/29/how-it-works-sql-server-timings-and-timer-output-gettickcount-timegettime-queryperformancecounter-rdtsc.aspx
Yes, I already have.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply