would be better NOT to use the sp_ prefix !

this is clear in BOL

[font="Courier New"]We strongly recommend that you not use the prefix sp_ in the procedure name. This prefix...

searching the MS sites I found this oldie

http://weblogs.asp.net/cazzu/archive/2004/07/16/SharedMemoryError.aspx

which suggested problems with not using explicit instance names

- suggest you remove and re-register instance name if using "." or (local)...

any pub with independent_agent=true will have its own DistribAgent (eg SysA_Pub1). If you have 5 such pubs that would mean 5 windows processes (each running distrib.exe visible in taskmanager).

If you...

BOL has lots of technical detail but sometimes not much wisdom. The forums would be more focussed if people at least used BOL for what it IS good for.

You suggest...

all explained in BOL which should be your first port of call

- either as installed on your PC or the online MS-website

specific pages at

http://msdn.microsoft.com/en-us/library/ms173857.aspx

Dick

we use @schema_option = 0x00000000080350DB so I commend this for you to try

you should be able to edit your generation script for all such sp_addarticle calls

let the community know how...

"Enterprise Manager" and "OSQL" in 2008, when SQL2005 brought in SSMS and SQLCMD ??

on a more worrying note the author makes no allowance for errors

- network, deadlocking, resource, shutdowns etc...

the SSMS (GUI) wizard is over-protective in this case ...

you can use SSMS to replicate

svr1.db1.dbo.tbl1 -> svr1.db2.dbo.tbl1

and produce scripts. then edit the subscription script to change all "db2.dbo.tbl1" to "db1.dbo.tbl2"...

of course you can't repl from svr1.db1.dbo.tbl1 -> svr1.db1.dbo.tbl1

- i.e. pub source to same sub target

but you can do to

-> svr1.db1.dbo.tbl2

-> svr1.db1.xyz.tbl1

-> svr1.db2.dbo.tbl1

-> svr2.db1.dbo.tbl1

where svr2 could be another instance on...

security accounts come from the domain [may be AD] or local SAM if standalone

- this defines account names and SIDs (ugly GUID things!)

if you have re-installed the O/S this means...

your networking experts should be able to advise what ports are/not allowed through the FW

- many sites have a strict HTTP-only (HTTP=port=80, HTTPS port=443) policy and forbid SQL (ports 1433,...

in any sane business you would place the SQL servers in the corporate zone and not DMZ

- therefore an external (domain2 Distrib) would have to pass through 2 FW's (ie...

SCRIPTIO was initially written by Bill Graziano in MS SQLTeam but now lives at

http://www.codeplex.com/scriptio

so you can get latest, code, docs etc from there

Dick

1. in ancient times [~Sybase] there were only SQL-logins that requires password, but SQLServer has had Windows integrated (domain logins whether NT4 or Win200x AD with Kerberos) where the O/S...

try scriptio from the MS SQL team, installable from

http://www.sqlteam.com/publish/scriptio

and the .NET source-code is also available.

The underlying code library is SMO so you can cobble together code to do...