I just setup my server with win2k3 sp1 and ALL the latest patches, plus
sql 2004 standard sp4.
I keep getting this error on a table with 39000 records where I am
running a basic wildcard CONTAINS fulltext query for "cer*"
Server: Msg 7643, Level 16, State 1, Line 1
Your search generated too many results. Please perform a more specific
search.
There should be about 30000 records.
I noticed on technet that this was a problem pre sp2 in sql, but was
since patched. Has the bug recently been re-introduced in some combo
of win2k3 and sql patches?
Phadke,
Yes, there was some additional logic added in SP3 that generates the below
error message. SQL FTS is optimized for returning 2000 results per query,
primarily for performance reasons. You may want to re-write your query using
CONTAINSTABLE and use the Top_N_by_Rank parameter to limit the results to
2000 or use a similar TOP restriction in the select list.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<phadke@.gmail.com> wrote in message
news:1129632193.545575.218860@.g47g2000cwa.googlegr oups.com...
>I just setup my server with win2k3 sp1 and ALL the latest patches, plus
> sql 2004 standard sp4.
> I keep getting this error on a table with 39000 records where I am
> running a basic wildcard CONTAINS fulltext query for "cer*"
> Server: Msg 7643, Level 16, State 1, Line 1
> Your search generated too many results. Please perform a more specific
> search.
> There should be about 30000 records.
> I noticed on technet that this was a problem pre sp2 in sql, but was
> since patched. Has the bug recently been re-introduced in some combo
> of win2k3 and sql patches?
>
|||John,
Just to clarify, is this a hard limit of 2000, because I am able to see
the result set for queries that return a con query with 17-18k records
with no problem.
I saw another technote that the problem limit was at approx 20k
records:
http://support.microsoft.com/default...;en-us;Q296456
Thanks for the info,
Aditya
|||Also, is this limitation common to sql 2005?
|||Ok, now I am really confused...I ran a fulltext query for "c*" on a
database on another server. This database has 2.4 Million Records.
This server is Win2k3 (no SP) and SQL 2k SP3.
When I run the query, I get 900,000 records back without an error
message.
|||Aditya,
Yes, this is the KB article that I couldn't find early this morning when in
a rush to get off to work...
Still for performance reasons, it might be best to use Top_N_Rank with
CONTAINSTABLE or is there a specific reason you want to return this many
rows?
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<phadke@.gmail.com> wrote in message
news:1129660216.247521.205300@.g47g2000cwa.googlegr oups.com...
> John,
> Just to clarify, is this a hard limit of 2000, because I am able to see
> the result set for queries that return a con query with 17-18k records
> with no problem.
> I saw another technote that the problem limit was at approx 20k
> records:
> http://support.microsoft.com/default...;en-us;Q296456
> Thanks for the info,
> Aditya
>
|||Aditya,
I need to confirm this with a large table in order to generate the large
results. However, I would suspect that it is still in SQL 2005 until proved
otherwise...
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Aditya Phadke" <phadke@.gmail.com> wrote in message
news:1129660966.529955.176010@.g44g2000cwa.googlegr oups.com...
> Also, is this limitation common to sql 2005?
>
|||Aditya,
Different servers can behavior differently for FTS results based upon the OS
platform (different wordbreakers) and due to different noise word file
contents. In this case, and on this server is the single letter "C" removed
from the language-specific noise word file (noise.enu = US English) for the
specific FT-enable column's "Language for Word Breaker"?
As they say the devil is in the details... ;-)
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Aditya Phadke" <phadke@.gmail.com> wrote in message
news:1129672239.794380.257680@.o13g2000cwo.googlegr oups.com...
> Ok, now I am really confused...I ran a fulltext query for "c*" on a
> database on another server. This database has 2.4 Million Records.
> This server is Win2k3 (no SP) and SQL 2k SP3.
> When I run the query, I get 900,000 records back without an error
> message.
>
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Monday, March 26, 2012
Monday, March 12, 2012
Fresh SQL 2000 to SP4 gives error
Hi,
I'm trying to Service Pack 4 a fresh installation of SQL 2000 (a named instance called 'SQLSERVER2000') and get the error "Installation of the Microsoft Full-Text Search Engine package failed. (-2147467259) 0x80004005 Unspecified Error" towards the end of the process thus I cannot service Pack my fresh installation of SQL 2000. I have done this many times before on other machines, but its not working for me this time.
At http://www.dbforums.com/ ( http://www.dbforums.com/showthread.php?t=1198047 ) someone ran into this problem and mentioned to re-install Microsoft Full-Text Search. I have followed the article http://support.microsoft.com/kb/827449 but run into problems at step 2C. At step 2C it says to start the Microsoft Search service via the Services console, but Microsoft Search was nowhere to be found.
Going back a step to Step 2B it says that all registry keys that were previously-deleted are now available and the previously-deleted 'MSSearch' folder is recreated. I took a look, but both the keys and folder WERE NOT there.
It is a fresh OS installation of MS Windows 2003 Standard SP1, 768MB RAM and is running fine.
Can you please point me in the right direction here?
Brad.
Am experiencing the same problem. Have you come across a solution yet?|||Try this link:http://sqlserver2000.databases.aspfaq.com/what-do-i-need-to-know-about-sql-server-2000-sp4.html|||Had the server rebuilt. Installed SQL 2000 and sp4 prior to any patches, or any other applications (TIVOLI). No problems.
Fresh SQL 2000 to SP4 gives error
Hi,
I'm trying to Service Pack 4 a fresh installation of SQL 2000 (a named instance called 'SQLSERVER2000') and get the error "Installation of the Microsoft Full-Text Search Engine package failed. (-2147467259) 0x80004005 Unspecified Error" towards the end of the process thus I cannot service Pack my fresh installation of SQL 2000. I have done this many times before on other machines, but its not working for me this time.
At http://www.dbforums.com/ ( http://www.dbforums.com/showthread.php?t=1198047 ) someone ran into this problem and mentioned to re-install Microsoft Full-Text Search. I have followed the article http://support.microsoft.com/kb/827449 but run into problems at step 2C. At step 2C it says to start the Microsoft Search service via the Services console, but Microsoft Search was nowhere to be found.
Going back a step to Step 2B it says that all registry keys that were previously-deleted are now available and the previously-deleted 'MSSearch' folder is recreated. I took a look, but both the keys and folder WERE NOT there.
It is a fresh OS installation of MS Windows 2003 Standard SP1, 768MB RAM and is running fine.
Can you please point me in the right direction here?
Brad.
Am experiencing the same problem. Have you come across a solution yet?|||Try this link:http://sqlserver2000.databases.aspfaq.com/what-do-i-need-to-know-about-sql-server-2000-sp4.html|||Had the server rebuilt. Installed SQL 2000 and sp4 prior to any patches, or any other applications (TIVOLI). No problems.
frequent index corruption
Hi All,
I have a table on SQL 2000 (SP4) with about 55k records and was not
having any problems with it for some time. Recently, I am getting
index corruption errors such as:
Could not find the index entry for RID
'3601000001001c0031002d0044004b0058002d0
03800340037003300' in index
page (1:1396706), index ID 3, database <db_name>
I've tried researching on this matter, but there seems to be no clear
explanation on how or why these are happening. I have looked at the
possibility of a hardware problem, but the same set of indexes on two
replication subscribers (from a single publisher) have the corruption.
So it would be quite unlikely that both subscribers, which are
different machines on different locations, would have the same
hardware problem at the same time. The publisher does not have this
problem.
Second, if I drop the corrupt indexes, the errors go away, and if I
recreate them the corruption is consistently present. I did the
dropping and creation a couple of times, and it is very consistent,
which is odd.
I came across KB 822747 (http://support.microsoft.com/kb/822747),
which was quite similar to what I am having since my database is on a
binary collation and the involve indexes have several unicode columns,
but I'm not sure if there is any relationship there. The issue in the
KB was said to be fixed on SP4, but I already got SP4.
DBCC does not return any error, btw.
I hope someone can enlighten me on this or point me to the right
direction.
Thanks,
AramidThis sounds like a case for MS support. I'd run through method#2 in the
stated KB and collect the result. Along with your server info (@.@.version),
it should be a very quick call. You will need a credit to open a case, but
shouldn't be charged if it's indeed a bug.
-oj
"Aramid" <aramid@.hotmail.com> wrote in message
news:ml6d82tca5vf3gr71od5sc8fj5kjp5qtkv@.
4ax.com...
> Hi All,
> I have a table on SQL 2000 (SP4) with about 55k records and was not
> having any problems with it for some time. Recently, I am getting
> index corruption errors such as:
> Could not find the index entry for RID
> '3601000001001c0031002d0044004b0058002d0
03800340037003300' in index
> page (1:1396706), index ID 3, database <db_name>
> I've tried researching on this matter, but there seems to be no clear
> explanation on how or why these are happening. I have looked at the
> possibility of a hardware problem, but the same set of indexes on two
> replication subscribers (from a single publisher) have the corruption.
> So it would be quite unlikely that both subscribers, which are
> different machines on different locations, would have the same
> hardware problem at the same time. The publisher does not have this
> problem.
> Second, if I drop the corrupt indexes, the errors go away, and if I
> recreate them the corruption is consistently present. I did the
> dropping and creation a couple of times, and it is very consistent,
> which is odd.
> I came across KB 822747 (http://support.microsoft.com/kb/822747),
> which was quite similar to what I am having since my database is on a
> binary collation and the involve indexes have several unicode columns,
> but I'm not sure if there is any relationship there. The issue in the
> KB was said to be fixed on SP4, but I already got SP4.
> DBCC does not return any error, btw.
> I hope someone can enlighten me on this or point me to the right
> direction.
> Thanks,
> Aramid
I have a table on SQL 2000 (SP4) with about 55k records and was not
having any problems with it for some time. Recently, I am getting
index corruption errors such as:
Could not find the index entry for RID
'3601000001001c0031002d0044004b0058002d0
03800340037003300' in index
page (1:1396706), index ID 3, database <db_name>
I've tried researching on this matter, but there seems to be no clear
explanation on how or why these are happening. I have looked at the
possibility of a hardware problem, but the same set of indexes on two
replication subscribers (from a single publisher) have the corruption.
So it would be quite unlikely that both subscribers, which are
different machines on different locations, would have the same
hardware problem at the same time. The publisher does not have this
problem.
Second, if I drop the corrupt indexes, the errors go away, and if I
recreate them the corruption is consistently present. I did the
dropping and creation a couple of times, and it is very consistent,
which is odd.
I came across KB 822747 (http://support.microsoft.com/kb/822747),
which was quite similar to what I am having since my database is on a
binary collation and the involve indexes have several unicode columns,
but I'm not sure if there is any relationship there. The issue in the
KB was said to be fixed on SP4, but I already got SP4.
DBCC does not return any error, btw.
I hope someone can enlighten me on this or point me to the right
direction.
Thanks,
AramidThis sounds like a case for MS support. I'd run through method#2 in the
stated KB and collect the result. Along with your server info (@.@.version),
it should be a very quick call. You will need a credit to open a case, but
shouldn't be charged if it's indeed a bug.
-oj
"Aramid" <aramid@.hotmail.com> wrote in message
news:ml6d82tca5vf3gr71od5sc8fj5kjp5qtkv@.
4ax.com...
> Hi All,
> I have a table on SQL 2000 (SP4) with about 55k records and was not
> having any problems with it for some time. Recently, I am getting
> index corruption errors such as:
> Could not find the index entry for RID
> '3601000001001c0031002d0044004b0058002d0
03800340037003300' in index
> page (1:1396706), index ID 3, database <db_name>
> I've tried researching on this matter, but there seems to be no clear
> explanation on how or why these are happening. I have looked at the
> possibility of a hardware problem, but the same set of indexes on two
> replication subscribers (from a single publisher) have the corruption.
> So it would be quite unlikely that both subscribers, which are
> different machines on different locations, would have the same
> hardware problem at the same time. The publisher does not have this
> problem.
> Second, if I drop the corrupt indexes, the errors go away, and if I
> recreate them the corruption is consistently present. I did the
> dropping and creation a couple of times, and it is very consistent,
> which is odd.
> I came across KB 822747 (http://support.microsoft.com/kb/822747),
> which was quite similar to what I am having since my database is on a
> binary collation and the involve indexes have several unicode columns,
> but I'm not sure if there is any relationship there. The issue in the
> KB was said to be fixed on SP4, but I already got SP4.
> DBCC does not return any error, btw.
> I hope someone can enlighten me on this or point me to the right
> direction.
> Thanks,
> Aramid
frequent index corruption
Hi All,
I have a table on SQL 2000 (SP4) with about 55k records and was not
having any problems with it for some time. Recently, I am getting
index corruption errors such as:
Could not find the index entry for RID
'3601000001001c0031002d0044004b0058002d003800340037003300' in index
page (1:1396706), index ID 3, database <db_name>
I've tried researching on this matter, but there seems to be no clear
explanation on how or why these are happening. I have looked at the
possibility of a hardware problem, but the same set of indexes on two
replication subscribers (from a single publisher) have the corruption.
So it would be quite unlikely that both subscribers, which are
different machines on different locations, would have the same
hardware problem at the same time. The publisher does not have this
problem.
Second, if I drop the corrupt indexes, the errors go away, and if I
recreate them the corruption is consistently present. I did the
dropping and creation a couple of times, and it is very consistent,
which is odd.
I came across KB 822747 (http://support.microsoft.com/kb/822747),
which was quite similar to what I am having since my database is on a
binary collation and the involve indexes have several unicode columns,
but I'm not sure if there is any relationship there. The issue in the
KB was said to be fixed on SP4, but I already got SP4.
DBCC does not return any error, btw.
I hope someone can enlighten me on this or point me to the right
direction.
Thanks,
AramidThis sounds like a case for MS support. I'd run through method#2 in the
stated KB and collect the result. Along with your server info (@.@.version),
it should be a very quick call. You will need a credit to open a case, but
shouldn't be charged if it's indeed a bug.
--
-oj
"Aramid" <aramid@.hotmail.com> wrote in message
news:ml6d82tca5vf3gr71od5sc8fj5kjp5qtkv@.4ax.com...
> Hi All,
> I have a table on SQL 2000 (SP4) with about 55k records and was not
> having any problems with it for some time. Recently, I am getting
> index corruption errors such as:
> Could not find the index entry for RID
> '3601000001001c0031002d0044004b0058002d003800340037003300' in index
> page (1:1396706), index ID 3, database <db_name>
> I've tried researching on this matter, but there seems to be no clear
> explanation on how or why these are happening. I have looked at the
> possibility of a hardware problem, but the same set of indexes on two
> replication subscribers (from a single publisher) have the corruption.
> So it would be quite unlikely that both subscribers, which are
> different machines on different locations, would have the same
> hardware problem at the same time. The publisher does not have this
> problem.
> Second, if I drop the corrupt indexes, the errors go away, and if I
> recreate them the corruption is consistently present. I did the
> dropping and creation a couple of times, and it is very consistent,
> which is odd.
> I came across KB 822747 (http://support.microsoft.com/kb/822747),
> which was quite similar to what I am having since my database is on a
> binary collation and the involve indexes have several unicode columns,
> but I'm not sure if there is any relationship there. The issue in the
> KB was said to be fixed on SP4, but I already got SP4.
> DBCC does not return any error, btw.
> I hope someone can enlighten me on this or point me to the right
> direction.
> Thanks,
> Aramid
I have a table on SQL 2000 (SP4) with about 55k records and was not
having any problems with it for some time. Recently, I am getting
index corruption errors such as:
Could not find the index entry for RID
'3601000001001c0031002d0044004b0058002d003800340037003300' in index
page (1:1396706), index ID 3, database <db_name>
I've tried researching on this matter, but there seems to be no clear
explanation on how or why these are happening. I have looked at the
possibility of a hardware problem, but the same set of indexes on two
replication subscribers (from a single publisher) have the corruption.
So it would be quite unlikely that both subscribers, which are
different machines on different locations, would have the same
hardware problem at the same time. The publisher does not have this
problem.
Second, if I drop the corrupt indexes, the errors go away, and if I
recreate them the corruption is consistently present. I did the
dropping and creation a couple of times, and it is very consistent,
which is odd.
I came across KB 822747 (http://support.microsoft.com/kb/822747),
which was quite similar to what I am having since my database is on a
binary collation and the involve indexes have several unicode columns,
but I'm not sure if there is any relationship there. The issue in the
KB was said to be fixed on SP4, but I already got SP4.
DBCC does not return any error, btw.
I hope someone can enlighten me on this or point me to the right
direction.
Thanks,
AramidThis sounds like a case for MS support. I'd run through method#2 in the
stated KB and collect the result. Along with your server info (@.@.version),
it should be a very quick call. You will need a credit to open a case, but
shouldn't be charged if it's indeed a bug.
--
-oj
"Aramid" <aramid@.hotmail.com> wrote in message
news:ml6d82tca5vf3gr71od5sc8fj5kjp5qtkv@.4ax.com...
> Hi All,
> I have a table on SQL 2000 (SP4) with about 55k records and was not
> having any problems with it for some time. Recently, I am getting
> index corruption errors such as:
> Could not find the index entry for RID
> '3601000001001c0031002d0044004b0058002d003800340037003300' in index
> page (1:1396706), index ID 3, database <db_name>
> I've tried researching on this matter, but there seems to be no clear
> explanation on how or why these are happening. I have looked at the
> possibility of a hardware problem, but the same set of indexes on two
> replication subscribers (from a single publisher) have the corruption.
> So it would be quite unlikely that both subscribers, which are
> different machines on different locations, would have the same
> hardware problem at the same time. The publisher does not have this
> problem.
> Second, if I drop the corrupt indexes, the errors go away, and if I
> recreate them the corruption is consistently present. I did the
> dropping and creation a couple of times, and it is very consistent,
> which is odd.
> I came across KB 822747 (http://support.microsoft.com/kb/822747),
> which was quite similar to what I am having since my database is on a
> binary collation and the involve indexes have several unicode columns,
> but I'm not sure if there is any relationship there. The issue in the
> KB was said to be fixed on SP4, but I already got SP4.
> DBCC does not return any error, btw.
> I hope someone can enlighten me on this or point me to the right
> direction.
> Thanks,
> Aramid
Sunday, February 26, 2012
Free Text Search
We have two SQL Server 2000 servers with SP4 loaded. We have copied a
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on
"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on
"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
Free Text Search
We have two SQL Server 2000 servers with SP4 loaded. We have copied a
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
--
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> > We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> > database from one to the other. The free text search runs on the original
> > server and produces results but on the new server it runs but produces a
> > nil
> > return.
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> >
> > Can anyone offer any help?
> >
> > --
> > Confused but battling on
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
--
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> > We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> > database from one to the other. The free text search runs on the original
> > server and produces results but on the new server it runs but produces a
> > nil
> > return.
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> >
> > Can anyone offer any help?
> >
> > --
> > Confused but battling on
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
Free Text Search
We have two SQL Server 2000 servers with SP4 loaded. We have copied a
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text searc
h
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text searc
h
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>
Subscribe to:
Posts (Atom)