Hi Mark,
Thank you for you valuable answer, sorry for getting back so late but I wanted our DBA to reload the initial dump to do an analysis based on your answer and make sure I understood it.
Therefore if I go back to your explanation.
for point1.
output of sp_reptostandby tells me this database is/was a source for replication.
Moreover sp_setreplicate lists 70 tables so my conclusion at this level is these 70 tables were/are replicated
For point2.
sp_help_rep_agent <dbname> outputs my db is not configured to use Replication Agent.
As you mention, rep agent configuration 'should be' in the dump but as I'm not sure I can't strongly confirm the source database has a replication agent configured.
For point3.
master..syslogshold does not have any rows with name='$replication_truncation_point'. My assumption is replication is not active.
But if I look at the output of dbcc gettrunc, I'm a bit lost again because I have an entry
col1=8113058 (first page not truncated in the log)
col2=0 (Adaptive Server ignores the truncation page), what does it mean actually?
col3=142, what's the meaning of this value.
...
Even though your explanations were cleared the 'test-case' I'm facing is not straigh forward for me because on my hand I can confirm the database was/is marked for replication but as repAgent wasn't configured nor start and no truncation point visible in master..syslogshold.
If you can clarify my assumption it'll be very helpfull.
So far we just executed 'dbcc settrunc(ltm,'ignore') and it solves our LOG SUSPEND issue but I'd like to understand and not doing things mechanically.
Thank you
Simon