I have not had any issues with running the databases in a compatibility mode BUT what you might run into is that if your application has problems and its not...

I have always found it good practice to reboot before and after i do maintenance on a server just to make sure the server comes back up probably old school...

SUCCESS!!!!!!!!

Thank to all... Greatly appreciated on all the assistance from anyone that replied or read the post

Currently  the code is running and like i  said  hopefully...

Thanks so much for the help... it compiles and runs but returns this error
Msg 137, Level 15, State 2, Line 1
Must declare the scalar variable "@Loop".

Which...

Thank you for your reply

When i remove the single quote that is around the @Loop = @Loop + 1  i still get the same error. which is

Thanks for the reply... The error is
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '@Loop = @Loop + 1'.

If there is another way to...

No third party tools are to be used in this solution.  Jut trying to make it happen with the capabilities of SQL Server.

Thanks for the comment

I agree...that a fail over cluster might be your best option IF you can not use ALWAYS ON and log shipping will be a mess as you state

Much much clearer now that its known this is a active/active cluster. Had me wondering there for a few minutes but wanted to make sure it was verified and...

George,

You are correct it is a one line change in 2 locations....but my point was that the cluster appears to me that it is NOT doing everything that Peacesells want...

I could be mistaken here or just confused :w00t:. Not sure how you have separate databases on NodeA and Node B IF this is an Active/Passive Cluster as both...

As mentioned ...use the trace available and see if you can also use Activity monitor and when the dead lock happens try to see what code is running BEFORE you...

Thank you everyone for looking and taking the time to read thru....greatly apprecatied

Was able to get this fixed with the use of sp_unbinddefault ....as a surprise to me didnt...

Not sure why this was this way but it worked so its fixed 🙂 wooo hooooo

use [database name]

sp_droppublication @publication='publication_name', @ignore_distributor = 1

then restarted the services..and the publication was still...

What type of replication are you setting up? Also are you sure you want to use the same publication table to do differnt things...altho i am sure that it can...