DR replication-how to's

Let me start with this: We have a critical SQL application on a Win 2003
with SQL 2000 sp3a. I set up another Win 2003 server with SQL 2000 sp3a.
From posts read I believe log shipping is what I want, the files can be
replicated overnight and appears to be easiest to manage. OK, my questions:
do I want log shipping? Is that the easiest way for DR purposes, ie recovery
time?
Also, I'm running into problems and I can't seem to find a simple how to do
this on microsoft's site. My number one problem appears to stem from the
initial installation, it was submitted as a local instance. Is there a way
around this? Say, make the backup server as the distrubutor and subscriber
and then make the main a publisher?
Another problem I'm having is that it's failing on the Distrubutor portion,
it's saying it fails because it is a local system account. WHen I go tto
change the account every user on the server is either unknown or invalid.
Does anyone know a solution for this? Is there any documentation? I can't
seem to find help on microsoft's site.
First off, log shipping is probably the best choice for a DR solution.
Replication can work, but you need to do a fair amount of configuring to
make this work.
I am a little confused by your second and third questions. You suddenly
start talking about replication.If you are talking about a remote
distributor, then it seems like you are using replication to provide DR.
Please review this kb article to understand the complexity of what you are
trying to do.
http://support.microsoft.com/default...b;en-us;886839
I think you third problem results from not having created a local NT user
account. Create this account, put it in the sys admins role, and then have
SQL Server agent run under this account.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:3E7923F1-C4D3-46D0-830E-0DCB04236C55@.microsoft.com...
> Let me start with this: We have a critical SQL application on a Win 2003
> with SQL 2000 sp3a. I set up another Win 2003 server with SQL 2000 sp3a.
> From posts read I believe log shipping is what I want, the files can be
> replicated overnight and appears to be easiest to manage. OK, my
questions:
> do I want log shipping? Is that the easiest way for DR purposes, ie
recovery
> time?
> Also, I'm running into problems and I can't seem to find a simple how to
do
> this on microsoft's site. My number one problem appears to stem from the
> initial installation, it was submitted as a local instance. Is there a
way
> around this? Say, make the backup server as the distrubutor and
subscriber
> and then make the main a publisher?
> Another problem I'm having is that it's failing on the Distrubutor
portion,
> it's saying it fails because it is a local system account. WHen I go tto
> change the account every user on the server is either unknown or invalid.
> Does anyone know a solution for this? Is there any documentation? I
can't
> seem to find help on microsoft's site.
sql

Domain name change for MS SQL 2005

Any help will be appreciated.
To clarify few things I have no previous MS SQL experience, did some Oracle and MySQL work.
I will have to move one Win 2000 server with MS SQL 2005 running one database to our AD 2003 environment. I was wondering if anybody already went through that kind of scenario, and what was the procedure.
Thanks

let me understand the scenario

you have sql server 2005 running on Win 2000 ADS machine (Same physical machine) and you want to migrate windows 2000 to 2003 and transfer sql server 2005 to new ADS 2003 machine.

is this the requirement?

Madhu

|||I wasn't clear enough.
We have to move a windows 2000 server from one domain to another. That server has SQL 2005 installed and we are using it as our accounting database. We have to keep that server and it's 2005 SQL database functional on our domain. We will not upgrade that server to win 2003. Recently we acquired another company and this is the only problem that is stopping us from connecting both networks.

Doing demos with SQL2K RS Developer

Hi there.
I need to know if there's a proper setup to have SQL 2k Developer Edition
and SQL 2k RS Developer Edition on top of Win XP Pro to demo some reports.
I have locally installed VS .Net 2003 professional, SQL 2K Developer, SQL 2K
RS Developer, SQL 2K AS and IIS on top of Windows XP and RS does not ran if
I'm not connected to corporate network.
I have no way to make RS work on the road or at customers networks to show
some nice reports we have built...
I even installed SQL 2K RS Sp1 and it has no effect
Do I need to format my notebook and Install Win 2000?
Is it a setup problem?
Is it a licensing restriction?
Thank you very much for your support
Michael PrendergastSearch this newsgroup for "loopback":
http://groups-beta.google.com/group/microsoft.public.sqlserver.reportingsvcs/search?group=microsoft.public.sqlserver.reportingsvcs&q=loopback&qt_g=1&searchnow=Search+this+group
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"MPS" <mps@.udd.cl> wrote in message
news:u$M4kf29EHA.2996@.TK2MSFTNGP10.phx.gbl...
> Hi there.
> I need to know if there's a proper setup to have SQL 2k Developer Edition
> and SQL 2k RS Developer Edition on top of Win XP Pro to demo some reports.
> I have locally installed VS .Net 2003 professional, SQL 2K Developer, SQL
> 2K RS Developer, SQL 2K AS and IIS on top of Windows XP and RS does not
> ran if I'm not connected to corporate network.
> I have no way to make RS work on the road or at customers networks to show
> some nice reports we have built...
> I even installed SQL 2K RS Sp1 and it has no effect
> Do I need to format my notebook and Install Win 2000?
> Is it a setup problem?
> Is it a licensing restriction?
> Thank you very much for your support
> Michael Prendergast
>