The following query, which looks good to me, gets "Incorrect syntax near 'FULLTEXT'" when I try to run it in the 2005 Management Studio and in Enterprise Manager:

CREATE FULLTEXT CATALOG [VirtualMOSCatalog]
IN PATH N'c:\Program Files\Microsoft SQL Server\MSSQL\FTDATA'
WITH ACCENT_SENSITIVITY = ON
AUTHORIZATION [dbo]

The database is Full-Text Index enabled and this code was automatically generated from another database.

I get a similar error from this query:

CREATE LOGIN [MOSuser] WITH PASSWORD=N'abc123', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=ON

What do I need to do to get these queries to run?

Ron, I copied and pasted your exact syntax into a query window in my SQL Server 2005 environment and both statements executed without error. Are you still getting this error?

Yeah. It's driving me nuts. I'm trying to run it by simply opening the file in a window in Management Studio. is there someplace else these sorts of scripts have to be run to recognize the syntax?

Not that i know of. That is where i ran them...in a query window in Management Studio.

I would start dissecting the statement, make it as simple as possible. For example:

CREATE FULLTEXT CATALOG VirtualMOSCatalog
GO

If that succeeds, drop it and try a more complicated statement:

CREATE FULLTEXT CATALOG VirtualMOSCatalog
IN PATH 'c:\program files\microsoft sql server\mssql\data'
GO

and so on. I would also try the same thing with the CREATE LOGIN statement...

Tried that. Still puked on FULLTEXT. But we understand why, now.

The problem is that the script syntax is for a SQL Server 2005 database and we're still running 2000, although using the new Server Management Studio. For some reason understood only by the developer, she used 2005 to generate the script even though it was a SQL Server 2000 database being scripted. The Studio won't translate 2005 code to 2000. We got 2000 format script - problem solved.

So, it's just a slightly smaller version of the miles/kilometers miscommunication experienced by that doomed Mars explorer. ;)

Thanks for checking my sanity, though. :)

Hey Guys, I recently ran into the same issue but was able to get around it using enterprise manager to create my index. Can you explain what the difference was in the script that allowed it to work on a 2000 database.

Thx