do I need to enable cross database ownership chaining for merge repl?

I have seen conflicting info on this one:
Do I need to enable cross database ownership chaining on databases that
participate in Merge replication (publishers and subscribers)? I have seen
info pointing to maybe yes, maybe no...
anyone have comments on this?
DJC,
I'm not aware of any issues having been reported.
In what context have you heard of problems arising? Maybe from the SP3
readme - there was an issue which has been clarified in the ReadMe
additions:
Clarification to Section 5.3.17 - Change to Requirements for Attaching or
Restoring a Replication Database
Section 5.3.17 "Change to Requirements for Attaching or Restoring a
Replication Database" in the SQL Server 2000 SP3 Readme file incorrectly
implies that enabling cross-database ownership chaining is a requirement for
attaching or restoring replication databases after SQL Server 2000 SP3 has
been applied. The preferred method for attaching or restoring databases
after applying SQL Server 2000 SP3, is to have a member of the sysadmin
fixed server role run the sp_changedbowner stored procedure to assign
ownership of the database to the sa built-in administrator logon. For
example:
Regards,
Paul Ibison
sql

Do I need /PAE to enable AWE memory?

Hi All
I am running Windows 2000 Advanced Server with SQL 2K
Enterprise. I now have 8 GB of RAM and am using the /3GB
switch in the BOOT.INI file. I want to enable AWE within
SQL but some documentation says that the /PAE switch is
also required within the BOOT.INI file. Is this correct?
I don't want to use the /PAE unless I have to.
Will the /3GB switch, together with enabling AWE in SQL
allow SQL to see all but 128MB of the 8GB of RAM (i.e.
no /PAE)?
Many thanks
H
Sample boot.ini for 8GB memory usage:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000 Advanced Server" /fastdetect /PAE
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microso ft W2K 2000 Advanced Server" /fastdetect /PAE
JBandi
|||No. Without PAE the server only sees up to 4GB.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Do I need /PAE to enable AWE memory?

Hi All
I am running Windows 2000 Advanced Server with SQL 2K
Enterprise. I now have 8 GB of RAM and am using the /3GB
switch in the BOOT.INI file. I want to enable AWE within
SQL but some documentation says that the /PAE switch is
also required within the BOOT.INI file. Is this correct?
I don't want to use the /PAE unless I have to.
Will the /3GB switch, together with enabling AWE in SQL
allow SQL to see all but 128MB of the 8GB of RAM (i.e.
no /PAE)?
Many thanks
HSample boot.ini for 8GB memory usage:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft Windows 2000 Advanced S
erver" /fastdetect /PAE
multi(0)disk(0)rdisk(0)partition(2)\WINN
T="Microsoft W2K 2000 Advanced Serve
r" /fastdetect /PAE
JBandi|||No. Without PAE the server only sees up to 4GB.
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...