Internally sql server uses SID of NT users to link them
with sql logins. I don't know if NT will preserve SIDs
when users are migrated to another domain. If it does then
users can login with Domain2\user1 and still have same
permissions in sql server based on their SID stored in
sysxlogins table, though their username will be displayed
as Domain1\user1. You can update sysxlogins table and
change users display name.
If users are assigned new SID by NT then I am afraid you
have to add them again and assign permisstions.
hth.
>--Original Message--
>We are in the process of collapsing a domain. How do i
change the database permissions to reflect the new domain
names. Example Domain1\user1 is migrated to Domain2. user1
is now Domain2\user1. In SQL, the user is still displayed
as Domain1\User. Any idea. Thanks in advance.
>.
>When they are migrated to nt the sid stays the same. so the permission shoul
d be ok from your info. Thanks for the help.
Showing posts with label migrated. Show all posts
Showing posts with label migrated. Show all posts
Friday, February 24, 2012
Domain change has affected SQL need help
Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well
,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
>
>
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well
,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
>
>
Domain change has affected SQL need help
Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
Joe
Joe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
> Joe
|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
>
>
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
Joe
Joe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
> Joe
|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
>
>
Domain change has affected SQL need help
Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question :(
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question :(
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> > Hey,
> >
> > One of my clients has migrated from an old NT domain to an AD domain with
> > Win2K servers. When the migration was performed, SQL 7.0 came across as
> > well,
> > but now displays some strange characteristics. NT authentication no longer
> > works, only SQL authentication.
> > The MS Search service does not start but I have an article to fix this.
> >
> > Do I need to do anything else to SQL besides the MS Search service to get
> > SQL seeing the new domain correctly?
> >
> > I was never involved in the move of SQL, and now this damn server runs a
> > mission-critical CRM package on SQL that can in no way be interupted or go
> > down during the day, and rebuilding is out of the question :(
> >
> > Any help would be appreciated.
> > SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> >
> > Joe
>
>
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question :(
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question :(
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> > Hey,
> >
> > One of my clients has migrated from an old NT domain to an AD domain with
> > Win2K servers. When the migration was performed, SQL 7.0 came across as
> > well,
> > but now displays some strange characteristics. NT authentication no longer
> > works, only SQL authentication.
> > The MS Search service does not start but I have an article to fix this.
> >
> > Do I need to do anything else to SQL besides the MS Search service to get
> > SQL seeing the new domain correctly?
> >
> > I was never involved in the move of SQL, and now this damn server runs a
> > mission-critical CRM package on SQL that can in no way be interupted or go
> > down during the day, and rebuilding is out of the question :(
> >
> > Any help would be appreciated.
> > SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> >
> > Joe
>
>
Subscribe to:
Posts (Atom)