No, there is no adverse impact other than never dropping a subscription. It sounds like this is exactly what you want. You are right that there are two...

Barry,

Are you saying that you have transactional replication from the publishers to ShareDB, and then snapshot replication from ShareDB to the subscribers?

It sounds like you want to trigger a snapshot...

The problem you are describing with SQL 2000 replication sounds like the one that was fixed in Service Pack 4.

Generating the drop and add scripts is simple, merely right-click in Enterprise Manager on the replication publication in question and select Generate SQL Script....  You can use the included Preview...

To prevent the log file from getting huge again, either set the database recovery model to Simple or schedule regular Transaction Log Backups.

Rangark,

The Redmond guys did not miss a step.  The expiration parameter indicates how long to wait for a subscriber to get data before the subscriber is dropped.  If it were...

Customer request to move all databases off C drive to a large RAID array (E drive).  I've already passed word to customer that in all likelihood this will stay where it is, since it...

Have you tried setting the trace flags per Colin's 6/7/2006 post?  This will tell you exactly what is deadlocking. 

As for why the rate of deadlocking changes, a contributor besides disk bandwidth...

Interesting, because it works perfectly in SQL 2000 and SQL 7. 

The only thing in my 2000 & 2005 BOL on data type precedence is in reference to combining different data...

Try this:

UPDATE tbFactuLineas

SET NoTarjeta = '10000000000000500213'

FROM tbfactucabecera

INNER JOIN tbfactulineas

ON tbfactucabecera.nocliente=tbfactulineas.nocliente

AND tbfactucabecera.noOrden=tbfactulineas.noorden

WHERE tbfactucabecera.statusFactura='G'

AND tbfactulineas.nocliente=2000

AND tbfactulineas.noemple='123456'

Try a variation on Dan's response:

select x, y, z

from server1.db1.owner1.tableA

UNION

select x, y, z

from server2.db2.owner2.tableA

UNION

select x, y, z

from server3.db3.owner3.tableA

If you have linked the SQL Servers to each other, then connecting to...

Yes.  As a matter of fact, the publisher and distributor can also both be set for SIMPLE recovery or Truncate Log on Checkpoint.

Thanks!  Yes, the developers changed the system date to October to test the change of daylight savings time, then changed the date back again all while replication was running.

Quick and cheesy answer is remove SET XACT_ABORT ON.

This is what is trying to begin the distributed transaction with Oracle using the MSDORA provider.

I believe you want what Francis was talking about, specifically:

SELECT eno,ename,dname

INTO #temp

FROM TABLE5 emp,TABLE6 dept

WHERE EMP.DEPTNO=DEPT.DEPTNO

This will put the results in the temporary table #temp.

To see the contents, simply...