If you didn't move to another record, then you're on the same record.

The problem is most likely with the circular refference, but I can't confirm without the code. Also I hope that this design doesn't go in production!!!

Can't tell what's wrong without the code used to create it as I've no way to try to reproduce the error here.

What code did you use to make the foreign key?

Why would you want to link a city to a single title??

As I said, it's possible but it's a worst practice, at best. Do at your own risks.

I'd check in the server's EULA for system tables. You'll most likely find that info there.

Select name, xtype from dbo.SysObjects where uid = 1

1 = dbo

Yes the db will become unsupported. Also triggers on system tables don't always work because some changes are handled entirely by the server (without actually using update statements >>...

Unequal and exotic joins are one of the most powerfull feature of tsql. You can find 5K exemples of their use on this site alone.

I didn't know our admin was so cool :-).

Can you upload the pic on a server. We can't see it from your hd.

So it's not a trigger problem.

The indexes are automatically updated by the server, but that can take a long time if there are many of them.

As I said, change the...

I said big query. Go with over 1 M records.

I'm ready to say never try to formulate an unilateral rule in sql server without making sure it applies in that situation .

I guess we're saying the same thing. It's like trying to prove that a cursor is slower than a set based approach. We all know that, no need...