We have 3 databases, one publisher and two subscriber.
Merge-Replication, constantly replicated.
Because of unknown circumstances, the replication process failed for
over 14 days, and the publication had a retention time of 14 days.
I wasn=B4t detected earlier, and now is the great question:
HOW CAN I MERGE MY 3 DATABASES TOGETHER?
Is there a possibility to tell the subscribion, that they are NOT
obsolete?
To create a new snapshot won't work, i get a lot of errors afterwards.
To remove the subscriptions and setup the subscriptions anew, will
procede a well-running merge-replication, but with different data.
What about turning back the system time for a few days?
I would be very glad if you have an idea.
Andreas, you could manually synchronize the data using datacompare from
Redgate then do a nosync initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul Ibison schrieb:
> Andreas, you could manually synchronize the data using datacompare from
> Redgate then do a nosync initialization.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
But SQL DataCompare can either copy from database A to B or from B to
A, but cannot merge, or am I wrong?
And I a dataset exists on site A, but not on B, does that mean, that
the dataset was new on A and should copy to B, or was the dataset
delete on B and should also be deleted on A?
|||there is no way in Merge, there is a way in transactional but its dangerous.
If you do reinitialize it will prompt you to upload changes from the
subscriber first which will send the subscribers changes to the publisher.
I think you need to investigate 1) what is causing the problem which makes
your subscriber go offline 2) what is causing these errors you get after
running the snapshot.
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
"Andreas Lauffer" <alweb01@.online.de> wrote in message
news:1128770684.895595.285420@.g44g2000cwa.googlegr oups.com...
We have 3 databases, one publisher and two subscriber.
Merge-Replication, constantly replicated.
Because of unknown circumstances, the replication process failed for
over 14 days, and the publication had a retention time of 14 days.
I wasnt detected earlier, and now is the great question:
HOW CAN I MERGE MY 3 DATABASES TOGETHER?
Is there a possibility to tell the subscribion, that they are NOT
obsolete?
To create a new snapshot won't work, i get a lot of errors afterwards.
To remove the subscriptions and setup the subscriptions anew, will
procede a well-running merge-replication, but with different data.
What about turning back the system time for a few days?
I would be very glad if you have an idea.
|||Andreas - you're quite right. To get this to work, you'll have to select
which one is the master in terms of updates to the same record on both
sites. If the updates are partitioned, then you can use this tool more
easily, but if there are a lot of conflicts then there is a big problem to
sort out, and only you can decide what is appropriate ie who wins these
conflicts, or in other words, which node is the master.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hillary,
thank you for your answer, but I don=B4t understand exacly what this
means for me.
I use merge-replication, not transactual replication.
What happens, if I reinitialize my databases? Will the subscribers
upload their data then?
What is so dangerous?
|||Unfortunately there is no master. Each of the 3 databases have the same
priority.
I cannot set anything aside.
What about my question:[vbcol=seagreen]
Do you think there is a chance to get a system which synchronizes the
data, without marking the subscibers as "obsolete"?
|||What do you think about this scenario:
1) Deleting the subscriptions
2) New pull Merge Subscriptions => Replication will run again, but with
different data
3) Restore the subscibers databases, state before deleting the
subscriptions
Do you think this will work to synchronize the databases?
If this works, maybe the changes from the publisher were not
transmittet to the subscriters yet, and I have to backup the subscribes
database and restore it as the subscribers database.
MAY THIS WORK?
|||Andreas,
this sounds feasible. You'll probably also need to change the value of the
status flag in sysmergesubscriptions. Alternatively (and probably easier)
you might be able to increase the activation/retention period and change
this flag. I haven't tried either approach and don't have any expired
subscriptions to test, so please let us know how you get on.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Yes, with merge replication when you reinitialize you are prompted to upload
the changes which happened on your subscribers first.
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
"Andreas Lauffer" <alweb01@.online.de> wrote in message
news:1128924652.854174.261410@.g47g2000cwa.googlegr oups.com...
Hillary,
thank you for your answer, but I dont understand exacly what this
means for me.
I use merge-replication, not transactual replication.
What happens, if I reinitialize my databases? Will the subscribers
upload their data then?
What is so dangerous?
Showing posts with label subscription. Show all posts
Showing posts with label subscription. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
Help! Replication jobs fails when it was working fine.
Hello,
I have a push subscription setup to replicate some tables. Initially, this
was setup properly and everything was working perfectly. Until recently, the
jobs started failing even though nothing was changed. The errors do not give
me enough information to find out what the problem is. Can someone give me
some hints or ideas of what to do?
FYI, I've re-generated snapshots and re-initialized the subscriptions but it
still fails.
FIRST ERROR
==============================================
Date4/21/2005 9:01:35 AM
LogJob History (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX)
Job NameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Step ID2
Step NameRun agent.
MessageExecuted as user: xxx\Administrator. The step did not generate any
output. NOTE: The step was retried the requested number of times (10)
without succeeding. The step failed.
Duration00:05:10
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted10
SECOND ERROR
==============================================
Date4/21/2005 9:06:46 AM
LogJob History (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX)
Job NameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Step ID3
Step NameDetect nonlogged agent shutdown.
MessageExecuted as user: NT AUTHORITY\SYSTEM. Replication-Replication
Distribution Subsystem: agent XXXXXXXX for XXXXXXXXXX failed. Executed as
user: Domain\Administrator. The step did not generate any output. NOTE: The
step was retried the requested number of times (10) without succeeding. The
step failed. [SQLSTATE 42000] (Error 14151). The step failed.
Duration00:00:00
Sql Severity18
Sql Message ID14151
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
its hard to say. Can you do logging to see if it reveals anything? also
look for dumps in case there were any access violations.
Follow these instructions to enable logging.
http://support.microsoft.com/default...b;en-us;312292
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
|||Also run profiler on the subscriber, check for blocking, or any exceptions
being thrown.
Donna
"Hilary Cotter" wrote:
> its hard to say. Can you do logging to see if it reveals anything? also
> look for dumps in case there were any access violations.
> Follow these instructions to enable logging.
> http://support.microsoft.com/default...b;en-us;312292
> --
> 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 have a push subscription setup to replicate some tables. Initially, this
was setup properly and everything was working perfectly. Until recently, the
jobs started failing even though nothing was changed. The errors do not give
me enough information to find out what the problem is. Can someone give me
some hints or ideas of what to do?
FYI, I've re-generated snapshots and re-initialized the subscriptions but it
still fails.
FIRST ERROR
==============================================
Date4/21/2005 9:01:35 AM
LogJob History (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX)
Job NameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Step ID2
Step NameRun agent.
MessageExecuted as user: xxx\Administrator. The step did not generate any
output. NOTE: The step was retried the requested number of times (10)
without succeeding. The step failed.
Duration00:05:10
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted10
SECOND ERROR
==============================================
Date4/21/2005 9:06:46 AM
LogJob History (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX)
Job NameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Step ID3
Step NameDetect nonlogged agent shutdown.
MessageExecuted as user: NT AUTHORITY\SYSTEM. Replication-Replication
Distribution Subsystem: agent XXXXXXXX for XXXXXXXXXX failed. Executed as
user: Domain\Administrator. The step did not generate any output. NOTE: The
step was retried the requested number of times (10) without succeeding. The
step failed. [SQLSTATE 42000] (Error 14151). The step failed.
Duration00:00:00
Sql Severity18
Sql Message ID14151
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
its hard to say. Can you do logging to see if it reveals anything? also
look for dumps in case there were any access violations.
Follow these instructions to enable logging.
http://support.microsoft.com/default...b;en-us;312292
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
|||Also run profiler on the subscriber, check for blocking, or any exceptions
being thrown.
Donna
"Hilary Cotter" wrote:
> its hard to say. Can you do logging to see if it reveals anything? also
> look for dumps in case there were any access violations.
> Follow these instructions to enable logging.
> http://support.microsoft.com/default...b;en-us;312292
> --
> 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
>
Wednesday, March 21, 2012
HELP! Issue creating subscription
We have been creating the initial subscriptions the same way for years
(sp_addmergepullsubscription_agent). Our FTP server is the same as well.
Yesterday I ran into a strange situation on one client (3 subscribers to one
database at 3 different locations, 2 with the same ISP). Each have SQL
Server 2005 Developer's Editon.
As soon as the process to connect to our FTP and download the snapshot we
get the following error:
************************************************** *******
Error messages:
The schema script '' could not be propagated to the subscriber. (Source:
MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
The process could not retrieve file
'OURSERVER_CLIENT_DBNAME_CLIENT_DBNAME\20071105123 250\snapshot.cab' from the
FTP site '11.222.33.44'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20033) Get help:
http://help/MSSQL_REPL20033
200 Type set to I.
500 Invalid PORT Command.
500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
understood
(Source: MSSQL_REPL, Error number: MSSQL_REPL12003)
************************************************** ******
I used the exact same procedure on their publication as if I was one for
their locations and it worked fine. We do this at least twice every week for
new clients or when the subscription has to be recreated and have never had
this issue.
We turned off the firewalls and set the router to DMZ. Same problem. I
turned on verbose logging and did not get any additional information.
To work-around I downloaded the snapshot manually, changed the snapshot
location to the subscriber's local drive and it created the subscriptions.
When it finished I changed the snapshot path back to FTP and re-ran the
snapshot agent to see if it would continue to sync. Thankfully it does at
least for now.
The same issued happened again today on our other server. Both are SQL
Server 2005 SP2.
Anybody know what is causing this?
Thank you in advance!
when I ping 111.222.33.44 the ping request times out. I think this is your
problem;)
When I examine your logs it looks like the ftp command was not correctly
formatted:
500 Invalid PORT Command.
500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
understood
Can you check your ftp logs to see what ftp command SQL Server was issuing?
The ftp logs might also give you some clues as to what actually occured and
what the problem is.
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"RichardD" <RichardD@.discussions.microsoft.com> wrote in message
news:5B0C5E4D-9529-4EFC-97B5-5748558B4399@.microsoft.com...
> We have been creating the initial subscriptions the same way for years
> (sp_addmergepullsubscription_agent). Our FTP server is the same as well.
> Yesterday I ran into a strange situation on one client (3 subscribers to
> one
> database at 3 different locations, 2 with the same ISP). Each have SQL
> Server 2005 Developer's Editon.
> As soon as the process to connect to our FTP and download the snapshot we
> get the following error:
> ************************************************** *******
> Error messages:
> The schema script '' could not be propagated to the subscriber. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
> Get help: http://help/MSSQL_REPL-2147201001
> The process could not retrieve file
> 'OURSERVER_CLIENT_DBNAME_CLIENT_DBNAME\20071105123 250\snapshot.cab' from
> the
> FTP site '11.222.33.44'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20033) Get help:
> http://help/MSSQL_REPL20033
> 200 Type set to I.
> 500 Invalid PORT Command.
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
> understood
> (Source: MSSQL_REPL, Error number: MSSQL_REPL12003)
> ************************************************** ******
> I used the exact same procedure on their publication as if I was one for
> their locations and it worked fine. We do this at least twice every week
> for
> new clients or when the subscription has to be recreated and have never
> had
> this issue.
> We turned off the firewalls and set the router to DMZ. Same problem. I
> turned on verbose logging and did not get any additional information.
> To work-around I downloaded the snapshot manually, changed the snapshot
> location to the subscriber's local drive and it created the subscriptions.
> When it finished I changed the snapshot path back to FTP and re-ran the
> snapshot agent to see if it would continue to sync. Thankfully it does at
> least for now.
> The same issued happened again today on our other server. Both are SQL
> Server 2005 SP2.
> Anybody know what is causing this?
> Thank you in advance!
>
|||The actual IP is working. ;)
So far this has only happened to 2 clients. Others that have been done
before AND after have not had this issue. All clients use the same FTP
Server but each of the these 2 snapshots that failed are on a different
server. The others that worked after these failed are on the same server as
one of the failing clients.
In the event view we did see this message but have not yet tried using the
uncompressed snapshot.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 14151
Date: 11/7/2007
Time: 7:13:13 AM
User: HOSTING\sql-int05
Computer: OURSQLSERVER
Description:
Replication-Replication Snapshot Subsystem: agent
OURSQLSERVER-ClientName_DBName-ClientName_DBName-5 failed. The replication
agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.FciException
Exception Message: The replication agent had encountered a file compression
(cabinet) library error while calling 'FCIF
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 47 37 00 00 12 00 00 00 G7.....
0008: 0e 00 00 00 49 00 4e 00 ...I.N.
0010: 54 00 45 00 52 00 41 00 T.E.R.A.
0018: 43 00 54 00 49 00 56 00 C.T.I.V.
0020: 45 00 30 00 35 00 00 00 E.0.5...
0028: 0d 00 00 00 64 00 69 00 ...d.i.
0030: 73 00 74 00 72 00 69 00 s.t.r.i.
0038: 62 00 75 00 74 00 69 00 b.u.t.i.
0040: 6f 00 6e 00 00 00 o.n...
I will look for the FTP logs and see if there is anything in those as well.
Thanks!
"Hilary Cotter" wrote:
> when I ping 111.222.33.44 the ping request times out. I think this is your
> problem;)
> When I examine your logs it looks like the ftp command was not correctly
> formatted:
> 500 Invalid PORT Command.
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
> understood
> Can you check your ftp logs to see what ftp command SQL Server was issuing?
> The ftp logs might also give you some clues as to what actually occured and
> what the problem is.
>
> --
> RelevantNoise.com - dedicated to mining blogs for business intelligence.
> 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
> "RichardD" <RichardD@.discussions.microsoft.com> wrote in message
> news:5B0C5E4D-9529-4EFC-97B5-5748558B4399@.microsoft.com...
>
>
(sp_addmergepullsubscription_agent). Our FTP server is the same as well.
Yesterday I ran into a strange situation on one client (3 subscribers to one
database at 3 different locations, 2 with the same ISP). Each have SQL
Server 2005 Developer's Editon.
As soon as the process to connect to our FTP and download the snapshot we
get the following error:
************************************************** *******
Error messages:
The schema script '' could not be propagated to the subscriber. (Source:
MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
The process could not retrieve file
'OURSERVER_CLIENT_DBNAME_CLIENT_DBNAME\20071105123 250\snapshot.cab' from the
FTP site '11.222.33.44'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20033) Get help:
http://help/MSSQL_REPL20033
200 Type set to I.
500 Invalid PORT Command.
500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
understood
(Source: MSSQL_REPL, Error number: MSSQL_REPL12003)
************************************************** ******
I used the exact same procedure on their publication as if I was one for
their locations and it worked fine. We do this at least twice every week for
new clients or when the subscription has to be recreated and have never had
this issue.
We turned off the firewalls and set the router to DMZ. Same problem. I
turned on verbose logging and did not get any additional information.
To work-around I downloaded the snapshot manually, changed the snapshot
location to the subscriber's local drive and it created the subscriptions.
When it finished I changed the snapshot path back to FTP and re-ran the
snapshot agent to see if it would continue to sync. Thankfully it does at
least for now.
The same issued happened again today on our other server. Both are SQL
Server 2005 SP2.
Anybody know what is causing this?
Thank you in advance!
when I ping 111.222.33.44 the ping request times out. I think this is your
problem;)
When I examine your logs it looks like the ftp command was not correctly
formatted:
500 Invalid PORT Command.
500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
understood
Can you check your ftp logs to see what ftp command SQL Server was issuing?
The ftp logs might also give you some clues as to what actually occured and
what the problem is.
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"RichardD" <RichardD@.discussions.microsoft.com> wrote in message
news:5B0C5E4D-9529-4EFC-97B5-5748558B4399@.microsoft.com...
> We have been creating the initial subscriptions the same way for years
> (sp_addmergepullsubscription_agent). Our FTP server is the same as well.
> Yesterday I ran into a strange situation on one client (3 subscribers to
> one
> database at 3 different locations, 2 with the same ISP). Each have SQL
> Server 2005 Developer's Editon.
> As soon as the process to connect to our FTP and download the snapshot we
> get the following error:
> ************************************************** *******
> Error messages:
> The schema script '' could not be propagated to the subscriber. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
> Get help: http://help/MSSQL_REPL-2147201001
> The process could not retrieve file
> 'OURSERVER_CLIENT_DBNAME_CLIENT_DBNAME\20071105123 250\snapshot.cab' from
> the
> FTP site '11.222.33.44'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20033) Get help:
> http://help/MSSQL_REPL20033
> 200 Type set to I.
> 500 Invalid PORT Command.
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
> understood
> (Source: MSSQL_REPL, Error number: MSSQL_REPL12003)
> ************************************************** ******
> I used the exact same procedure on their publication as if I was one for
> their locations and it worked fine. We do this at least twice every week
> for
> new clients or when the subscription has to be recreated and have never
> had
> this issue.
> We turned off the firewalls and set the router to DMZ. Same problem. I
> turned on verbose logging and did not get any additional information.
> To work-around I downloaded the snapshot manually, changed the snapshot
> location to the subscriber's local drive and it created the subscriptions.
> When it finished I changed the snapshot path back to FTP and re-ran the
> snapshot agent to see if it would continue to sync. Thankfully it does at
> least for now.
> The same issued happened again today on our other server. Both are SQL
> Server 2005 SP2.
> Anybody know what is causing this?
> Thank you in advance!
>
|||The actual IP is working. ;)
So far this has only happened to 2 clients. Others that have been done
before AND after have not had this issue. All clients use the same FTP
Server but each of the these 2 snapshots that failed are on a different
server. The others that worked after these failed are on the same server as
one of the failing clients.
In the event view we did see this message but have not yet tried using the
uncompressed snapshot.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 14151
Date: 11/7/2007
Time: 7:13:13 AM
User: HOSTING\sql-int05
Computer: OURSQLSERVER
Description:
Replication-Replication Snapshot Subsystem: agent
OURSQLSERVER-ClientName_DBName-ClientName_DBName-5 failed. The replication
agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.FciException
Exception Message: The replication agent had encountered a file compression
(cabinet) library error while calling 'FCIF
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 47 37 00 00 12 00 00 00 G7.....
0008: 0e 00 00 00 49 00 4e 00 ...I.N.
0010: 54 00 45 00 52 00 41 00 T.E.R.A.
0018: 43 00 54 00 49 00 56 00 C.T.I.V.
0020: 45 00 30 00 35 00 00 00 E.0.5...
0028: 0d 00 00 00 64 00 69 00 ...d.i.
0030: 73 00 74 00 72 00 69 00 s.t.r.i.
0038: 62 00 75 00 74 00 69 00 b.u.t.i.
0040: 6f 00 6e 00 00 00 o.n...
I will look for the FTP logs and see if there is anything in those as well.
Thanks!
"Hilary Cotter" wrote:
> when I ping 111.222.33.44 the ping request times out. I think this is your
> problem;)
> When I examine your logs it looks like the ftp command was not correctly
> formatted:
> 500 Invalid PORT Command.
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
> understood
> Can you check your ftp logs to see what ftp command SQL Server was issuing?
> The ftp logs might also give you some clues as to what actually occured and
> what the problem is.
>
> --
> RelevantNoise.com - dedicated to mining blogs for business intelligence.
> 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
> "RichardD" <RichardD@.discussions.microsoft.com> wrote in message
> news:5B0C5E4D-9529-4EFC-97B5-5748558B4399@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)