Cool. What would you use in 2005?

Are you running this against a 2000 server or against a 2005 server in 8.0 compatibility mode? Either of those will be the problem.

One likely issue is the USING word you've got in the very first join. Also, you can't use variables $x. Instead you should use @x. What are those other two...

No, you and the article are correct. Seeks are better than scans. Eliminating, as much as you can, bookmark lookups is the way to go. The issue isn't whether or not...

The differences in the data are most likely going to cause different query plans. I suspect that's the most likely issue.

One thing you said that concerns me a bit. You've created...

Is the amount of data and it's distribution the same between dev & production. Do you have the latest statistics in both environments? Do you have an index maintenance plan in both...

There are some tools that offer a solution to this problem too. You can try Red-Gate's SQL Refactor which will rename an object and all it's references. Another one is...

I've only spent five minutes looking at this, but the first two things I'd check would be the parallelism threshold on your server and the cluster on the Subscriber table.

I'd...

sp_addextendedproperty is for putting descriptions, etc., on to your SQL server objects. It doesn't do any kind of formatting of any kind. It's for creating meta-data about your database objects....

And get a copy of Inside SQL Server 2005: The Storage Engine by Kalen Delaney

Have you runa a DBCC CHECKDB against the database as it suggests?

Other than that, I'd want to see the code to try to figure out where the error lies.

You might...

Not at all. If I thought I had something really cool & wonderful I'd be crushed. Instead, what I've got is a bit of a hack based on other people's...

It's not a terribly well written script. We had a specific need and wrote it to meet that need and then stopped. We're extremely dilligent about keeping reserved words &...

I'm fairly certain you can only get the columns available from the inserted table within a trigger and not any parameters within a stored procedure. You either have to simply...

This should do it:

SELECT

p.name,m.name

FROM

sys.server_principals p

JOIN