Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
nmg196
Yak Posting Veteran
70 Posts |
 Posted - 2001-07-13 : 09:13:25
|
Hi,I'm struggling and could REALLY use some help here!Basically, I'm trying to transfer a database which uses full-text indexing on 3 tables from SQL2000 sp1 to another SQL2000 sp1 install using DTS (transfer objects) and it's failing with the following error:"IX_tbTranslation_nID is not a valid index to enforce a full-text search key.""You must specify a unique, non-nullable, single column index."The index in question conforms to the criteria mentionned:CREATE TABLE [dbo].[tbTranslation] ([nID] [int] IDENTITY (1, 1) NOT NULL ,...etcCREATE UNIQUE INDEX [IX_tbTranslation_nID] ON [dbo].[tbTranslation]([nID]) ON [PRIMARY]...etc ..and the full-text catalog is set to use this index.So why do I get this error?!If I remove the full-text indexes and transfer the DB, I get errors because loads of stored procedures use full-text keywords like CONTAINS. So I can't really do that either.Does anyone have any idea why this is happening, or how I can transfer a DB with full-text indexing?I've looked on the web/microsoft/google etc, and can find no relavent information. It doesn't appear to be a known bug.Thanks in advance for your help,Nick... |
|
|
nmg196
Yak Posting Veteran
70 Posts |
Posted - 2002-03-19 : 08:33:05
|
| By the way... This problem was fixed by installing the latest service pack on the machine running enterprise manager - NOT the server itself. Enterprise manager was generating some dubious SQL for recreating the Full-Text indexes (it was creating the indexes in the wrong order).Nick... |
 |
|
|
|
|
|
Transferring DB with full-text indexing - FAILS!