Replication to Mainframe Db2 OSZ

What would I need in order to setup replication between SQL2000 SP3 and MVS Subsystem running Db2 database . I mean, does it need any 3rd party tool or regular replication setup between SQL and Db2 is enoughAsk IBM for the DB2 Federated Server. If you have DB2 license, they should let you use that software free. It comes with a Replicator which allows you to replicate data from a different platform.

Replication to a web server in DMZ

Hello,
We have active/active SQL2000 SP3a on a Win2k3 cluster in our domain. We
need to copy some tables from a
database out to our web server.
The web server, is SQL2000 SP3a on Windows 2000, SP4. It is a stand-alone
server out in the DMZ.
We get the following error when trying to do this:
SubSystem Message - Job 'VIRTUALSERVERNAME\INSTANCENAME-WEBSERVER-13'
(0x5F1388610429AD4B8860D51DF8504198), step 2 - Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection. The
process could not connect to Subscriber 'WEBSERVER'.
Here are some thoughts we have. The SQL server in the domain runs on port
1303. The SQL server in the DMZ is running on a different port. Do the
ports need to match for the replication to occur?
We are not sure why this isn't working. Anyone have some input or some
documentation on how to set up replication to a web server in a DMZ. I am
sure this is something that is done at most companies, but we are missing
something.
Thanks in advance.
Hopefully this article will help out:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I would try SQL Authentication.
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
"JJP" <anonymous@.discussions.microsoft.com> wrote in message
news:%23%23dsWsu6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Hello,
> We have active/active SQL2000 SP3a on a Win2k3 cluster in our domain. We
> need to copy some tables from a
> database out to our web server.
> The web server, is SQL2000 SP3a on Windows 2000, SP4. It is a stand-alone
> server out in the DMZ.
> We get the following error when trying to do this:
> --
> SubSystem Message - Job 'VIRTUALSERVERNAME\INSTANCENAME-WEBSERVER-13'
> (0x5F1388610429AD4B8860D51DF8504198), step 2 - Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection. The
> process could not connect to Subscriber 'WEBSERVER'.
> --
> Here are some thoughts we have. The SQL server in the domain runs on port
> 1303. The SQL server in the DMZ is running on a different port. Do the
> ports need to match for the replication to occur?
> We are not sure why this isn't working. Anyone have some input or some
> documentation on how to set up replication to a web server in a DMZ. I am
> sure this is something that is done at most companies, but we are missing
> something.
> Thanks in advance.
>
|||Thanks Paul, I am looking that over.
Hilary, the web server is using Windows and SQL, is that what you are
referring to?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ORJz63u6FHA.3416@.TK2MSFTNGP15.phx.gbl...
>I would try SQL Authentication.
> --
> 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
> "JJP" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23%23dsWsu6FHA.1276@.TK2MSFTNGP09.phx.gbl...
>
sql

Replication scenario question...Merge or Transactional?

