If you have different plans then either:

* The queries are not logically equivalent

* The different form resulted in the optimiser searching a different area of the plan space and finding...

Please note: 4 year old thread. Also backup/restore is not an option for moving some objects from one filegroup to another.

And the definition of the trigger (which is the prime suspect for the update failing)?

As for why the selects fail when explicitly converted, probably because there's non-numeric values in the...

Please note: 3 year old thread

Completely irrelevant. Order that you specify the joins is not the order they are executed in, unless you're forcing join order.

Check that the queries are logically equivalent.

Please post the definition of the table and check for triggers.

Why not use identity insert and use the identity values from the other database? You did make sure they can't overlap when you brought the live server back up (via...

Your problem is that DataCompare is picking the wrong order for syncing the tables. Solution, rather than comparing and syncing the entire database, do it a table at a time.

Sync table by table?

Something like Red Gate's SQL Data Compare would work well here. Otherwise you're going to be writing comparison and insert/update queries for quite some time.

Can you post the last few lines of the CheckDB output please. Or the entire output when run WITH NO_INFOMSGS?

jasona.work (5/17/2013)

---

Lynn Pettis (5/17/2013)

---

Lynn Pettis (5/17/2013)

---

And we have another winner:

After the date was changed to 2032 , scheduled jobs did run no issues. After changing the date to 2013 it...

If you don't see it, then there's something in sp_whoisactive that's filtering out those locks. Probably it's only showing sessions that are running, not ones that are sleeping and holding...

Grant Fritchey (5/17/2013)

---

And we have a really good reason to not run backups, to have the database...