April 15, 2008 at 7:45 am
Hi everyone,
I'm a newbie to SQL Server, and in the process of migrating SQL Server from 2000 to 2005. I ran the Upgrade Advisor and it recommended to "increase the database size to accommodate DOCID map" for one of our databases that has full-text indexes.
I went to the affected tables and calculated the space required based on the table's primary key index, and therefore increased the database size based on the result. But then, when I re-launch the UA Wizard it still shows the same recommendation.
Did someone ever deal with this issue? Can someone tell me how to point out the Full-text Keys in a table? And then how to calculate its size?
Thank you,
Karina
April 15, 2008 at 10:42 am
Generally speaking, I think the best way to migrate full text indexes is to drop the 2000 ones and rebuild them in 2005 as if they were completely new. I haven't actually done this, but I think that's what I've read.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
April 16, 2008 at 1:05 pm
Thank you GSquared, for your answer.
What would be the best way to do that:
- Generate the full-text indexes creation script in SQL 2000
- Drop full-text indexes
- migrate
- Run the full-text indexes creation script in SQL 2005. (is the syntax the same?)
Karina
April 16, 2008 at 1:53 pm
Since I haven't done a migration from 2000 to 2005 that included full-text indexes, all I can say is that your best bet it to go to MSDN and/or Books Online, and read up on the subject.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply