Re: Profiling error message 208: sorting the wheat from the chaff
From: AnthonyThomas (Anthony.Thomas_at_CommerceBank.com)
Date: 01/13/05
- Next message: Kiran: "Incorrect syntax near the keyword 'OR'."
- Previous message: Andrew J. Kelly: "Re: PARTITIONING DISKS"
- In reply to: Greg Linwood: "Re: Profiling error message 208: sorting the wheat from the chaff"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 Jan 2005 08:06:54 -0600
Ah, got'cah. So, you'd have manufacture data by using a GROUP BY around
execution time over some sample duration and then exclude off of that, like
the closes NOT NULL Text data without the Error statement, either before or
after the StartTime of the error.
Sincerely,
Anthony Thomas
-- "Greg Linwood" <g_linwoodQhotmail.com> wrote in message news:OUgPq1T%23EHA.3700@tk2msftngp13.phx.gbl... That doesn't work becasue the text reported in the TextData column only ever shows "Error: 208, Severity: 16, State: 0" so there's no content by which you can effectively provide a predicate. Regards, Greg Linwood SQL Server MVP "AnthonyThomas" <Anthony.Thomas@CommerceBank.com> wrote in message news:OnIi5pT%23EHA.2076@TK2MSFTNGP15.phx.gbl... > Sure there is: it's called a query. Profile load to a file then load the > file to a table or have Proviler load to a table directly. The, you can > use > whatever predicates you desire within the WHERE clause against that table. > > SELECT * > FROM <profiler table> > WHERE (Error = 208 > AND [Text] NOT LIKE '%CREATE%PROCEDURE%' > ) > OR COALESCE(Error, 1) <> 208 > > Sincerely, > > > Anthony Thomas > > > -- > > "Greg Linwood" <g_linwoodQhotmail.com> wrote in message > news:%23m4ZBis2EHA.1264@TK2MSFTNGP12.phx.gbl... > Hi Mark > > Unfortunately, I've not found a way to do this either yet. This little > problem regularly peeves me as the consequences of real 208's can be > damned > serious at times - depending on your circumstances, even leading to lost > work / business as 208's can orphan transactions, create massive blocking > chains etc. > > I discussed this in the private MVP newsgroup just back in October and > no-one was able to provide a useful answer in there either so I don't > think > there's any way to do this at present. > > Regards, > Greg Linwood > SQL Server MVP > > "Mark Andersen" <markandersen@evare.com> wrote in message > news:e189957b.0412030624.1a8af64c@posting.google.com... >> Using Microsoft SQL Server 2000: >> >> If I turn on profiling in our production system, I see hundreds of >> "208" errors. Most of these are false indications of problems which >> result from the use of temporary tables. >> >> For example, a 208 error is generated when one compiles a stored >> procedure which declares and uses a temporary table. >> >> However, some errors interest us. Even some 208 errors. From time to >> time, a programmer might make a genuine 208 error and fail to catch it >> (I saw one caused by an exec statement where the developer forgot to >> check @@error). >> >> I'd like to filter out the uninteresting 208 errors (temporary tables >> in stored procedures) and retain the rest. Has anyone succeeded in >> doing that? What is the best practice for profiling--keep getting >> error 208 in order to have the chance to see other errors and >> warnings? >> >> Any suggestions would be helpful. >> >> Ideally, I would like all interesting 208's and all other errors. >> Failing that, I would like all non-208 errors. (Do I simply add a >> filter where error<>208 to do that). >> >> Turning off all errors does not seem like a great idea. > >
- Next message: Kiran: "Incorrect syntax near the keyword 'OR'."
- Previous message: Andrew J. Kelly: "Re: PARTITIONING DISKS"
- In reply to: Greg Linwood: "Re: Profiling error message 208: sorting the wheat from the chaff"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
