migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!
You want to start with this:
http://support.microsoft.com/kb/246133/
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>
|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>
|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:

> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!
|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!
|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:

> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.
|||The script can be download from:
http://download.microsoft.com/downlo...us/mapsids.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.

migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
--
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!You want to start with this:
http://support.microsoft.com/kb/246133/
--
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
--
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>> You want to start with this:
>> http://support.microsoft.com/kb/246133/
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.|||The script can be download from:
http://download.microsoft.com/download/sqlsvr2000/utility/5.0/win98me/en-us/mapsids.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
--
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>> Yes, follow the instruction in this kb. sp_sidmap should help resolve
>> your
>> issue.
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.sql

migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!You want to start with this:
http://support.microsoft.com/kb/246133/
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:

> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:

> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.|||The script can be download from:
http://download.microsoft.com/downl...id
s.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
Pablo
Hi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
--
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>sql

Microsoft.Data.Odbc on 64-Bit Server

Hi!

Today we installed our ASP.NET Application on a 64-bit server for the first time. We got the error'Unable to find entry point named 'InterlockedIncrement' in DLL 'kernel32.dll''.

This error comes when we make a database query using Microsoft.Data.Odbc. I think it does not run on 64-bit machines.

Does anybody know something about this?

KaaN

I don't know why you need it with ODBC datasource but the link below Microsoft explains the reason for you error. Hope this helps.

(The variable pointed to by the Addend parameter must be aligned on a 32-bit boundary; otherwise, this function will behave unpredictably on multiprocessor x86 systems and any non-x86 systems.)

http://msdn2.microsoft.com/en-us/library/ms683614.aspx

|||

Thanks for your answer.

Actually I don't need this xxIncrement method, I only need the .Net Odbc Provider and probably this provider is using this function. Now I have to refactor my code to native providers or find another .Net ODBC Provider.

Microsoft SQL Server, Error: 87 17march

Source computer: SQL server 2005 SP1
Remote computer : SQLEXPRESS
When I try to register/connect with remote server (named instance) using sql
server management studio I am getting following error:
TITLE: New Server Registration
--
Testing the registered server failed. Verify the server name, login
credentials, and database, and then click Test again.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 25 - Connection string is not
valid) (Microsoft SQL Server, Error: 87)
Thanks
Ontario, canadaSource computer: SQL server 2005 SP1 (Microsoft windows nt 5.1)
Remote computer : Microsoft SQL server express edition (Microsoft windows
nt 5.1)
-
ontario, canada
"db" wrote:
> Source computer: SQL server 2005 SP1
> Remote computer : SQLEXPRESS
>
> When I try to register/connect with remote server (named instance) using sql
> server management studio I am getting following error:
> TITLE: New Server Registration
> --
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 25 - Connection string is not
> valid) (Microsoft SQL Server, Error: 87)
>
> Thanks
> Ontario, canada

Microsoft SQL Server, Error: 87 17march

Source computer: SQL server 2005 SP1
Remote computer : SQLEXPRESS
When I try to register/connect with remote server (named instance) using sql
server management studio I am getting following error:
TITLE: New Server Registration
Testing the registered server failed. Verify the server name, login
credentials, and database, and then click Test again.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 25 - Connection string is not
valid) (Microsoft SQL Server, Error: 87)
Thanks
Ontario, canada
Source computer: SQL server 2005 SP1 (Microsoft windows nt 5.1)
Remote computer : Microsoft SQL server express edition (Microsoft windows
nt 5.1)
-
ontario, canada
"db" wrote:

> Source computer: SQL server 2005 SP1
> Remote computer : SQLEXPRESS
>
> When I try to register/connect with remote server (named instance) using sql
> server management studio I am getting following error:
> TITLE: New Server Registration
> --
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 25 - Connection string is not
> valid) (Microsoft SQL Server, Error: 87)
>
> Thanks
> Ontario, canada