Do you have any history details in the snapshot job?

Are you sure the publication still exists?

To really know what is happening it is better to start the snapshot agent by...

While the table is part of the publication you can't drop it. The best way is to drop the table from the publication. You can use sp_dropmergearticle.

After dropping the table...

Wich Service Pack??

You must execute it from the publishing database. What the stored procedure is created in the master db.

Run

SELECT * FROM sysobjects WHERE name = 'sp_scriptpublicationcustomprocs' AND xtype...

Not directly.

You can drop and then add the column with the new size with sp_repladdcolumn and sp_repldropcolumn.

In this way there is no need to reinitialize the subscriptions.

You can export to different text files and then run a cmd task to execute a copy of all your text files to a single file.

Don't think you can, unless you have the same drive letter in all your servers.

I think you will have to, at least, replace the server name with the @@servername function...

The value 0 in the @rc variable doesn't mean that the validation was succesfull. Only means that the sp executed suscesfully.

If you executed that sp in your publisher then you...

Be sure to check that the path of the log backup file is correct, that the backup device already exists, or that the backup file isn't taken by any other...

I don't think running profiler is a bad practice. There always a need to run profiler and maybe the development guys need to know what the app is executing to...

I don't think running profiler is a bad practice. There always a need to run profiler and maybe the development guys need to know what the app is executing to...

If you are going to use trigger then yes, you will have to create one trigger per table.

Or you can also run continuosly profiler to log the updates.

Or also...

I hope not!

Anyway you should first check wich one is the master server and if you wont delete the job from it, and provably defect the target server if you don't need...

the databases must have the same collation between the publisher and the subscriber.

Change the collarion with :

ALTER DATABASE DBName

SET COLLATE SQL_Latin1_General_CP1251_CS_AS

Run:

SELECT serverproperty('LicenseType')

SELECT serverproperty('NumLicenses')