Stored procedure depends on Full-text Index - SQL Compare

TimVerversTimVervers Posts: 13 New member
edited June 30, 2015 4:31PM in SQL Compare 11
Dear RedGate,

We are currently creating model scripts of our Database that includes Full Text indexes. And one of our Stored procedures depend on those indexes.

I get the following error :
Msg 7601, Level 16, State 2, Procedure pr_Search, Line 55
Cannot use a CONTAINS or FREETEXT predicate on table or indexed view 'table_name' because it is not full-text indexed.
I think SQL Compare ignored the relationship between our Stored procedure and the full-text index. If i copy the Create part for our Stored procedure after the creating of the fulltext index the scripts works fine.

Thanks in advance,

Tim Ververs
Communited

Comments

  • Eddie DEddie D Posts: 1,666 Rose Gold 5
    Thank you for your forum post and sorry for the delay in replying back to you.

    The problem you have encountered is known problem. I have added the details of this forum post to an existing Bug Report whose reference is SC-1196. Sadly it appears that the Development Team are having a few problem fixing this problem and therefore sadly I cannot provide an ETA as to when this issue will be fixed.

    Many Thanks
    Eddie
    Eddie Davis
    Product Support Engineer
    Redgate Software Ltd
    Email: [email protected]
  • TimVerversTimVervers Posts: 13 New member
    I saw that SC-1196 was fixed. Will there be an ETA for this solution?
  • Yes, SC-1196 was fixed in version 11.2, at the beginning of May (see http://documentation.red-gate.com/display/SC11/SQL+Compare+11.2+release+notes), which means that dependencies on full text indexes are now correctly handled.

    Note that you need to use the option to turn transactions off; this is due to the SQL Server limitation that full text indexes and catalogs cannot be modified within a transaction.
    Development Lead
    Redgate Software
Sign In or Register to comment.