If the huge transaction is not backed up with a transaction log backup, then DBCC SHRINKFILE won't help much, because it is still in the log so it won't free...

Well, the backup in most cases will be executing because there was a job that fires the backup. Then you should check the state of that job to actually know...

You should consider doing more frequent log backups to have the size of the backup file smaller, at least one each 30 minutes. It seems that you have many transactions...

It seems that before restating the SQL server you had a big transaction running.

Run DBCC OPENTRAN('database_a'), that will give you the oldest transaction in the db before restarting the server....

The correct way is Servername.DBName.Owner.TableName.

First add the server as a linked server an then run the query.

If you need to begin a distributed transaction, using the two phase commit, then...

Depending of how you configured your publication, the snapshot might drop and recreate the tables at subscriber, so you should check after the snapshot is applied the all the triggers...

Well, you should be shure to change the service account of all the servers involved in your replication schema and also be sure to assing the same permissions you current...

Stored procedures used by replication are not dropped by replication. When applying a new snapshot they are dropped but recreated again, so maybe they where manually dropped.

You can recreate them...

The most common ones are:

20598: The row was not found at the Subscriber when applying the replicated command

547:%ls statement conflicted with %ls %ls constraint '%.*ls'. The conflict occurred in database...

Also check at the replication Monitor for more information and not just in the job history. May be you shoud reinitialize the entire publication and run the snapshot agent again....

After adding the new column only at the publisher you need to reinitialize the article, so that SQL will genereate a new snapshot wich will include the added column in...

If you want to add a new column to the table (not the filter) then you can use sp_repladdcolumn and with this there is no need to generate a new...

It seems a problem with the stored procedures used to replicate. Run sp_HelpArticle to see the names of the stored procedures. Check the update_command column and edit that stored procedure...

You can configure transactional replication not to replicate delete actions.

When you add the article to the publication, specify 'none' in the delete command stored procedure.

@del_cmd  = 'NONE 'parameter if you...

Wich type of replication is it? Transactional? Are you applying the initial snapshot?

If so, I would reinitialize the subscription, generate a new snapshot and apply it again.

If the table at...