Re: Capturing SQL code that generates error
From: Narayana Vyas Kondreddi (answer_me_at_hotmail.com)
Date: 07/06/04
- Next message: Andrew J. Kelly: "Re: SQL 2000 Maint. Plans"
- Previous message: Ben: "SQL 2000 Maint. Plans"
- In reply to: DanetteB: "Capturing SQL code that generates error"
- Next in thread: DanetteB: "Re: Capturing SQL code that generates error"
- Reply: DanetteB: "Re: Capturing SQL code that generates error"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 6 Jul 2004 14:50:51 +0100
Have you considered using Profiler? Let us know if you need help with using
Profiler to capture the statement and the error.
-- HTH, Vyas, MVP (SQL Server) http://vyaskn.tripod.com/ Is .NET important for a database professional? http://vyaskn.tripod.com/poll.htm "DanetteB" <DanetteB@discussions.microsoft.com> wrote in message news:E5E14CFC-8F1C-49F5-AEE5-40C14448FC86@microsoft.com... I have an application that imports application data based on the Windows Installer .MSI schema into a SQL database. If it possible that the data in the tables exceeds the size allowed in our database. When that happens, an error message is generated. This is fine as the user has the option to 'Ignore.' The problem is that I cannot tell what application is being imported when the error message is produced. Is there a method to capturing the 'parent' SQL insert statements so that I can get the application name? Thanks
- Next message: Andrew J. Kelly: "Re: SQL 2000 Maint. Plans"
- Previous message: Ben: "SQL 2000 Maint. Plans"
- In reply to: DanetteB: "Capturing SQL code that generates error"
- Next in thread: DanetteB: "Re: Capturing SQL code that generates error"
- Reply: DanetteB: "Re: Capturing SQL code that generates error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|