Re: Profiling error message 208: sorting the wheat from the chaff

From: AnthonyThomas (Anthony.Thomas_at_CommerceBank.com)
Date: 01/13/05 

Date: Thu, 13 Jan 2005 00:37:06 -0600

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.

Relevant Pages

  • Re: Profiling error message 208: sorting the wheat from the chaff
    ... Profile load to a file then load the> file to a table or have Proviler load to a table directly. ... > SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: FW: HMC load failure - IPL address 0000 invalid
    ... >to activate the lpar, or just a LOAD profile? ... >A load profile has a pre-determined load address and parm specified. ... >Double click exact icon that is being "ACTIVATED" for the system to IPL ...
    (bit.listserv.ibm-main)
  • Intermittent problems loading amazon.com - please help
    ... I can get the page to load on my system, and I know it's not being blocked ... This made it seem like it was something in the profile, ... I've tried deleting cache files, and even manually combing through the test ... so I'm hoping I can find what's wrong and fix ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: windows cannot load your profile ?
    ... then under "Registry Size" you can set the value to a higher ... if admin user default profile will load" ... This doesn't make much sense since the user profile should load. ...
    (microsoft.public.win2000.general)
  • slow
    ... >The computer boots slower than normal, ... >then the windows screen pops up and it takes AGES to load ... >upto the point where one choses a profile. ... >The computer then contniues to load but EXTREMELY slow, ...
    (microsoft.public.windowsxp.hardware)