"Joseph" <josephsheppard@gmail.com> wrote in message
news:1168795376.104798.223490@38g2000cwa.googlegroups.com...
> Thank you for the information, and your recommendation, Hilary...I am
> under some constraints that do not allow me to use
> transactional...mainly, we're using the desktop version of MSSQL2k at
> the locations.
>
> The 'warehouse' is merely another instance of the database containing
> all of the locations data, updated daily. It does indeed have poor
> performance, taking 4 1/2 hours to populate.
>
> Thanks again!
> Joseph
>
> Hilary Cotter wrote:
>> I would strongly not recommend merge replication for a data warehouse as
>> it
>> doesn't offer good performance, and is designed for bi-directional
>> replication. You should IMHO use transactional replication for this.
>>
>> To get an idea of the last time a job ran or a sync/merge happened look
>> at
>> the MSmerge_history table in the distribution database.
>>
>> --
>> Hilary Cotter
>>
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>>
>>
>> "Joseph" <josephsheppard@gmail.com> wrote in message
>> news:1168696977.895024.283510@l53g2000cwa.googlegroups.com...
>> >I would like to build my warehouse with replicated data...I would like
>> > to report the last time a particular location merged.
>> >
>> > What is the best way to programatically determine the last time a
>> > location replicated successfully?
>> >
>> > I'm sure there are tables that contain the agents and their statuses,
>> > so that's a possibility.
>> >
>> > I'm playing with the idea of trying to attach a step or job to each
>> > Merge agent to populate a User table containing last replication
>> > attempts, in DTS fashion.
>> >
>> > TIA!
>> >
>