Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / January 2007

Tip: Looking for answers? Try searching our database.

Default FTData Location

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
CarolinaKB - 25 Jan 2007 22:10 GMT
I recently redistributed our database data files from one large VRAID5 disk
(G:) to 3 VRAID1 disks (T:, U:, V:).  At this point, I have moved everything
(including SQLAgent output & log files, job logs, tlogs, backups) EXCEPT:

1) FTDATA folder and its contents;
2) distmdl.mdf and distmdl.ldf

We do not use Full Text Searching, nor do we use replication.  However, in
the interest of not leaving a ticking time bomb for someone who might later
want to use these features, I'd like to move these to drive T:.

Question 1: Is there an easy way to change the default location for FT
catalogs since I'm not even using full text right now?  I found
http://support.microsoft.com/kb/240867/en-us for FTDATA but was hoping for a
simpler solution.

Question 2: How do I tell SQL where distmdl is if I enable replication?  The
database doesn't appear to be attached in Ent Manager.
Hilary Cotter - 26 Jan 2007 03:35 GMT
1) http://support.microsoft.com/kb/817296
2) when you create the distribution database you will be prompted where you
want to place the database files.

Signature

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

>I recently redistributed our database data files from one large VRAID5 disk
> (G:) to 3 VRAID1 disks (T:, U:, V:).  At this point, I have moved
[quoted text clipped - 18 lines]
> The
> database doesn't appear to be attached in Ent Manager.
CarolinaKB - 28 Jan 2007 01:37 GMT
Thanks for the info.

> 1) http://support.microsoft.com/kb/817296
> 2) when you create the distribution database you will be prompted where you
[quoted text clipped - 22 lines]
> > The
> > database doesn't appear to be attached in Ent Manager.
CarolinaKB - 29 Jan 2007 13:43 GMT
Okay, one other question.  What do I do with the existing distmdl?  Do I
simply move the .mdf & .ldf whereever I want to, or delete them?

> 1) http://support.microsoft.com/kb/817296
> 2) when you create the distribution database you will be prompted where you
[quoted text clipped - 22 lines]
> > The
> > database doesn't appear to be attached in Ent Manager.
Hilary Cotter - 29 Jan 2007 14:57 GMT
do the following sp_helpdistributor  and sp_helpdistributiondb. These will
tell you if the distributor is installed and if the distribution database
files you see are the ones in use.

DO NOT DELETE distmdl.mdf or distmdl.ldf as these are the model distribution
database files. If you delete these you won't be able to install replication
again.
Signature

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

> Okay, one other question.  What do I do with the existing distmdl?  Do I
> simply move the .mdf & .ldf whereever I want to, or delete them?
[quoted text clipped - 30 lines]
>> > The
>> > database doesn't appear to be attached in Ent Manager.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.