The situation I am faced with is we have a web application supported by a SQL
2000(sp4) database that resides on a limited bandwidth network. Our
distributed users are constantly complaining of "slow" response times. Our
local users have no such complaints. Some of our leadership has suggested
sending a SQL server/IIS server to the remote location and using some type of
replication to synchronize the data between these boxes. The requirements
are for minimal latency and concurrent updating of data. The leadership also
want this solution to be completely automated (little or no supervision of
the replication process) and as with everything we do they want it right away
(we're talking days, not weeks). I am very new to replication and have read
through the BOL section and am in the process of reading Hillary Cotter's
book. I am leaning toward an implementation of Merge Replication but I am
unsure if this is the right solution. Any advice or informed opinions would
be greatly appreciated.
There is no concurrent replication option ie each solution will have a degree
of latency. If you use merge then you can select from a variety of conflict
resolvers and easily work offline. This might be your best option. There are
alternatives - queued updating subscribers, immediate updating subscribers
and bidirectional transactional replication. Do you have BLOBS in the table?
Are the subscribers always connected? Should they be able to continue if not
connected? These questions will clarify and narrow down the options a bit.
Whichever option you select, don't rush - you'll need time to configure it in
a test environment to establish a set of protocols (change management, error
handling...) and to simply verify that it all works for your situation.
HTH,
Paul Ibison
"Dave Stokes" wrote:

> The situation I am faced with is we have a web application supported by a SQL
> 2000(sp4) database that resides on a limited bandwidth network. Our
> distributed users are constantly complaining of "slow" response times. Our
> local users have no such complaints. Some of our leadership has suggested
> sending a SQL server/IIS server to the remote location and using some type of
> replication to synchronize the data between these boxes. The requirements
> are for minimal latency and concurrent updating of data. The leadership also
> want this solution to be completely automated (little or no supervision of
> the replication process) and as with everything we do they want it right away
> (we're talking days, not weeks). I am very new to replication and have read
> through the BOL section and am in the process of reading Hillary Cotter's
> book. I am leaning toward an implementation of Merge Replication but I am
> unsure if this is the right solution. Any advice or informed opinions would
> be greatly appreciated.

Replication only working 1 way

Hi Guys
I am running SQL2000 I have set up Transactional Replication with a push
subscription.
My 2 servers are not in the same domain but can see eachother.
Server 1 is Distributor as well as publisher. All insert, delete & updates
made on this side replicates fine to server 2, however any inserts, delete or
update made on server 2 does NOT replicate back to server 1.
I do not get any errors everything seems fine except for the lack of
replication.
Any ideas?
Thanks.
Regards
Jonas
Jonas,
Transactional replication is one way by default (Publisher -> Subscriber).
To get it bidirectional, you need to set up immediate updating subscriptions
or queued updating subscribers.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Monitor - Publisher is empty, but my replication is still there and working

I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
Which account are you using to connect to the EM?
"Query Builder" <querybuilder@.gmail.com> wrote in message
news:1162496955.745756.103220@.e3g2000cwe.googlegro ups.com...
>I have a wired situation..!
> I set up transactional replication on one of my development server (SQL
> 2000 Dev Edition with sp4).
> It is running fine without any issues and all of a sudden, i noticed in
> my repication monitor tab under Publisher where I usually see the
> publication is empty now.
> I do see the snapshot agent, log reader and distribution agent under my
> agents inside the replication Monitor. But its usefull to see all 3
> agents in one window under publisher before. What happend? Is there any
> way to get that inside that monitor? Has someone encountered this
> sitation before? Please advise...
> After that I tried to create a new set of replication on different
> database on the same server and i dont see those either under
> Replication Monitor - Publishers...
> All it says is (No Items)...
> I would appreciate any help to correct this issue... Thanks in advance..
>
|||I think your subscription has expired and being dropped. Check to see if the
job exists in the jobs folder, it will have a name similar to the
publication.
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
"Query Builder" <querybuilder@.gmail.com> wrote in message
news:1162496955.745756.103220@.e3g2000cwe.googlegro ups.com...
>I have a wired situation..!
> I set up transactional replication on one of my development server (SQL
> 2000 Dev Edition with sp4).
> It is running fine without any issues and all of a sudden, i noticed in
> my repication monitor tab under Publisher where I usually see the
> publication is empty now.
> I do see the snapshot agent, log reader and distribution agent under my
> agents inside the replication Monitor. But its usefull to see all 3
> agents in one window under publisher before. What happend? Is there any
> way to get that inside that monitor? Has someone encountered this
> sitation before? Please advise...
> After that I tried to create a new set of replication on different
> database on the same server and i dont see those either under
> Replication Monitor - Publishers...
> All it says is (No Items)...
> I would appreciate any help to correct this issue... Thanks in advance..
>
|||I am connected thru EM using the SA account. I also have adimin rights
thru windows authentication...
How do I check my subscriptions are expired or not? I created a new
replication for testing and it is also working fine but i dont see the
replication in the replication monitor.. I do see the publications
under the replication--> publication tree...
THanks for all your input. I would apprecate if you can help me figure
this out...! Thanks again
On Nov 3, 6:34 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I think your subscription has expired and being dropped. Check to see if the
> job exists in the jobs folder, it will have a name similar to the
> publication.
> --
> 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 FTShttp://www.indexserverfaq.com
> "Query Builder" <querybuil...@.gmail.com> wrote in messagenews:1162496955.745756.103220@.e3g2000cwe.go oglegroups.com...
>
>
>
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> I am connected thru EM using the SA account. I also have adimin rights
> thru windows authentication...
> How do I check my subscriptions are expired or not? I created a new
> replication for testing and it is also working fine but i dont see the
> replication in the replication monitor.. I do see the publications
> under the replication--> publication tree...
> THanks for all your input. I would apprecate if you can help me figure
> this out...! Thanks again
>
> On Nov 3, 6:34 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> I am connected thru EM using the SA account. I also have adimin rights
> thru windows authentication...
> How do I check my subscriptions are expired or not? I created a new
> replication for testing and it is also working fine but i dont see the
> replication in the replication monitor.. I do see the publications
> under the replication--> publication tree...
> THanks for all your input. I would apprecate if you can help me figure
> this out...! Thanks again
>
> On Nov 3, 6:34 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
|||I finally figured out the issue... I had the sql names changed.. when I
changed it back, the replications appeared under the replication
monitor tab...
So the moral of the whole story(issue) is never change SQL jobs
associated with replication.. It will disspear from the replication
monitor group...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
> Query Builder wrote:

replication locking (sql2000 / transactional)

Currently, we have a table replicated from one database to another on the
same server.
If I update 127 records based on the primary key, the subscription process
locks all the records until all the 127 commands have been executed.
Seamingly regardless of how they were updated.
eg.
CREATE TABLE Orgs ( OrganisationID INT PRIMARY KEY CLUSTERED ,
TimeLastUpdated DATETIME NOT NULL )
DECLARE @.SelectedOrgs ( OrganisationID INT PRIMARY KEY CLUSTERED )
/* ... insert 127 organisations to update here ... */
-- Process Type 1
UPDATE Orgs SET TimeLastUpdated = GETDATE()
FROM Orgs INNER JOIN @.SelectedOrgs SO ON Orgs.OrganisationID =
SO.OrganisationID
-- Process Type 2
WHILE ( blah )
BEGIN
-- one at a time in asc order
SELECT @.OrgID = OrganisationID FROM @.SelectedOrgs WHERE ( blah )
UPDATE Orgs SET TimeLastUpdated = GETDATE() WHERE OrganisationID =
@.OrgID
END
Using the default isolation level and no explicit transactions the table in
the subscriber database was locked until the commands had all been executed.
What gives - both types lock the whole table on the subscriber.
Surely it's not meant to use the same locks as were applied when the data
was updated?
Is there any to stop it locking the whole thing while it processes the
commands?
Ideally we'd upgrade to 2k5 and use row versioning... but that wont happen
for a while.

I need to implement a similar thing on a much larger database which needs to
be up 24/7 and can't be locked for long periods of time, mean while on the
publisher, 5% of the data may be changed in one go - but if we can't get it
to use optimistic locking on the subscriber we can't use replication.
Rebecca,
an update statement always has an implicit transaction. if you use
lumigent's Logexplorer you can see how this works. Your update statement will
be logged to the transaction log as :
BEGIN TRAN
Update Orgs SET TimeLastUpdated = GETDATE() where OrganizationID = 1
Update Orgs SET TimeLastUpdated = GETDATE() where OrganizationID = 2
..
..
..
Update Orgs SET TimeLastUpdated = GETDATE() where OrganizationID = 127
COMMIT TRAN
This is read by the log reader agent and converted to stored procedure
calls, but also with the transaction (AFAIR same XACT in msrepl_commands) .
The distribution agent applies it in the same way.
The table itself shouldn't be locked (lock escalation shouldn't occur on
such a low # rows), and inserting a record at the same time as the
distribution agent runs should prove this to be true.
Anyway, to answer your question more directly, -MaxCmdsInTran should allow
you to break the ACID properties and commit separate parts of the update as
separate transactions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Issues

Hello,
I am replicating databases from a sql2000 server with a
seperate distributer running sql2000 server and a MSDE subscriber. I
am using merge replication. The subscribers pull a subscription.
We want to have this setup across the internet for multiple
subscribers
each of whom might be updating as frequently as 1 hour. There are a
couple of issues I would like to find out about.
1.Security: I understood that the initial snapshots can be
published via ftp ( or any other means ofcourse). Can the merge
process be accomplished via ftp too? i.e The merge agent running on
the subscriber, writes to the ftp space reserved for it and the
publisher uses these files to bring the publisher up to speed and put
the updates back to all the subscribers. (sounds very slow). What are
our options as far as channel security if we are not using ftp ( and
is it possible in the first place across the internet).If we use a
secure ftp site, can the agents manage that?
2.Load: Our publisher has about 20 databases right now, with a
total of 1Gig file space occupied by mdf and log files. One database
is being replicated. Its consuming 1Gig of RAM Memory. Is that normal?
Is it because of the replication. How can I find out? Can anybody with
experience in this area, tell how much more load we can expect to
see? How much processing is needed for 40 users each updating about
500KB of data every one hour?
Thanks a lot,
Hananiel
1) I'm confused by what you are referring to by ftp. Are you talking about
the ftp port (21) or the ftp service. IE can the merge agent download the
commands using FTP? The answer is no, only the snapshot. If you are talking
about using port 21 the answer is yes. The merge agent will connect to the
publisher/distributor/subscriber using port 1433 or whatever port your SQL
Server is configured to run on, which could be port 21.
2) SQL Server will consume as much memory as is accessible on the machine or
whatever you configure SQL Server to consume using sp_configure 'max server
memory (MB)'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0409170710.68893ce9@.posting.google.c om...
> Hello,
> I am replicating databases from a sql2000 server with a
> seperate distributer running sql2000 server and a MSDE subscriber. I
> am using merge replication. The subscribers pull a subscription.
> We want to have this setup across the internet for multiple
> subscribers
> each of whom might be updating as frequently as 1 hour. There are a
> couple of issues I would like to find out about.
> 1.Security: I understood that the initial snapshots can be
> published via ftp ( or any other means ofcourse). Can the merge
> process be accomplished via ftp too? i.e The merge agent running on
> the subscriber, writes to the ftp space reserved for it and the
> publisher uses these files to bring the publisher up to speed and put
> the updates back to all the subscribers. (sounds very slow). What are
> our options as far as channel security if we are not using ftp ( and
> is it possible in the first place across the internet).If we use a
> secure ftp site, can the agents manage that?
> 2.Load: Our publisher has about 20 databases right now, with a
> total of 1Gig file space occupied by mdf and log files. One database
> is being replicated. Its consuming 1Gig of RAM Memory. Is that normal?
> Is it because of the replication. How can I find out? Can anybody with
> experience in this area, tell how much more load we can expect to
> see? How much processing is needed for 40 users each updating about
> 500KB of data every one hour?
> Thanks a lot,
> Hananiel
|||Hilary Thanks!,
Does SqlServer natively support encryption of
communication between its remote merge agents and itself? Or should we use a
tool like secure shell to make an encrypted connection?
Thanks,
Hananiel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eXjhIAOnEHA.644@.tk2msftngp13.phx.gbl...
> 1) I'm confused by what you are referring to by ftp. Are you talking about
> the ftp port (21) or the ftp service. IE can the merge agent download the
> commands using FTP? The answer is no, only the snapshot. If you are
talking
> about using port 21 the answer is yes. The merge agent will connect to the
> publisher/distributor/subscriber using port 1433 or whatever port your SQL
> Server is configured to run on, which could be port 21.
> 2) SQL Server will consume as much memory as is accessible on the machine
or
> whatever you configure SQL Server to consume using sp_configure 'max
server
> memory (MB)'
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Hananiel" <hananiel@.yahoo.com> wrote in message
> news:e338e321.0409170710.68893ce9@.posting.google.c om...
>

