I have two sql server instances on two different machines with the same db;
on the first machine some tables need to be copied on the second machine,
and on the second machine some other tables need to be copied on the first;
all the tables are related with the others in some way.

I have a very large and very active table which I want to replicate to
another server.  How can I set-up a Publication for this table and avoid the
locking during the initial snap-shot in SQL 2005?  SQL 2000 allowed
configuring replication without generating a snap-shot - assumed ...

I want via email to monitor transactional replication status such as still
running, have some problem during retry, or re-initialize, etc. instead of
login to Microsoft SQL Server Management Studio in SQL Server 2005 (SP1). I
think those information should get from msdb, does ...

Am very new to replication and would like to request some advice about solving
the following problem. I have a main database running on Sql Server 2005
Standard. A copy of this database is also running on Sql Server 2005 Express
on 3 laptops used by reps in the field. The reps ...

I have to move a SQL Server 2000 database from drive to another on the
same server because we are running out of space.  I know the easiest
way to accomplish this is to detach the database, move the .mdf & .ldf
files, and reattach the database.  However, this database is being

I'm developing on SQL Server 2005 and our application needs to be
'replicable'. I can see how this is done using a RowGuid and marking to be
used for replication, no problem.
My question, however, is if I should make this rowguid column the primary

Can anyone please provide me with a step-by-step explanation on how to
replicate data (snapshot replication) from a table in a SQL Server
2005 database to a table in a MySQL database through an ODBC
connection?

we are running sql200 and i am trying to do a transactional replication, i
recieve the following error message during snapshot creattion
The process could not bulk copy out of table
'[dbo].[syncobj_0x4336423045343434]'.

Hi,
SQL Server 2000 on Windows 2003 server.
We have been replicating between databases on the same server using
snapshot replication for some time without any problems.  Last night

I get the error:
"A failure occurred when accessing 'tabelle1_2.sch' due to an operating
system error [53=''] during Web synchronization. Ensure that the
-InternetLogin user when using basic authentication and the user running

We are in the process of configuration replication for our 64-bit clustered
sql 2000 environment.   We run into this very common error, in the first step
itself ('Cofnigure publisher, subscribers and distribution from EM').   At
this point we didn't even select any subscribers.  ...

We are decommissioning a cluster and moving all the databases to a new
cluster. The issue is, the distribution database. Is it possible to move the
distribution database without dropping the publications and subscriptions ?
If it is possible, please let me know how to do it.

Any suggests on Agent is suspect error?
MJ

I got 2 servers running, Dev and Production
The Production one is the one that the users run on and it's working
with a Access adp project
The Dev one is the migration project that evolve and use VB as

New to SQL Replication.
Have SQL 2000 and wanted to replicate my business & core databases to a
server at another site to increase availability.
Is SQL replication able to keep my business application running without end