Executing Parse in Sql Server 2005 Management Studio I get the following error:
.Net SqlClient Data Provider: Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Reading SP1 fixes, I found a similar problem but despite I installed latest hotfix (sql version is now 9.0.2153) I can't able to execute Parse to check T-SQL statements...
Thanks,
Giulio

Error executing Parse in SSMS
chocobo_ff
I tried using this sample statement and I get error...
Alter
Table Agente Add xTipoAgente Numeric(1, 0) NullThanks,
Giulio
kamuixkotori
Tigerwood2006
I'm not sure but I would have a customer with same problem... 3 machines with 3 different SQL Server 2005 (all standard edition, 2 english and 1 italian) and same problem: it doesn't seem to be a coincidence...
Giulio
megame
TCP/IP and Named Pipe protocols are enabled.
Giulio
Zamial
I couldn't find any more information or help with this problem. Sorry. I might consider a reinstall or a call to Microsoft.
Sorry....
mcobrien
Senthil Ramadoss
i sense internal error..
your sql server can be sitting on a problematic OS.
how about reinstalling the OS and the SQL server.
well, just in case you run out of options
Ben Wang
Sorry, it doesn't fail for me. Will the statement execute Is is just the parse that fails
What version of SQL Server ar you using Do an @@version:
select @@version
If no one replies I will ask around and see what I can find out.
AndersL
I have SQL Server 2005 installed on a Windows 2003 Server and a Windows XP Professional Sp2.
Sql version (Italian) on W2k3 is:
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Sql version (English) on WXP is:
Microsoft SQL Server 2005 - 9.00.2153.00 (Intel X86) May 8 2006 22:41:28 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
Also parsing "select @@version" I get error on both machines...
However it seems to be just a parser problem.
RizwanSharp
Thanks...