Looking for info on the noted error message received:
General network error. Check your network documentation.
[SQLSTATE 42000] (Error 11). The step failed.
Basic file import INSERT job failed on data warehouse.
No reported network or backup problems ...
Thanks in advance,
ericggordonHi Ericggordon,
Thanks for your post. What is the version of SQL Server (Service Pack)? I
am not quite clear the problem on your side, Please provide more
information so that I can narrow down this issue.
1. How does this problem occur? Can you describe it in detail?
2. How often did the job fail? Do you mean that the job fails every time?
How is the issue going on your side now?
3. What did the job do? Please describe it in detail.
4. It seems that the INSERT job failed, could you run the job manually?
Does any error occur?
Please check to see if the following article helps.
317852 FIX: An INSERT May Fail with a 3624 Error Message After a Failed
Attempt
http://support.microsoft.com/?id=317852
I am standing by for your response.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Showing posts with label message. Show all posts
Showing posts with label message. Show all posts
Thursday, March 29, 2012
General network error.
This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>
Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.
|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolved.
I also wanted to ask you - when you rebuild the server did it have the same configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we started to have this problem from that day on. Microsoft is working on it but this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...
>
>
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>
Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.
|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolved.
I also wanted to ask you - when you rebuild the server did it have the same configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we started to have this problem from that day on. Microsoft is working on it but this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...
>
>
General network error.
This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolv
ed.
I also wanted to ask you - when you rebuild the server did it have the same
configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we
started to have this problem from that day on. Microsoft is working on it b
ut this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...
>
>sql
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolv
ed.
I also wanted to ask you - when you rebuild the server did it have the same
configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we
started to have this problem from that day on. Microsoft is working on it b
ut this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...
>
>sql
Tuesday, March 27, 2012
General network error
Hi,
I'am working with a merge Replication and a pull Subscription on demand from
the client
I'am getting this message error from a vb.net Windows Application
DATE=2006-03-15 15:18:34
ERROR=SyncJMI.CDatabaseUtils.LoadDataTable failed.
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior)
at
System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand
command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at SyncJMI.CDatabaseUtils.LoadDataTable(SqlCommand cmd, DataTable& dt,
Boolean verifyDb)
This is the first time a get this error
After doing some research on the Web, Ifind that if i put Polling=False in
my connection string this error dont appear anymore.
I'am not very confortable to deactivate the pooling for performance reason
Is this solution the real solution ?
Also by deactivating the pooling, does this deactivationis done on the
client side or server side?
It is a better idea to maximise the size of the pool instead of turn it off?
Thanks in advance!
I'm interested in any articles you can provide which show the connection
between General network error and connection pooling - haven't heard of this
as a solution myself before. Usually these issues concern breaks in
connectivity. If persistant then the network needs to be investigated. If
not, then simply restarting the merge agent suffices.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||My understanding is that connection pooling has advantages for other
connections using the same connection string properties, ie uid, pwd, or
trusted authentication. So the first connection in will spin up the min pool
size connections (default 1) and after it has complete its work subsequenct
connections with the same connection string can use that open connection.
What puzzles me is why are you using ado.net as opposed to the activex merge
replication objects? Its not clear to me that this is replication related or
ADO related. It seems to be barfing on LoadDataTable which doesn't sound
replication related.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:93AF91D3-59F6-4F1A-8DB3-A91C38DEDD57@.microsoft.com...
> Hi,
> I'am working with a merge Replication and a pull Subscription on demand
> from
> the client
> I'am getting this message error from a vb.net Windows Application
> DATE=2006-03-15 15:18:34
> ERROR=SyncJMI.CDatabaseUtils.LoadDataTable failed.
> System.Data.SqlClient.SqlException: General network error. Check your
> network documentation.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
> behavior)
> at
> System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior
> behavior)
> at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
> startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
> CommandBehavior behavior)
> at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand
> command, CommandBehavior behavior)
> at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
> at SyncJMI.CDatabaseUtils.LoadDataTable(SqlCommand cmd, DataTable& dt,
> Boolean verifyDb)
>
> This is the first time a get this error
> After doing some research on the Web, Ifind that if i put Polling=False
> in
> my connection string this error dont appear anymore.
> I'am not very confortable to deactivate the pooling for performance reason
> Is this solution the real solution ?
> Also by deactivating the pooling, does this deactivationis done on the
> client side or server side?
> It is a better idea to maximise the size of the pool instead of turn it
> off?
> Thanks in advance!
>
>
>
>
>
|||Let me explain,
We use a vb.Net application that execute some script,copy files,update
version of my vb.net application and so on.
After all update are up to date I call the pull subscription that update all
the records in the database
My application is there for maintenance purpose and for synchronisation of
the database
So the General Network error could arrive during an the execution of a
script like a store procedure etc... that have nothing to do with the
replication.
Still have the problem with the pooling
We have develop many application for customer and it is the first time i got
this error.
Hope this help you
"Hilary Cotter" wrote:
> My understanding is that connection pooling has advantages for other
> connections using the same connection string properties, ie uid, pwd, or
> trusted authentication. So the first connection in will spin up the min pool
> size connections (default 1) and after it has complete its work subsequenct
> connections with the same connection string can use that open connection.
> What puzzles me is why are you using ado.net as opposed to the activex merge
> replication objects? Its not clear to me that this is replication related or
> ADO related. It seems to be barfing on LoadDataTable which doesn't sound
> replication related.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:93AF91D3-59F6-4F1A-8DB3-A91C38DEDD57@.microsoft.com...
>
>
|||did you monitor your connection pooling objects? This will reveal what if
your pool is exhausted.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:AE292989-2D5B-4A66-B8CF-EFD222B48808@.microsoft.com...[vbcol=seagreen]
> Let me explain,
> We use a vb.Net application that execute some script,copy files,update
> version of my vb.net application and so on.
> After all update are up to date I call the pull subscription that update
> all
> the records in the database
> My application is there for maintenance purpose and for synchronisation of
> the database
> So the General Network error could arrive during an the execution of a
> script like a store procedure etc... that have nothing to do with the
> replication.
> Still have the problem with the pooling
> We have develop many application for customer and it is the first time i
> got
> this error.
> Hope this help you
>
>
>
>
> "Hilary Cotter" wrote:
I'am working with a merge Replication and a pull Subscription on demand from
the client
I'am getting this message error from a vb.net Windows Application
DATE=2006-03-15 15:18:34
ERROR=SyncJMI.CDatabaseUtils.LoadDataTable failed.
System.Data.SqlClient.SqlException: General network error. Check your
network documentation.
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior)
at
System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand
command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at SyncJMI.CDatabaseUtils.LoadDataTable(SqlCommand cmd, DataTable& dt,
Boolean verifyDb)
This is the first time a get this error
After doing some research on the Web, Ifind that if i put Polling=False in
my connection string this error dont appear anymore.
I'am not very confortable to deactivate the pooling for performance reason
Is this solution the real solution ?
Also by deactivating the pooling, does this deactivationis done on the
client side or server side?
It is a better idea to maximise the size of the pool instead of turn it off?
Thanks in advance!
I'm interested in any articles you can provide which show the connection
between General network error and connection pooling - haven't heard of this
as a solution myself before. Usually these issues concern breaks in
connectivity. If persistant then the network needs to be investigated. If
not, then simply restarting the merge agent suffices.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||My understanding is that connection pooling has advantages for other
connections using the same connection string properties, ie uid, pwd, or
trusted authentication. So the first connection in will spin up the min pool
size connections (default 1) and after it has complete its work subsequenct
connections with the same connection string can use that open connection.
What puzzles me is why are you using ado.net as opposed to the activex merge
replication objects? Its not clear to me that this is replication related or
ADO related. It seems to be barfing on LoadDataTable which doesn't sound
replication related.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:93AF91D3-59F6-4F1A-8DB3-A91C38DEDD57@.microsoft.com...
> Hi,
> I'am working with a merge Replication and a pull Subscription on demand
> from
> the client
> I'am getting this message error from a vb.net Windows Application
> DATE=2006-03-15 15:18:34
> ERROR=SyncJMI.CDatabaseUtils.LoadDataTable failed.
> System.Data.SqlClient.SqlException: General network error. Check your
> network documentation.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior
> behavior)
> at
> System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior
> behavior)
> at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
> startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
> CommandBehavior behavior)
> at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand
> command, CommandBehavior behavior)
> at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
> at SyncJMI.CDatabaseUtils.LoadDataTable(SqlCommand cmd, DataTable& dt,
> Boolean verifyDb)
>
> This is the first time a get this error
> After doing some research on the Web, Ifind that if i put Polling=False
> in
> my connection string this error dont appear anymore.
> I'am not very confortable to deactivate the pooling for performance reason
> Is this solution the real solution ?
> Also by deactivating the pooling, does this deactivationis done on the
> client side or server side?
> It is a better idea to maximise the size of the pool instead of turn it
> off?
> Thanks in advance!
>
>
>
>
>
|||Let me explain,
We use a vb.Net application that execute some script,copy files,update
version of my vb.net application and so on.
After all update are up to date I call the pull subscription that update all
the records in the database
My application is there for maintenance purpose and for synchronisation of
the database
So the General Network error could arrive during an the execution of a
script like a store procedure etc... that have nothing to do with the
replication.
Still have the problem with the pooling
We have develop many application for customer and it is the first time i got
this error.
Hope this help you
"Hilary Cotter" wrote:
> My understanding is that connection pooling has advantages for other
> connections using the same connection string properties, ie uid, pwd, or
> trusted authentication. So the first connection in will spin up the min pool
> size connections (default 1) and after it has complete its work subsequenct
> connections with the same connection string can use that open connection.
> What puzzles me is why are you using ado.net as opposed to the activex merge
> replication objects? Its not clear to me that this is replication related or
> ADO related. It seems to be barfing on LoadDataTable which doesn't sound
> replication related.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:93AF91D3-59F6-4F1A-8DB3-A91C38DEDD57@.microsoft.com...
>
>
|||did you monitor your connection pooling objects? This will reveal what if
your pool is exhausted.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:AE292989-2D5B-4A66-B8CF-EFD222B48808@.microsoft.com...[vbcol=seagreen]
> Let me explain,
> We use a vb.Net application that execute some script,copy files,update
> version of my vb.net application and so on.
> After all update are up to date I call the pull subscription that update
> all
> the records in the database
> My application is there for maintenance purpose and for synchronisation of
> the database
> So the General Network error could arrive during an the execution of a
> script like a store procedure etc... that have nothing to do with the
> replication.
> Still have the problem with the pooling
> We have develop many application for customer and it is the first time i
> got
> this error.
> Hope this help you
>
>
>
>
> "Hilary Cotter" wrote:
Sunday, February 19, 2012
Fulltext search "IT manager"
i remove "IT" from noise word and rebuild fulltext
and when i query it won't give error message anymore "Informational: The
full-text search condition contained noise word(s)."
but it return no result
any clue?
SELECT top 10 j.position
from myjob j (NOLOCK)
INNER JOIN CONTAINSTABLE(job,position,'"IT Manager"') ft ON ft.[key] =
j.job_id
You need to rebuild the catalogs after removing IT from the noise word
lists.
http://www.zetainteractive.com - Shift Happens!
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
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:84274EF1-758C-458F-AD83-793104B0FBD6@.microsoft.com...
>i remove "IT" from noise word and rebuild fulltext
> and when i query it won't give error message anymore "Informational: The
> full-text search condition contained noise word(s)."
> but it return no result
> any clue?
>
> SELECT top 10 j.position
> from myjob j (NOLOCK)
> INNER JOIN CONTAINSTABLE(job,position,'"IT Manager"') ft ON ft.[key] =
> j.job_id
>
and when i query it won't give error message anymore "Informational: The
full-text search condition contained noise word(s)."
but it return no result
any clue?
SELECT top 10 j.position
from myjob j (NOLOCK)
INNER JOIN CONTAINSTABLE(job,position,'"IT Manager"') ft ON ft.[key] =
j.job_id
You need to rebuild the catalogs after removing IT from the noise word
lists.
http://www.zetainteractive.com - Shift Happens!
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
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:84274EF1-758C-458F-AD83-793104B0FBD6@.microsoft.com...
>i remove "IT" from noise word and rebuild fulltext
> and when i query it won't give error message anymore "Informational: The
> full-text search condition contained noise word(s)."
> but it return no result
> any clue?
>
> SELECT top 10 j.position
> from myjob j (NOLOCK)
> INNER JOIN CONTAINSTABLE(job,position,'"IT Manager"') ft ON ft.[key] =
> j.job_id
>
Subscribe to:
Posts (Atom)