Yes I ment was Blocked not DEADLOCK.

Yes again i agree with GILA.

Try to Drop in this Order and post any errors.

DROP ROUTE route_name

DROP SERVICE [servicename] ;

DROP QUEUE QUEUENAME

maybe you have already seen this, but i though why not post again:

http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx

Gila is right 🙂

I forgot to mention, that if you are moving form a lower version of SQL (2000) to 2005, then change the cmptlevel, but be sure to RUn...

How about adding him to the db_backupoperator Role in all databases and db_owner as well instead of SA.

After upgrading the Databases:

1. Change the Compatiility Level to 90

2. DBCC UPDATEUSAGE

3. DBCC CHECKDB (DatabaseName)

4. Copy all the logins associated with the Database OR ALL using this Scripts from...

Can you post a small detail about what you are trying to do in the script...

BEst Option will be BACKUP and Restore on the New Server.

After the Move, Change the compatibility level and RUN these commands.

DBCC UPDATEUSAGE and DBCC CHECKDB

Adding to it:

sometimes, the Deadlocks might resolve by themselves in time, but if you kill a long waiting deadlock, you might end up with a Phantom Process/lock and it stays...

As Michael suggested, there should be good design to start with, so you dont fall into the pits later on, Doesnt matter how big or small the project is .....

Adding to Anders.

My Current job, there is a Application "Maximo" which deals with SHOP Floor Order Entry system. There are 100 People in the Steel Mill loggin into the application...

Are you trying to connect to SQL 2000 or SQL 2005

Did you try:

From SQL Server Mana Studio, when you click to connect-> click Options and Network Protocols-> Named Pipes.. Check...

adding to the above discussion:

Since you mentioned Server is 16 CPU. so you must be having a Heavy load on the BOX and are you running 32x or 64x....

http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx

Yes you can set up the Triggers to sent out emails also.. TRY to REAd about DDL Triggers on BOL.

http://technet.microsoft.com/en-us/library/ms175941.aspx

http://www.sqlservercentral.com/articles/SQL+Server+2005+-+Security/2927/