Hi Group!
I am trying to delete a view from a database and always get the following
message:
"Error 3724: Cannot drop the view 'xxx' because it is beeing used for

I am trying to run the replication merge agent for the first time for a
replication. Several servers already replicate to the same server without
problems. I have replicated all the previous Publishers to my subscriber
with the identical setup with the exception of the user login ...

What issues can I expect if I need to restart the subscriber server
for any reason.

  We are getting an error with a particular table during the
snapshot
process for a merge publication on a SQL2K box.  The table errors out
with the message

Hi DBA's
We have one machime with 4 core processors and 2 GB of RAM. This machine have
3 sql 2005 instances and It's responsable form many replications. More of
them, have pull distribution agent, so we can controll these number over

In one book, I found the below statement.
"Keep in mind that transactional replication does not guarantee
identical databases at any given point in time. Rather, it guarantees
that each change at the source will eventually be propagated to the

Environment:  Publisher is SQL 2000, Distributor is SQL 2005
Please note: I have changed the user name, the publisher name and the
database names in the following text.
When I attempt to create a new publication, using either SSMS or EM, I

I have been getting this message in the past couple of hours.  I rebooted
publisher and subscriber.  Even if I restart the agent - it doesn't help. I
rebuilt transactional replication from scratch and I still got this error
message. I set for the agent to output to the file and ...

I've been given the task of creating a disaster recovery "replica" of a
production SQL server and keeping it current.
(SQL 2000)
At first we thought of using scripts to do a backup/restore method.

when I run the script....
EXEC sp_droparticle
 @publication = N'CB to 00',
 @article = N'CB_PayOuts',

I have become aware that some database entries were not "syncd" from a
disconnected server when it came online.  My only guess is that a conflict
resulted when the syncd finally happened.  The problem is it was 5 days ago,
and when I look at the conflicts under the subscription, the ...

How do you remove a push subscription from subscriber server?
This is our Server and we get are data pushed every 15 minutes from a remote
server that
is not managed by us.

I am attempting to create a subscription using the following script:
EXEC sp_addsubscription
 @publication = N'CB to 00',
 @subscriber = N'R00S-SQLa',

I am getting the following error when trying a merge replication:
 The process could not bulk copy into table "dbo"."MSmerge_contents".
Field size too large.
I assume that the "field size too large" is significant but I do not

Using SQL2005 SP2 transactional replication.  Whenever we have a deploy to
production that contains DDL, I drop the publication and then drop the
subscription on the replicated server.  Once the update is complete, I
recreate the publication with any changes that are necessary ...