Does the same as "Close your EM and re-open it. EM is caching data" if you're not too familiar with SQL Server?

See this for some AMD vs Xeon specs on DBMS (not SQL)

http://www.anandtech.com/it/

AMD are quicker , generally, but say that and you get flamed.

Internal architecture aside, one of the biggest...

What is the username you are trying?

Maybe it is...but probably not as efficient as a join as the IN list count goes up...

Ah well, it could just be something in your DDL.

Try QA.

Or post the DDL.

Close your EM and re-open it. EM is caching data

You're using EM aren't you...

Either:

Create the login but DO NOT attempt to add to the db. Then look at sp_change_users_login to fix the association

OR:

Use sp_revokedbaccess 'user' in QA to remove...

Nope, it's how EM connects to SQL.

In QA it would be a simple "CREATE VIEW..." but EM may not use this method or use soem sp_ or use DMO etc...

No special patch, just apply SP4...

Does EM on the server work?

Not on your workstation?

Patch your client tools.

What about through Query Anayzer? The better way to develop code...

don't need trace flag 3605, just need 1204

Try this to set the alert up:

        EXEC dbo.sp_add_alert 'Error 1205 - Deadlock detected', 1205, 0, 1, 60, NULL, 5

        EXEC dbo.sp_add_notification 'Error...

Glad to help.

probably not much performance degradation because no query plans with table access, also execution is split across 2 servers...

It's always a pain getting the number of ''''''' corect...

This is similar to this post

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=215490

Is this a secret double life?

And another perf comparison...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=139939&p=2

Moral: no strings!

I have also thought about deploying a stored procedure locally to every server which would simply contain the DATABASEPROPERTYEX statements above, I could then query this remotely to return the results, but...