Don't use the upsizing wizzard.

Re-develop your database based on SQL Server functionality and data types. Build it correctly the first time based on published...

There is some job, process or someone that is rebuilding the publication, the job probably runs late Sunday night or early Monday morning.

If this is the...

EM is not robust enough to return realtime connection/SPID information, especially if the server is too busy, EM will just hang. using QA and...

Are you adding the table after you have created the publication and snapshot ??

Are you adding the new table via GUI or sp_addarticle ??

Besids BCP you can use DTS. in the DTS package create a connection to the destination DB. create aconnection to the text file, during the creation of the connection to...

why don't you try a DBCC IndexDefrag insted of a dbcc dbreindex. it can be done without taking the db or table off-line.

I would shutdown the replication agent.

Run DBCC IndexDefrag <check...

if you double click on the agent this will give you more details about the error, it could be a deadlock, blocking, time-out etc

I'v had the same error happen periodiocally, but not really sure what the cause is . usually stopping and starting the SQL agent seems to...

I have done it using t-sql commands via QA or job steps.

From BOL:

BACKUP DATABASE Northwind    TO DISK = '\\uncservername\Northwind.bak'RESTORE FILELISTONLY    FROM...



                    

why don't you just create 2 subscriptions, one from Server_a to Server_b and one from Server_a to Server_c. This is much more efficient and if Server_b dies data will still get...

try the following: re-create and apply a new snapshot

what is the error that you are getting on the failure, what is the size...

have you used the proc called "sp_removedbreplication dbname". This will remove all replication objects in the database.

Good luck

When the package is scheduled it creates a job. Open the job properties and in the notify tab select your method of notification.

Good luck.

when you save it as a "structured storage" file format >>> when you open it on the destination server you will need to do a "save as" and save it...

You need to setup a connection alais.

<<< run on the client >>>

Start the Client Network Utility (its in the SQL Server program group).

select the Alais tab >>> click the Add...