Red Gate forums :: View topic - Cannot use a CONTAINS ... it is not full-text index indexed
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Packager 6
SQL Packager 6 forum

Cannot use a CONTAINS ... it is not full-text index indexed

Search in SQL Packager 6 forum
Post new topic   Reply to topic
Jump to:  
Author Message
radiantgrid



Joined: 14 Apr 2009
Posts: 1

PostPosted: Tue Apr 14, 2009 5:42 am    Post subject: Cannot use a CONTAINS ... it is not full-text index indexed Reply with quote

I'm attempting to create a new database that i've packaged, but i'm getting this error:

"Cannot use a CONTAINS or FREETEXT predicate on table or indexed view 'dbo.UserEventsView' because it is not full-text indexed."

Seems like the view isn't being marked as FT indexed by the time my function that references was created.

Is this a bug in SQL Packager, or something I need to change in the way i'm packaging things?

Thanks,
Kirk
Back to top
View user's profile Send private message
Chris Auckland



Joined: 24 Oct 2006
Posts: 755
Location: Red Gate Software Ltd.

PostPosted: Thu Apr 16, 2009 10:03 am    Post subject: Reply with quote

Thanks for your post.

Unfortunatly this is an issue with the SQL Compare engine part of SQL Packager, which is explained in the following forum thread:
http://www.red-gate.com/MessageBoard/viewtopic.php?p=25607#25607

I think the only workaround would be similar to the suggested workaround for SQL Compare, that being to create a package for the fulltext catalogs / tables with fulltext indexes first, and then another package for the rest of the database.
_________________
Chris
Back to top
View user's profile Send private message Send e-mail
Chris Auckland



Joined: 24 Oct 2006
Posts: 755
Location: Red Gate Software Ltd.

PostPosted: Tue Apr 21, 2009 10:48 am    Post subject: Reply with quote

Looking at this again, you could create each of the scripts first using SQL Compare (and data compare for the data), and then package the set of scripts using SQL Packager, then you could accomplish this using a single package.

e.g.

(If you want to package a new install, use SQL Compare against a blank database.)

1. Create the script for the fulltext catalogs / tables with fulltext indexes
2. Create the script for other schema objects
3. Create data scripts using SQL Data Comapre
4. Copy them all into a single sequential .sql file
5. Use SQL Packager 6 to package the complete script
_________________
Chris
Back to top
View user's profile Send private message Send e-mail
cbertolasio



Joined: 27 Jun 2006
Posts: 3

PostPosted: Mon Sep 14, 2009 4:40 pm    Post subject: Re: Reply with quote

I am having the same issue as well. You solution below will work.

However, as a user using SQL Packager I would like to be able to package multiple scripts into package and I would also like to set the order in which these scripts are run. As a user, this would save me a lot of time and make your product work better for me.

Chris Auckland wrote:
Looking at this again, you could create each of the scripts first using SQL Compare (and data compare for the data), and then package the set of scripts using SQL Packager, then you could accomplish this using a single package.

e.g.

(If you want to package a new install, use SQL Compare against a blank database.)

1. Create the script for the fulltext catalogs / tables with fulltext indexes
2. Create the script for other schema objects
3. Create data scripts using SQL Data Comapre
4. Copy them all into a single sequential .sql file
5. Use SQL Packager 6 to package the complete script
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group