Friday, February 24, 2012

can't move file for full-text index

Hi,
I need to move the file for my full-text catalog to a different drive due to
space issues. I've tried the following:
ALTER DATABASE mailarchivedec05
MODIFY FILE (NAME = MailArchiver3, filename = 'F:\FTDATA')
But get an error:
Server: Msg 5037, Level 16, State 1, Line 1
MODIFY FILE failed. Do not specify physical name.
According to the posting below I should take the database first offline, but
that gives a different error message about the db being offline.
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=full-text+alter&dg=&cat=en-us-technet-sqlserv&lang=en&cr=US&pt=261BA873-F3AB-420E-96D6-E3004596A551&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us
Any other ideas? Thanks.
Panos.
Yes, it should be the logical name. Here is an example of how to do it.
1) determine the logical name of your full-text catalog file. Issue
the following command:
SELECT name FROM SYS.DATABASE_FILES WHERE TYPE_DESC='FULLTEXT'
Note the value returned in the name column. This is your logical name for
your full-text catalog. It will look something like this:
sysft_MyCatalogName where MyCatalogName is the name of your catalog.
2) Issue the below command:
ALTER DATABASE database_name SET OFFLINE
3) Stop Full-Text Search
4) Move the full-text catalog to the new location
5) Restart Full-Text Search
6) Issue the below command:
ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME =
'new_path')
Where new_path is the new path to where you have moved your catalog.
7) Issue the below command:
ALTER DATABASE database_name SET ONLINE
You are now ready to query your full-text catalogs again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
message news:CAB627A0-C3AE-44B7-B12F-F1D98643E6F6@.microsoft.com...
> Hi,
> I need to move the file for my full-text catalog to a different drive due
> to
> space issues. I've tried the following:
> ALTER DATABASE mailarchivedec05
> MODIFY FILE (NAME = MailArchiver3, filename = 'F:\FTDATA')
> But get an error:
> Server: Msg 5037, Level 16, State 1, Line 1
> MODIFY FILE failed. Do not specify physical name.
> According to the posting below I should take the database first offline,
> but
> that gives a different error message about the db being offline.
> http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=full-text+alter&dg=&cat=en-us-technet-sqlserv&lang=en&cr=US&pt=261BA873-F3AB-420E-96D6-E3004596A551&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us
> Any other ideas? Thanks.
> Panos.
|||Hilary,
It still doesn't work. By the way I am using 2000 not 2005, does it make any
difference? For example the command SELECT name FROM SYS.DATABASE_FILES
WHERE TYPE_DESC='FULLTEXT'
does't work. But I am sure I have the right logical name for my index.
I've managed to physically move the files as in step 4 but when the issue
the alter database command I still get the same error message. It doesn't
also like it when the database is offline, gives me an error.
Any other ideas? Thanks.
Panos.
"Hilary Cotter" wrote:

> Yes, it should be the logical name. Here is an example of how to do it.
> 1) determine the logical name of your full-text catalog file. Issue
> the following command:
> SELECT name FROM SYS.DATABASE_FILES WHERE TYPE_DESC='FULLTEXT'
> Note the value returned in the name column. This is your logical name for
> your full-text catalog. It will look something like this:
> sysft_MyCatalogName where MyCatalogName is the name of your catalog.
> 2) Issue the below command:
> ALTER DATABASE database_name SET OFFLINE
> 3) Stop Full-Text Search
> 4) Move the full-text catalog to the new location
> 5) Restart Full-Text Search
> 6) Issue the below command:
> ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME =
> 'new_path')
> Where new_path is the new path to where you have moved your catalog.
> 7) Issue the below command:
> ALTER DATABASE database_name SET ONLINE
> You are now ready to query your full-text catalogs again.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
> message news:CAB627A0-C3AE-44B7-B12F-F1D98643E6F6@.microsoft.com...
>
>
|||I did not realize you were using SQL 2000. In this case follow these steps:
http://support.microsoft.com/kb/240867
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
message news:153D7F5D-76C4-45D2-835B-B0AB382DDD7B@.microsoft.com...[vbcol=seagreen]
> Hilary,
> It still doesn't work. By the way I am using 2000 not 2005, does it make
> any
> difference? For example the command SELECT name FROM SYS.DATABASE_FILES
> WHERE TYPE_DESC='FULLTEXT'
> does't work. But I am sure I have the right logical name for my index.
> I've managed to physically move the files as in step 4 but when the issue
> the alter database command I still get the same error message. It doesn't
> also like it when the database is offline, gives me an error.
> Any other ideas? Thanks.
> Panos.
>
> "Hilary Cotter" wrote:
|||That worked fine. Thanks.
"Hilary Cotter" wrote:

> I did not realize you were using SQL 2000. In this case follow these steps:
> http://support.microsoft.com/kb/240867
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
> message news:153D7F5D-76C4-45D2-835B-B0AB382DDD7B@.microsoft.com...
>
>

No comments:

Post a Comment