Replication Issue with ERROR 20026 publication '%s' does not exist

We have replication between two Microsoft SQL2000 servers. We took
down replication (had no problem) then backed up the database (no
problem). Tried to make some changes but had to delete the publication
first and then we ran into some other issuse (not a big problem). So
we decided to restore the database from the backup. the issue came
about because the publication has been deleted but the restored
database still has it listed. Bacause of this we cannot make any
changes to the database, further more if we try to delete the
publication it wont let us because it doesnt exist. So we are kind
caught in a bind (This is the main issue).
can you drop the publications using sp_droppublication?
Follow these instructions - http://support.microsoft.com/kb/324401
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
<ebade2000@.gmail.com> wrote in message
news:1174060376.222600.269530@.p15g2000hsd.googlegr oups.com...
> We have replication between two Microsoft SQL2000 servers. We took
> down replication (had no problem) then backed up the database (no
> problem). Tried to make some changes but had to delete the publication
> first and then we ran into some other issuse (not a big problem). So
> we decided to restore the database from the backup. the issue came
> about because the publication has been deleted but the restored
> database still has it listed. Bacause of this we cannot make any
> changes to the database, further more if we try to delete the
> publication it wont let us because it doesnt exist. So we are kind
> caught in a bind (This is the main issue).
>
|||Fixed it yeeeha. Thanks for your help Hilary what ended up working for
me was "sp_removedbreplication". The other stored procedures will work
if the publication pr replication existed (which was not my case)

