Unexpected token was encountered in Stored procedures and tables

Hot Topic

Parsing method body
Visual Studio crashes running web test many times
Installing Process Templates
TF26198: The work item does not exist, or you do not have permission to access it.
No process is associated with this object
HOWTO delete a work item in UI
Unit Test Wizard doesn't let me select certain projects.
how to setup controller and agents?
Desperate: Add a user to the Team Foundation Administrators group
How? Programmatically setting /analyze:WX-

VS Team System

Error importing one's own process-template
TF30321: The name you typed is already in use for another team project on the team foundation server."
Reports node in Team Explorer sticks at Working...
S Rule to check String.Empty is used instead of ""
So what happens when Orcas comes out?
TF30162 error
fxcop
Team Project creation failed. "Project folder... already exists."
Policy Override Reports
Error 32000 The Commandline "F:\TFS\Tools\Createds.exe"/Setup/install ...

Unexpected token was encountered in Stored procedures and tables

Hi All

 

When we Build the compiler raises several "Unexpected token was encountered."
On for each Begin/End try/Catch statement

We are also using  buildin system datatype in  a tabe "sysname" This also dont build with a "Unexpected token was encountered."

Open XML

Does any one know why

The project type is SQL 2005, but it seems like no 2005 features are supported. All Try Catch are also not marked as a known keyword  in the editor. and Ope nXML does not work either.

Regards

Christian 

 

Answer this question

Unexpected token was encountered in Stored procedures and tables

  • Eric Liang

    Gianluca -

    If you encounter crashing bugs, even with SQL Server 2005, please let us know. For other issues, you should focus on SQL Server 2000 until we have a newer build available with SQL Server 2005 support.



  • srkumar

    StevenPo wrote:

    If you encounter crashing bugs, even with SQL Server 2005, please let us know. For other issues, you should focus on SQL Server 2000 until we have a newer build available with SQL Server 2005 support.

    Thanks Steven,
    we started a pilot project to migrate a couple of small applications from 2000 to 2005 and from .NET 1.1/VS2003 to .NET2.0/VS2005 TFS, so in the next weeks the idea is still to try targeting SQL 2005 but we won't use any 2005 specific functionality.

    Hope I'll still be able to make it work with workarounds in the pre/post scripts, anyway if I find something I'll try to repro it targeting SQL 2000 and will eventually report it through connect.



  • Stephane Tombeur

    This is a parser error and is becuase we do not yet completely support all SQL Server 2005 features, including the try catch sql block. At RTM we will have full SQL Server 2005 support, today we only support SQL Server 2005 databases that use no features (SQL etc) which are not in SQL Server 2000

    Matt



  • Tarkan G.

    Hi Matt

    Thanks for the quick answer.

    We just wait for the next drops then. Our current development environment uses SQL 2005 and VS 2005 /Team Foundation Server, so we are looking forward especially to source control integration and unit test.

    Christian

  • Freddy Vanbaelen

     Matt Nunn wrote:

    This is a parser error and is becuase we do not yet completely support all SQL Server 2005 features, including the try catch sql block. At RTM we will have full SQL Server 2005 support, today we only support SQL Server 2005 databases that use no features (SQL etc) which are not in SQL Server 2000

    Hi Matt,
    generally is it worth reporting things about SQL Server 2005 integration or should we just focus on 2000 and wait for RTM (or a later build) to report them

    TIA



  • Bradley

    SQL 2005 projects are not yet supported in the CTP3 drop. They'll be supported in future drops.

    Thanks,

    -Tom

    SDE/T - VS Team System for Database Professionals



  • Unexpected token was encountered in Stored procedures and tables
Answer this question