Changing the SQL SErver DOmain

Hello,
Anybody knows what's the effects caused by a Server Domains Change?
I'm planning to change a Domain of my SQL Server that actually has a trust
with the current Domain of this server.
I think that I don't need to do nothing after this change. I'm correct?
Thanks
Juliano Horta
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
Hello,
Take a look into the google archive for the similar topic.
[url]http://groups.google.com/group/microsoft.public.sqlserver.connect/browse_frm/thread/3533c9535e06f49e/b6ea4289a0ead18c?lnk=st&q=changing+sql+server+doma in&rnum=19&hl=en#b6ea4289a0ead18c[/url]
Thanks
Hari
"julianohorta via droptable.com" <u13014@.uwe> wrote in message
news:6e89b9509fcf6@.uwe...
> Hello,
> Anybody knows what's the effects caused by a Server Domains Change?
> I'm planning to change a Domain of my SQL Server that actually has a trust
> with the current Domain of this server.
> I think that I don't need to do nothing after this change. I'm correct?
> Thanks
> Juliano Horta
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
>
sql

Changing the SQL SErver DOmain

Hello,
Anybody knows what's the effects caused by a Server Domains Change?
I'm planning to change a Domain of my SQL Server that actually has a trust
with the current Domain of this server.
I think that I don't need to do nothing after this change. I'm correct?
Thanks
Juliano Horta
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1Hello,
Take a look into the google archive for the similar topic.
http://groups.google.com/group/microsoft.public.sqlserver.connect/browse_frm/thread/3533c9535e06f49e/b6ea4289a0ead18c?lnk=st&q=changing+sql+server+domain&rnum=19&hl=en#b6ea4289a0ead18c
Thanks
Hari
"julianohorta via SQLMonster.com" <u13014@.uwe> wrote in message
news:6e89b9509fcf6@.uwe...
> Hello,
> Anybody knows what's the effects caused by a Server Domains Change?
> I'm planning to change a Domain of my SQL Server that actually has a trust
> with the current Domain of this server.
> I think that I don't need to do nothing after this change. I'm correct?
> Thanks
> Juliano Horta
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1
>

Changing the SQL SErver DOmain

Hello,
Anybody knows what's the effects caused by a Server Domains Change?
I'm planning to change a Domain of my SQL Server that actually has a trust
with the current Domain of this server.
I think that I don't need to do nothing after this change. I'm correct?
Thanks
Juliano Horta
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1Hello,
Take a look into the google archive for the similar topic.
http://groups.google.com/group/micr...6ea4289a0ead18c
Thanks
Hari
"julianohorta via droptable.com" <u13014@.uwe> wrote in message
news:6e89b9509fcf6@.uwe...
> Hello,
> Anybody knows what's the effects caused by a Server Domains Change?
> I'm planning to change a Domain of my SQL Server that actually has a trust
> with the current Domain of this server.
> I think that I don't need to do nothing after this change. I'm correct?
> Thanks
> Juliano Horta
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200703/1
>

Changing domains and SQL Server connectivity problem

Hi,
My firm will soon need to join the domain of our global firm. Currently I
have 4 SQL Servers in my old domain with replication setup. I have setup a
test server and I have found that clients within the old domain have no
access to the SQL Server in the new domain, but clients in the new domain
have access in the SQL Server of the old domain.
What do I need to do so that clients within the old domain have access to
the SQL Server in the new domain?
"Chris Themi" <ChrisThemi@.discussions.microsoft.com> wrote in message
news:F607969E-928C-4D58-BB7B-537E95BEF320@.microsoft.com...

> My firm will soon need to join the domain of our global firm. Currently I
> have 4 SQL Servers in my old domain with replication setup. I have setup a
> test server and I have found that clients within the old domain have no
> access to the SQL Server in the new domain, but clients in the new domain
> have access in the SQL Server of the old domain.
> What do I need to do so that clients within the old domain have access to
> the SQL Server in the new domain?
It sounds like you need to set up another domain trust, have your new domain
trust your old domain. Add your client accounts in the old domain into the
appropriate groups in the new domain (that have SQL Server access).
Steve

Changing domains and SQL Server connectivity problem

Hi,
My firm will soon need to join the domain of our global firm. Currently I
have 4 SQL Servers in my old domain with replication setup. I have setup a
test server and I have found that clients within the old domain have no
access to the SQL Server in the new domain, but clients in the new domain
have access in the SQL Server of the old domain.
What do I need to do so that clients within the old domain have access to
the SQL Server in the new domain?"Chris Themi" <ChrisThemi@.discussions.microsoft.com> wrote in message
news:F607969E-928C-4D58-BB7B-537E95BEF320@.microsoft.com...

> My firm will soon need to join the domain of our global firm. Currently I
> have 4 SQL Servers in my old domain with replication setup. I have setup a
> test server and I have found that clients within the old domain have no
> access to the SQL Server in the new domain, but clients in the new domain
> have access in the SQL Server of the old domain.
> What do I need to do so that clients within the old domain have access to
> the SQL Server in the new domain?
It sounds like you need to set up another domain trust, have your new domain
trust your old domain. Add your client accounts in the old domain into the
appropriate groups in the new domain (that have SQL Server access).
Steve

Changing domains and restoring db's

I have a 2000 server that also runs SQL 7.0.
This server is a PDC of domain "A". It also happens to be
the only server on the domain.
I am tasked to eliminate this domain and bring this server
into domain "B". I have been told that unfortunately, I
will have to FDISK this guy to scratch and reinstall OS,
SQL, everythng, to bring him into new domain.
Is this true?
Also, the SQL has some pretty big databases and of course
they are backed up nightly, but I was hoping not to have
to restore these db's from tape but instead, copy the
databases over to another server, then copy them back
after I have reinstalled the server and brought him into
domain "B".
Can I do this and what do I need to know how to go about
this?"Rick" <anonymous@.discussions.microsoft.com> wrote in message
news:00aa01c39991$10541780$a501280a@.phx.gbl...
> I have a 2000 server that also runs SQL 7.0.
> This server is a PDC of domain "A". It also happens to be
> the only server on the domain.
> I am tasked to eliminate this domain and bring this server
> into domain "B". I have been told that unfortunately, I
> will have to FDISK this guy to scratch and reinstall OS,
> SQL, everythng, to bring him into new domain.
> Is this true?
> Also, the SQL has some pretty big databases and of course
> they are backed up nightly, but I was hoping not to have
> to restore these db's from tape but instead, copy the
> databases over to another server, then copy them back
> after I have reinstalled the server and brought him into
> domain "B".
> Can I do this and what do I need to know how to go about
> this?
First make sure that the SQL services are not running under a domain
account. Go to the services applet and change the SQL services to use a
local system login (note: from this point SQL won't be able to use network
resources).
Then run dcpromo. Tell the wizard that this is the last domain controller
in the domain. This should turn it into a standalone server. Then you
should be able to join domain B and run the SQL services under a new domain
account.
To transfer databases from one SQL server to another use the DTS wizard from
Enterprise Manager. It has an option to transfer all objects from one SQL
database to another.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 22/10/2003|||So you're saying that I do not have to FDisk this server
and reinstall everything? I can just turn it into a
standalone server first and then bring it into a new
domain?
If that is the case, then I wouldn't have to do anything
to the SQL portion right? I'd just leave it as is?