spt_fallback_db is in master and is a system table.

Some things are.

If not on a cluster take a look at this: http://www.sqlservercentral.com/Forums/Topic661028-149-1.aspx

Officially you can't do that!

there are many other scripts on this site that could probably help you.

What exactly are you trying to do?

Nevermind I need some coffee :d

Are you sure only **one** insert is going at a time ?

In SQL 2005 ALTER TABLE ... ADD .. will propagate the DDL IF the publication was enabled to do it.

Note the default is ON ( so you may be lucky...

I vote for Log shipping as well.

I did selected "mirroring" because of all the hype around it but it is not IMO easier because of all the "new" concepts...

This is a BAD formulated question. I got right because I guessed the intentions of the author. The constraint DOES gets created on the subscriber just not enforced!

If you don't...

Try using:

BEGIN DISTRIBUTED TRANSACTION;

Instead of BEGIN TRANSACTION.

Note

1. MSDTC must be configured correctly on both servers for this to work.

2. Keep in mind that distributed transactions are expensive operations.

Good Luck

Can you tell us why are you replicating in the first place?

Why don't you write directly to the "replica" table, that way you don't need replication at all 🙁

bill (3/6/2009)

---

That was it! The publisher was set to MCALL while the subscriber was expecting XCALL. Thanks for that.

This replication was being re-established after the Publisher was rebuilt.

I...

sunny Brook (3/6/2009)

---

Disable all the logshipping jobs:

Manually Kick off the Logshipping-backup log job onyour primary server;

when it is finished, manually start the logshipping copy job;

then start the...

Or cast at table *creation time*

SQL 2005 by default uses SCALLs for updates.

SQL 2000 by default uses XCALLs for updates.