Probably your DB is set in compatibility level 10. I just got one stupid question... What version of the SSMS are you using? Is it still SSMS 2005 version or...

If I am not mistaken the only password you have to provide is the SQL User the system uses when setting up distributor and publisher. It is more like set...

What part of security are you concerned about? Maybe someone can help you...

Actually using service broker is quite easy. The SQL Server does all the work for you. Also helps maintain data concurrency since it works with transactions. (Atleast from what I...

Are you restoring the back up with Keep replication option?

Even if you are I think you will still fail since the publisher and subscriber DB are out of Synch....

Out of the two ideas that you have floated, I guess the Service broker is the best.

Take a look at power Shell, You might be able to do quite...

You all are talking about Live meeting.... Let me gloat a bit.

Jimmy may is coming in mid February to give a presentation for our chapter... Yes..!!!!!!!!!

Niw I have finished...

He has added more business rule to it. Just asked him to provide samples. let us see if he is willing to give more info... 🙂

Now your requirement has changed slightly. For you to get better help from the people here, you will have to provide the table structure, Sample data , what is the...

How come you set it up as once every 5 min? That makes the distribution commands grow and thus causing the problem. You could set the distribution as immediate.

Also are...

Actually in Windows 2008 it has changed a bit.

As per Technet

In Windows Server 2008, you can create multiple DTCs in a failover cluster using the following steps:

...

What I would suggest you to do is to get rid of the @@error to catch errors and use TRY Catch instead. It is much more easier to use.

No, there is no need to reinitialize the subscription. There are two requirements though. The column added should either be NULLABLE or should have a default constraint.

That is applicable only in SQL 2000 or below. From SQL 2005 onwards, alter commands get replicated as well.

As long as the SA user name and password is out there, your security is shot into tiny pieces what ever application you put. You could try putting a firewall...