Another missing point here is that all of this depends on table size, indexes in place and data distribution the plans can change depending all of this

It is never...

iwegbue3 (7/7/2010)

---

Hello Experts,

I have a Transactional replication setup with updateable subscription. I tried bulk copying data from the subscriber down to the Publisher and it throws up the error message,...

here is one example of how the Query optimizer can use FK metadata.

Now on to your non-trusted issue.

The reason replication marks them as non-trusted is because you could potentially use...

Check this out: http://social.msdn.microsoft.com/forums/en-US/transactsql/thread/bba53aeb-6bdf-4cfb-b62f-fc4443e171c0/[/url]

iwegbue3 (7/5/2010)

---

Hello Experts,

I have a Transactional replication setup with updateable subscription. I tried bulk copying data from the subscriber down to the Publisher and it throws up the error message,...

That's false.

You can!

See : Using Multiple Versions of SQL Server...

Just change the temptable from "local" # to global ##

then from a different connection read it without nay locking like: "select * from ##debugtable with (nolock)"

ZenDada (6/25/2010)

---

noeld (6/25/2010)

---

ZenDada (6/25/2010)

---

As usual, Pinal Dave has...

declare @t table (order_number int, dte datetime)

insert into @t (order_number, dte )

select 5000 i, '06/01/2010' d union all

select 4900, '04/01/2010' union all

select 3800, '01/01/2010' union all

select 2500,...

Actually thank *you* for bringing up this issue which is not...

select customer_id, count(*) cnt

from orders

where orderdate > (getdate() -150)

group by customer_id

Now it makes sense and in fact BOL is a bit non-clear(cryptic) when telling you that your queued transactions will only reach the primary after you fail...

First I will recommend you to verify that the linked server created in the Subscriber "works"

Second Verify that Both Subscriber and primary have MSDTC "running"

If the above is ok:

...

How is it possible that the production server is "denormalized" and the reporting is "normalized"... I have seen it the other way around though.

SQLJocky (6/23/2010)

---

Controlled Failover: Failover done manually through use of the 'Failover' button in Mirroring Monitor (or equivalent T-SQL), typically used to failover in the event that you want to do...