what is the output of

select i.name

from dbo.sysindexes i

inner join sysobjects o on i.id = o.id

Left Join maxtable m on m.tablename = ''

where i.indid > 0 and i.indid < 255...

Hi Paul,

I am facing the same issue:

Error: 845, Severity: 17, State: 1

Time-out occurred while waiting for buffer latch type 4 for page (1:407399), database ID 7.

I get this in eventvwr,...

it depends:

http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/41717364-4c30-4a6f-abb8-845e951e1c4d

My understanding on this is .... create a index where you require it most. for me. it could be possible that publisher is require different index then subsriber depending upon...

Just for your information,

Log reader Job : reads the transaction log data which is changed and move to distribution database.

Distributor Job: distributes /transafers the data to subsriber.

Please see. log reader...

Please see the link below.

http://www.codeproject.com/KB/database/ImageSaveInDataBase.aspx

http://msdn.microsoft.com/en-us/library/a1904w6t%28VS.80%29.aspx

http://www.informit.com/articles/article.aspx?p=377078

HTH

Vinay

Please check.

http://blogs.msdn.com/chkoenig/archive/2008/12/01/upgrading-from-sql-2000-2005-to-2008.aspx

also video:

http://blogs.msdn.com/chkoenig/archive/2008/12/01/upgrading-from-sql-2000-2005-to-2008.aspx

HTH

Vinay

Thanx ALZDBA,

Its not always same object.

we are tring to upgrade to sp4. Already confirm with hillery clitter about upgrade will not require to resetup replication here.

We dont have AWE enabled...

Thanx AlZDBA, this happend again but for different server, I dont think it is due to deadlock as that time nothing runs except log reader.

We are facing an issue on...

I am glad it helped...

Sorry for confusion,

follow this

declare @JobID uniqueidentifier

select @JobID=job_id from distribution.dbo.MSdistribution_agents a,master.sys.servers s

where a.publisher_db=['PublisherDB'] and

a.subscriber_db=['Destination_DB'] and

a.subscriber_id=s.srvid and

s.srvname=['SubsriberServer']

--this will give jobid for the replication we have created, just use that jobid and...

please follow below steps as well. as @distribution_jobname will not create job with new name, we have to refer that name to rename our job name with the below steps.

------------------get...

check weather data is replicated to subsriber once. if yes for now you can have following work around:

https://blogs.technet.com/claudia_silva/archive/2009/05/04/replication-distribution-cleanup.aspx

use [DB_name]

exec sp_addsubscription @publication = N'[Pub_server_name]', @subscriber = N'[Sub_server_name]', @destination_db = N'[DB_dest_name]', @subscription_type = N'Push', @sync_type = N'replication support only', @article = N'Program', @update_mode = N'read...

More information on this.

exec sp_addsubscription ....,@distribution_job_name ='Distribution1'

Here @distribution_job_name is system use only but if we provide value to this, it will keep it for internal tables for replication,and which...