Replication is failing due to use of FTS on my subscriber, what can I do?

Hi Daniel,
If you are using push subscriptions from a SQL2000 distributor, you are
essentially using the SQL2000 replication components which, I am sorry to
say, are ill-equipped to handle things like full-text indexes during
snapshot processing. This also means that upgrading the subscriber to
SQL2005 SP2 will probably not do you any good. Alternatively, you can use a
SQL2005 SP2 instance as the distributor of your SQL2000 publisher so you can
enable the FulltextIndex (0x0000000001000000) article schema option via
sp_add|changearticle (both SQL2000 and SQL2005 GUI will not allow you to
specify that for a SQL2000 publisher) and let the SQL2005 replication
components handle the full-text index dependencies for you (ideally using
"drop" as the article pre-creation commands). That said, I can imagine that
moving the distributor can involve a substantial amount of work.
Hope that helps,
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:uAOtEPAjHHA.1272@.TK2MSFTNGP04.phx.gbl...
> I'm in the middle of setting up a non-updating transactional replication
> from SQL Server 2000 SP3 (can't put SP4 on as the main application we use
> hasn't been certified for SP4 yet) to SQL Server 2005 SP1 (I could put SP2
> on if it will fix the issue, but it would mean taking our e-commerce sites
> down while doing so and I'd need to schedule a maintenance window for
> this). At first it was working fine, but snapshots were set to delete the
> tables and so we'd lose the FTS setups. I've now changed the snapshots to
> not do this, and now the replications fails with the error:
> Cannot drop index 'PK_Product' because it enforces the full-text key for
> table or indexed view 'Product'.
> This occurs with both "Delete data. If article has a row filter, delete
> only data that matches the filter.", "Truncate all data in the existing
> object" (which is the preferred option), and "Keep existing object
> unchanged". It also doesn't matter if I have the clustered and/or
> nonclustered index copy set to true or false (the PK is the clustered
> index on this table).
> This is a push subscription, with the distribution agent running on the
> publisher.
> Any ideas how I can retain the table structure (so keeping the FTS index
> and not having to rebuild it each time the snapshot is applied) and have
> transaction replication working? Or is it not possible?
> Dan
>
Hi Daniel,
I probably don't understand all the details about your scenario but given
that applying a snapshot typically replaces most of the data at the
subscriber, I would think that a FTS rebuild is likely required (or at least
a good idea) after the snapshot has been applied. That said, we no longer
drop the primary key\unique constraints (which is an arguably bad fix for
some other issue) in a "mostly" SQL2005 environment (SQL2005 snapshot and
distribution agent) if the article pre-creation is 'delete'. However,
leaving any unique constraints\indexes (especially non-clustered) while the
snapshot is being applied runs the risk of slowing down the snapshot
delivery process significantly (no minimal logging) and may prevent a
concurrent snapshot from being delivered successfully since bcp data
generated for a concurrent snapshot can violate uniqueness constraints
(compensated later on during the reconciliation phase).
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:eLx1McKjHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Raymond wrote on Tue, 1 May 2007 09:54:35 -0700:
>
> It seems strange that all options require the PK to be dropped - I would
> have thought that the options to delete or truncate data in the
> destination table would leave the PK untouched (after all, it shouldn't be
> touching the schema). I don't have an FTS index on the SQL Server 2000
> source tables - the FTS is handled solely on the subscriber, so I'm not
> trying to replicate the FTS catalog, just the data in the tables so that
> the change tracking on the subscriber handles all the FTS work.
> Dan
>
|||Hi Daniel,
I probably don't understand all the details about your scenario but given
that applying a snapshot typically replaces most of the data at the
subscriber, I would think that a FTS rebuild is likely required (or at least
a good idea) after the snapshot has been applied. That said, we no longer
drop the primary key\unique constraints (which is an arguably bad fix for
some other issue) in a "mostly" SQL2005 environment (SQL2005 snapshot and
distribution agent) if the article pre-creation is 'delete'. However,
leaving any unique constraints\indexes (especially non-clustered) while the
snapshot is being applied runs the risk of slowing down the snapshot
delivery process significantly (no minimal logging) and may prevent a
concurrent snapshot from being delivered successfully since bcp data
generated for a concurrent snapshot can violate uniqueness constraints
(compensated later on during the reconciliation phase).
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:eLx1McKjHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Raymond wrote on Tue, 1 May 2007 09:54:35 -0700:
>
> It seems strange that all options require the PK to be dropped - I would
> have thought that the options to delete or truncate data in the
> destination table would leave the PK untouched (after all, it shouldn't be
> touching the schema). I don't have an FTS index on the SQL Server 2000
> source tables - the FTS is handled solely on the subscriber, so I'm not
> trying to replicate the FTS catalog, just the data in the tables so that
> the change tracking on the subscriber handles all the FTS work.
> Dan
>

Replication in cluster environment problem

1) I have the Active/Passive cluster environment (using Microsoft cluster service).
2) SQL2000 is installed on the cluster (Virtual instance).
3) Virtual instance of SQL Server is used as Publisher in Transactional replication with updatable subscribers.
4) Subscribers are passing updates to subscriber using MSMQ
5) The problem is : after I establish replication , the Queue Agent fails with following error (Failed to initiate search for MSMQs)Did you define your MSMQ for your queue agent? My guess is not. That's why you got the error.|||I have defined MSMQ resource at "Cluster Managager".
The settings that i was used were taken from microsoft article.
MSMQ have dependeny the same "Network name" as SQL Server.
So if the question "Did you define your MSMQ for your queue agent"
is about that , the answer is yes.
Probably i have not understood your question.