Showing posts with label full-text. Show all posts
Showing posts with label full-text. Show all posts

Friday, March 30, 2012

Moving an SBS SharePoint Database

I wanted to setup SharePoint services but there are a couple issues
that I need some help with. I need to have the full-text search turned
on and I also have a space issue on the DC.
So, for the full-text search I need to upgrade the WMSDE to SQL Server.
But because I don't have the space on my DC I need to move the
database to another server. Fortunatly the other server already has
SQL 2000 installed on it.
My questions are then, can I infact move the databse to the second
server and if I can do I need to upgrade the DC to SQL 2000 before I
move the database so the full-text feature is supported?
EvanNot using the SBS SQL license - they have to be on the same machine..
FWIW - there are much better search engines then the full text search.
There are a lot of performance trade-offs for having the FTS engine
enabled on a database (or WSS site) of any size. Watch the CPU usage
when the MS Search Service starts up and you'll see what I mean.|||Thanks you for responding, sorry, I've been away for a little while.
We have SQL 2000 installed on the other server to run some accounting
software. Could we not use an instance of that for SharePoint, and
have SharePoint point to the other server?
Evan

Moving an SBS SharePoint Database

I wanted to setup SharePoint services but there are a couple issues
that I need some help with. I need to have the full-text search turned
on and I also have a space issue on the DC.
So, for the full-text search I need to upgrade the WMSDE to SQL Server.
But because I don't have the space on my DC I need to move the
database to another server. Fortunatly the other server already has
SQL 2000 installed on it.
My questions are then, can I infact move the databse to the second
server and if I can do I need to upgrade the DC to SQL 2000 before I
move the database so the full-text feature is supported?
EvanNot using the SBS SQL license - they have to be on the same machine..
FWIW - there are much better search engines then the full text search.
There are a lot of performance trade-offs for having the FTS engine
enabled on a database (or WSS site) of any size. Watch the CPU usage
when the MS Search Service starts up and you'll see what I mean.|||Thanks you for responding, sorry, I've been away for a little while.
We have SQL 2000 installed on the other server to run some accounting
software. Could we not use an instance of that for SharePoint, and
have SharePoint point to the other server?
Evan

Wednesday, March 28, 2012

Moving a Full-Text Catalog from a single server to a Cluster

