Re: Syntax Check
From: Pablo Castro [MS] (pablocas_at_online.microsoft.com)
Date: 02/23/05
- Next message: Bruce A. Julseth: "Has a bound control been changed"
- Previous message: Cathie Hagen: "Syntax Check"
- In reply to: Cathie Hagen: "Syntax Check"
- Next in thread: Cathie Hagen: "Re: Syntax Check"
- Reply: Cathie Hagen: "Re: Syntax Check"
- Reply: Cathie Hagen: "Re: Syntax Check"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 20:35:23 -0800
If you're running against SQL Server, you can use "SET PARSEONLY ON|OFF".
Check out books online for details on PARSEONLY. The short story is that you
can execute that before your statement so the server parses the statement
and generates an error if there is a syntax error, but the statement never
actually gets executed. Make sure you revert it to OFF before trying to
execute something for real.
-- Pablo Castro Program Manager - ADO.NET Team Microsoft Corp. This posting is provided "AS IS" with no warranties, and confers no rights. "Cathie Hagen" <cathie@bob.com> wrote in message news:uDaBA%23VGFHA.2180@TK2MSFTNGP12.phx.gbl... > Hi All, > > Is there a way to do a syntax check on the statement without executing it? > > Cathie > >
- Next message: Bruce A. Julseth: "Has a bound control been changed"
- Previous message: Cathie Hagen: "Syntax Check"
- In reply to: Cathie Hagen: "Syntax Check"
- Next in thread: Cathie Hagen: "Re: Syntax Check"
- Reply: Cathie Hagen: "Re: Syntax Check"
- Reply: Cathie Hagen: "Re: Syntax Check"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
