I used packager plus (5.0.0.949) to create an exe. I then used this exe to upgrade an existing database (SQL2000). I receive a full-text search not enabled error.
However we don't use any full-text indexes. This happens on about 3 or 4 tables in which we changed the length of a varchar column.
This was from the log:
<ERROR> 5/21/2009 10:17:42 AM...Cannot alter column [dbo].[IssueTypes].[TextValue] 5/21/2009 10:17:42 AM...Cannot alter column [dbo].[IssueTypes].[TextValue] 5/21/2009 10:17:42 AM...Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. 5/21/2009 10:17:42 AM...</ERROR>
Just wondering if there is something im missing. Should I unchecck the full text catalogs during the configuration options?
I also used the model database as the template, not sure if that causes a problem.
What is defined against those columns on the source database that you originally created the exe from?
The most likely explanation is that they have been marked for full text indexing at some point and the installer is attempting to replicate that attribute on the target database which doesn't have full text indexing enabled...
The source database is scripts in the file system. I have attached the table script in question
IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'[dbo].[IssueSettlementsDataPhile]') AND OBJECTPROPERTY(id, N'IsTable') = 1) DROP TABLE [dbo].[IssueSettlementsDataPhile] GO
SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO
It doesn't look like you have fulltext defined but it is a separate command:
CREATE FULLTEXT INDEX ON....
So it might be in another script - could you do a text search of your scripts directory to make sure nothing is defined please?
If there defintely isn't anything there then could you upgrade to the latest version of DB Ghost and recreate the installer and retry please? If that still fails then we can try to reproduce the issue here and get it into the issues system.