You can also use:

sp_helpreplicationdboption 'dbname'

I think that Scan Density shows the true fragmentation value. So you should only be aware of that value. The higher the best.

Are all the subscribers, publishers and distributor of your replication schema with the same service Pack?

Check in the SP3 documentation (in microsoft) for the correct order to apply service packs.

_{You can try running the distribution agent job at the subscriber. With pull subscription, the agent actually runs at the subscriber.}

EM in distributor (Replication Monitor) isn't 100% accurate. But running...

They won't be removed from the subscriber because it doesn't wok like that. The filter is to specify wich transactions at the publisher are sent to the subscriber. This transactions...

Maybe you cvan do smothing like this:

DECLARE @JobID AS UNIQUEIDENTIFIER

SELECT @JobID = job_id

FROM distribution.dbo.MSSnapshot_Agents

WHERE Publication = 'PublicationNameHere'

EXEC msdb.dbo.sp_Start_job @job_id = @JobID

Check this script

http://www.sqlservercentral.com/scripts/contributions/1122.asp

Ih that way I think you can.

But it will be difficult to set up a read only server with replication.

Everytime the replication is done, you will have to pub your...

You can use transaction replication with update subscribers (inmediate or queue).

Or also transactional replication in both servers (with both would be publishers and subscribers)

Or only merge replication.

By modifying replication...

Try executing the xp with named parameters like this:

EXEC master.dbo.xp_sendmail @recipients = 'myid@domain.com' , @subject = 'subject'

Run sp_Helpfile to really know where the data filers are.

Be sure that the disk has enough space for the data files.

Try expanding manually the file/s of the primary file group.

It will depend most of wich permissions are assigned to the public role.

You should check Brian's article

http://www.sqlservercentral.com/articles/articlesexternal.asp?articleid=1258

Sorry, can't help you there.

Check http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=7&messageid=113418

Could work. By using replication you can make sure that both databases are equal at some point in time.

Before migrating, you can set dba1 in single user, to stop transactions,...