Changing FQDN on SQL Server 2K

Can anybody shed some light on what I might run into when the FQDN is changed
on SQL Server 2K? We are currently in the process of migrating several
domains into a single .NET domain and there are several SQL Server 2K systems
that will be changed. Researching this I have been seeing a lot of
discrepancies, thus I thought I'd run the question through this newsgroup.
Thanks!Thanks for all the assistance, it was greatly appreciated!
"Bryan.S.Walker" wrote:
> Can anybody shed some light on what I might run into when the FQDN is changed
> on SQL Server 2K? We are currently in the process of migrating several
> domains into a single .NET domain and there are several SQL Server 2K systems
> that will be changed. Researching this I have been seeing a lot of
> discrepancies, thus I thought I'd run the question through this newsgroup.
> Thanks!
>

Changing FQDN on SQL Server 2K

Can anybody shed some light on what I might run into when the FQDN is changed
on SQL Server 2K? We are currently in the process of migrating several
domains into a single .NET domain and there are several SQL Server 2K systems
that will be changed. Researching this I have been seeing a lot of
discrepancies, thus I thought I'd run the question through this newsgroup.
Thanks!
Thanks for all the assistance, it was greatly appreciated!
"Bryan.S.Walker" wrote:

> Can anybody shed some light on what I might run into when the FQDN is changed
> on SQL Server 2K? We are currently in the process of migrating several
> domains into a single .NET domain and there are several SQL Server 2K systems
> that will be changed. Researching this I have been seeing a lot of
> discrepancies, thus I thought I'd run the question through this newsgroup.
> Thanks!
>

Changing FQDN on SQL Server 2K

Can anybody shed some light on what I might run into when the FQDN is change
d
on SQL Server 2K? We are currently in the process of migrating several
domains into a single .NET domain and there are several SQL Server 2K system
s
that will be changed. Researching this I have been seeing a lot of
discrepancies, thus I thought I'd run the question through this newsgroup.
Thanks!Thanks for all the assistance, it was greatly appreciated!
"Bryan.S.Walker" wrote:

> Can anybody shed some light on what I might run into when the FQDN is chan
ged
> on SQL Server 2K? We are currently in the process of migrating several
> domains into a single .NET domain and there are several SQL Server 2K syst
ems
> that will be changed. Researching this I have been seeing a lot of
> discrepancies, thus I thought I'd run the question through this newsgroup.
> Thanks!
>