Yes, it's supported... the database format is unchanged regardless of the flavour/edition of SQL Server 2008.

Do the tables contain a blob column?

If so, you may be a victim of a known SQL Server 200 bug.

Have a look at my response to this post earlier this...

Is it the distribution database itself, or the transaction log that is growing?

If it's the transaction log, check the recovery model. If it's anything other than simple, you need to...

The list of deleted rows is in the "deleted" table.

Your code

is just retrieving one...

Each replication process is carried out by a SQL Agent job.

You should be able to find your snapshot job (it will have a ctegory "REPL-Snapshot), and then it's just a...

I don't have access to a 2005 system with replication (only 2000 at the moment) to check that this is still valid for 2005.

Have a look in TempDb, and if...

Size shouldn't really matter here (even it does with a lot of other things :-D).

Is the stored procedure just inserting a single row, or many rows?

Are you sure the insert...

Is it just the actual INSERT statement that is slow, or is it the overall execution of the stored procedure you are using that is slow?

If it's the INSERT statement,...

Hold on, I've just re-read your original post, and I think there may be a bit of confusion between publications and subscriptions.

i try using sp_dropmergesubscription and sql answer me "The...

romanoplescia (11/20/2009)

---

P.S What do you mean by this:

The biggest problem I can see with the trigger is that it's referring to the "users" table, not the "inserted" table, so...

If my memory serves me correctly, the details displayed by Replication Monitor are from tables it creates in Tempdb.

Deleted publications don't always seem to be removed from these tables, so...

How do you know it's stopping inserts from happening?

It's an AFTER trigger, so unless you do a ROLLBACK or a DELETE (which I can't see), the original insert should be...

The other column is simply a computed column which is simply adding a character value in front of the primary key data type so that every table can have a...

Mystery solved.

Someone was asked to start the agent immediately, rather than via the schedule, and instead of clicking "Start Synchronizing", clicked "Run Agent at Subscriber". This makes a change to...

Unless you actually need the database restored with STANDBY, leave it as NO RECOVERY.

That should cut the restore time a bit, as SQL Server doesn't have to roll back...