Hi,
I was wondering if anyone could point me in the right direction with a
problem I'm having moving a full-text catalog from one server to
another.
In a nutshell, I want to take a database with full-text indexing
enabled and move it and the catalog to a new server. The existing
system is a single server build but the new one will be clustered in
an active/passive configuration which complicates things a little.
Obviously I've read and tried the instructions in Q240867 but this
doesnt seem to have worked and a full population starts as soon as I
enable the funtionality again (so either I'm doing something wrong or
it's not possible to do it).
I've tried to follow the instructions on each of the nodes in the
cluster and on the virtual server but it doesnt seem to work.
Any help anyone can give me in this would be really appreciated.
Regards,
Mike
Are the database IDs identical on the server you are moving the catalogs to?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mike" <mike.metcalf@.4projects.com> wrote in message
news:678e073d.0410180336.37c55f97@.posting.google.c om...
> Hi,
> I was wondering if anyone could point me in the right direction with a
> problem I'm having moving a full-text catalog from one server to
> another.
> In a nutshell, I want to take a database with full-text indexing
> enabled and move it and the catalog to a new server. The existing
> system is a single server build but the new one will be clustered in
> an active/passive configuration which complicates things a little.
> Obviously I've read and tried the instructions in Q240867 but this
> doesnt seem to have worked and a full population starts as soon as I
> enable the funtionality again (so either I'm doing something wrong or
> it's not possible to do it).
> I've tried to follow the instructions on each of the nodes in the
> cluster and on the virtual server but it doesnt seem to work.
> Any help anyone can give me in this would be really appreciated.
> Regards,
> Mike
|||Hi Hillary,
I've had a look and the DBID's are the same (I thought they were but
it's always worth double-checking), the only thing that should be
diffent is that the new build will be clustered (the old one isnt) and
the FTDATA directory is being moved from the c: to the shared d: (I've
updated the registry keys to reflect the new location)
What I'm really looking for is someone to tell me where I need to apply
the registry settings I took on the original system to (node 1, node 2,
virtual server, virtual SQL Server or some mix of everything), or
failing that if someone could say if and why it wasn't possible (I'm
fairly sure it is) that would be ok too.
There's probably something different (or extra) that needs doing on a
clustered installation that hasnt been documented yet.
Mike
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Mike,
I researched and wrote the original KB article Q240867 (before it was
modified for SP3) and because you're moving from a non-clustered environment
to a clustered environment, this modified KB article's cluster related
procedures assumes that you are already in a clustered environment before
moving or copying the FT Catalog folder & files.
I'd recommend that you review KB article 812666 - "How to recover a failed
full-text search resource on a clustered instance of SQL Server 2000" at
http://support.microsoft.com/default.aspx?kbid=812666 if re-installation of
FTS is required. If not, I'd recommend that you consider setting up your
clustered environment first and then copy over the SQL000<dbid>000<ftcatid>
folder assuming the same dibd & ftcatid is on your clustered environment. If
this is not possible, then you most likely will have to run a Full
Population and take the hit on a long population period as I'm assuming that
is why you are copying to the new build from the old non-clustered build.
Regards,
John
"Mike Metcalf" <mike.metcalf@.4projects.com> wrote in message
news:uSzxk0StEHA.1400@.TK2MSFTNGP11.phx.gbl...
> Hi Hillary,
> I've had a look and the DBID's are the same (I thought they were but
> it's always worth double-checking), the only thing that should be
> diffent is that the new build will be clustered (the old one isnt) and
> the FTDATA directory is being moved from the c: to the shared d: (I've
> updated the registry keys to reflect the new location)
> What I'm really looking for is someone to tell me where I need to apply
> the registry settings I took on the original system to (node 1, node 2,
> virtual server, virtual SQL Server or some mix of everything), or
> failing that if someone could say if and why it wasn't possible (I'm
> fairly sure it is) that would be ok too.
> There's probably something different (or extra) that needs doing on a
> clustered installation that hasnt been documented yet.
> Mike
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi John,
Thanks for your suggestions, I had a look at the article over the
weekend and a combination of the two led me to the correct solution,
I've tested it 3 times and it's worked each time so I know it's not a
fluke.
Thanks again,
Mike
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You're welcome, Mike,
I guess a little bit of persistence goes a long way!
John
"Mike Metcalf" <mike.metcalf@.4projects.com> wrote in message
news:#49OMjmuEHA.2832@.tk2msftngp13.phx.gbl...
> Hi John,
> Thanks for your suggestions, I had a look at the article over the
> weekend and a combination of the two led me to the correct solution,
> I've tested it 3 times and it's worked each time so I know it's not a
> fluke.
> Thanks again,
> Mike
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
>
sql

Friday, March 9, 2012

Move FTC from SS2K to SS2K5

Morning,

Here is my scenario:

I have a SQL Server 2000 server with 10 clients.

Each client has 5 Full-Text Catalogs. For ease of explanation let’s call the FTCs C1 thru C5.

Now each client’s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.

I need to move the clients to our new SQL Server 2005 Enterprise server.

I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.

So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.

Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?

If so, how do I overcome this event?

Thanks for any and all help!

JJKusch,

In SQL Server 2005, the format of full-text catalogs has changed significantly. This change requires all full-text catalogs from previous versions of SQL Server to be rebuilt.

Move FTC from SS2K to SS2K5

Morning,

Here is my scenario:

I have a SQL Server 2000 server with 10 clients.

Each client has 5 Full-Text Catalogs. For ease of explanation let’s call the FTCs C1 thru C5.

Now each client’s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.

I need to move the clients to our new SQL Server 2005 Enterprise server.

I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.

So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.

Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?

If so, how do I overcome this event?

Thanks for any and all help!

JJKusch,

In SQL Server 2005, the format of full-text catalogs has changed significantly. This change requires all full-text catalogs from previous versions of SQL Server to be rebuilt.