Not exaclty.

But you can run sp_addscriptexec to push the creation of the index to all your subscribers, ro also regenerate the snapshot.

Check in BOL for parameters.

Run

SELECT min_distretention, max_distRetention, History_Retention

FROM msdb.dbo.MSdistributiondbs

This will tell you the imte in hours that the distribution will hold replicated /non replicated data. If it is too hi for you, try putting...

Locks by replication at the publisher shoudn't happen.

Maybe at the subscriber, depending of the transactions to be replicated. At the publisher, the log reader agent only takes the transactions marked...

You should create the publication and add all the articles using system stored procedures.

You will need to use sp_replicationdboption, sp_addpublication, sp_addpublication_snapshot, sp_grant_publication_access, sp_addarticle and sp_addsubscription sps, for transactional replication.

Also you...

Happened to me once.

Used checkdb with the repair options but it didn't help.

I continue running check db with the repair options, and after five times, it solved the problem, and...

I Think that if you have a distribution db that big, is because in sometime, someone decided to save many days of replicated transactions.

You could try changing the retention time,...

Transactions are kept until they are all applied at the subscribers. Is means that if you transactions aren't applied within the time that it is specified, then they will be...

What is the retention time in the distribution database?

To know, right click over replication in EM, Configure Publishing, ..., and then Properties of the distribution database.

Where the values over there...

just before running the snapshot agent (job) of your snapshot publication, run the sp sp_reinitsubscription. Check in BOL for help, but you should use 'All' in the @Article parameter.

None of...

First you need to grant the login acces to the publication, check sp_grant_publication_access in BOL.

There is no need to resincronize with a snapshot.

The sp_repladdcolumn sp, adds the column in the publisher and also in the subscriber.

Microsoft says that you need to stop replication, because...

run sp_helptext triggername, and search for the message syntax. Sure the owner of the trigger inserted in the code that message to run every time the trigger fires.

Did you also specify the move command in the restore of the diff backup?

Did you try starting the server in minimally configured mode? Check the -f parameter in sqlservr.exe.

Never happened to me but I thoght that SQL should rebuild by itself tempdb database...

Run sp_helpconstraint. If Status_For_Replication is (n/a) then if won't be propagated to the subscriber. You should recreate it without specifying  the NOT FOR REPLICATION clause.