Have a look at article "Error 823" in books on line. 

Based on what this article says, it sounds like the error will most likely have been caused by a...

The only thing that I think could get you is replication may not generate the same schema as exists on the source database.  e.g. primary keys become unique constraints.

I think you...

This ain't easy to monitor. 

If it was an option, you would put triggers on the relevant system tables BUT this is not supported by MS.

What you could do is...

Indexed Views are equivalent to Materialised Views in Oracle.

There is no equivalent in MySQL. 

SQL Server by design uses as much memory as it can get subject to other demands on the server.  If there are no other processes requiring memory, there is no...

Intellisense = Yukon.  We just need hang out a little longer 'til we can catch up with the rest of the development world.

You could use transactional replication with immediate updating subscribers if you have reliable network links between the 2 servers.

You also can use transactional replication with queue updates if you are...

First things first - do you have a need to shrink the database.

If the database is going to grow during the week anyway, everytime it needs to grow, your users...

Snapshot replication will not create tables with IDENTITY "property". It will create the table but any column that has identity on the published will not have identity at the subscriber.You...

Adding a table to an existing publication is VERY SIMPLE. You can use sp_addarticle to do this.

This will add the table to the publication but with no...

Try increasing the QueryTimeout value first. I have successfully used this to work around temporary outages in the past.

Depending on the length of the outages you are...

There should be no problems with this (assuming that the server itself has capacity to handle the additional load)

I suspect that the problems with triggers may be because prior to SQL 2000, if a trigger (on a table with IDENTITY) happens to insert a record into another table...

For replication, the recommendation has always been to ensure that (at least) the distribution server is at the highest version/most recent service pack.

Cheers

Stephen

All steps have at most one precedence constraint. Having said that, there are tasks that have two tasks as the next task to run.

I have changed the package so...