If you restored into the same server, you shoudn't have any problems with the login, unless you have restored the master db.

If you need to compare database structure you can just script out the entire database (of both servers) and then use windows command comp to compare the scripts.

If you also...

Merge replication won't be affected by the creation of new tables.

When you settep up a merge publication, you already specified the tables (articles) that belong to the merge publication.

Changes to...

If you are trying to get the changes made at your server applied also to the new server, instead of triggers you can use replication.

try

exec remoteserver.master.dbo.xp_cmdshell 'test.bat'.

you shoud add it as a linked server.

I don't think you can.

They must be with the same codepage.

No. Permissions are not saved at table level, because depends on users and roles. So you can replicate permisions of a table.

You can try to copy roles and users with...

Even if you published all tables wich are involved in the integrity validation, if you specify the snapshot to drop the table before applying the snapshot, it will fail.

You shoudn't...

DTS package in replication are to transform the repliated transactions when you are replicating to heterogeneous subscribers, like Oracle.

If you don't need to transform your data, then you shound't use...

If the table already exists in the subscriber, you shound't specify the snapshot to drop it.

You can change that in the properties of each article.

If you need to re create...

run sp_helpmergepublication from the publisher in the publication database to check if the publication really exists.

The subscribers are SQL Server?

Why do you need to use DTS? Can you use pre and post Snapshot Application Scripts?

I have used it before and never had any problems.

You should be aware that the transactions marked for replication in the Log won't be delivered to the distribution database by...

did you made a clean drop of the subscriber before?

Check sp_dropsubscription in BOL, and run it from the publisher.

I have used before and never had problems.

You should keep in mind, that until you don't backup the log of the published database, transactions won't be delivered to the distribution...