+1

your original point advanced was well-made, and I concur with your follow-up that most?all politics/arguments start with subjective PoV

- the questions are whether a presenter makes a sufficient case, and...

Jeff, Hi

try this instead

https://www.telegraph.co.uk/news/2021/06/15/fear-freedom-doom-laded-government-graphs-dont-show-us/?fbclid=IwAR30zEscQDhPlr1KR0JWI5nFBz3un5_JLBoC4ZMPAdLVm74aoSLwCgk8k84

but in case you don't read newspapers either (too much bad news) the article was entitled

"Fear over freedom: Here's what the doom-laden government graphs didn't show...

here is another prime example of selective filtering

https://www.facebook.com/ed.green.127/posts/4241448059299955?notif_id=1623782606067696&notif_t=nf_share_story&ref=notif

read the post before MSM / woke brigade / censor take it down !

should not be necessary [and doubtless a pain in the bu44]

- If you are not already on latest SP I suggest you upgrade first if feasible

suggest you wire up repl...

the LogReader agent [on Distributor] reads changes from your userdb's tranlog and posts into the distribution db [and should keep up with your change rate]. The userdb's tranlog will NOT stay...

You will find that there is a different Snapshot job - one for each pub.

Also one LogReader job per db

but you have the option to set @independent_agent=false if you WANT...

There is a difference between @@IDENTITY and scope_identity() - read up in BOL

- perhaps other triggers are firing to write into audit table and thats the number you're getting.

can you...

if you use ALT PrintScrn keyboard keystrokes you can capture the current window

- can crop etc in mspaint and/or drop into word etc

there is also a good tool "Snag-It" that...

When you configure for repl [to be a pub] you designate the Dist too [usually same box] which adds a fistfull of sytem tables and the distribution db.

You do not...

The SQL2005 replication options are

Snapshot

Transactional

Merged

Peer-to-Peer [new]

or browse this for more details

http://msdn2.microsoft.com/en-us/library/ms151198.aspx

I suggest you have ONE publication for cope with ALL the branches [you can zone by geography to avoid...

I would

1. backup the db as-is [at least has metadata even if no data]

2. drop the db

3. change model to be more generous with autogrows [100MB each recommended] and ceiling

4....

perhaps the transaction log OR DIS(S) WERE full ??

- default autogrow (increment,ceiling) for (data,tlog) comes from model

you could try a re-run and watch the tlog

DBCC SQLPERF(LOGSPACE)

The SQLAgent job has an owner, and this is checked before the job can be started.

inidividual jobsteps can have a workflow to other steps in the same job

- eg step...

you can use a Linked-Server [yuch!] as an indirection pointer, or on SQL2005 you can

CREATE SYNONYM [ schema_name_1. ] synonym_name FOR < object >< object > :: ={    [...

your view should surface all the relevant PK's so the view can hit the appropriate base table.

but you might be interested in this experiment [same for TSQL and in SSMS...