Migrate SQL Server 2000 to SQL Server 2005: login

Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin

> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>|||Check out:
http://support.microsoft.com/defaul...kb;en-us;246133
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:ejLryIm1GHA.4264@.TK2MSFTNGP05.phx.gbl...
Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)|||The best way to do this is to transfer the logins with sp_help_revlogin to a
clean server - i.e. one with no logins. Do this just before you want to cut
over or advise your users that their password won't be current on the new
box if they change their passwords on the old box after you've transferred
them. You won't need sp_change_users_login in that case.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:%23Xf$aNm1GHA.4908@.TK2MSFTNGP02.phx.gbl...
Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin

> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>

Migrate SQL Server 2000 to SQL Server 2005: login

Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin
> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>|||Check out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:ejLryIm1GHA.4264@.TK2MSFTNGP05.phx.gbl...
Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)|||The best way to do this is to transfer the logins with sp_help_revlogin to a
clean server - i.e. one with no logins. Do this just before you want to cut
over or advise your users that their password won't be current on the new
box if they change their passwords on the old box after you've transferred
them. You won't need sp_change_users_login in that case.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:%23Xf$aNm1GHA.4908@.TK2MSFTNGP02.phx.gbl...
Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin
> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>sql

Migrate Login Control to SQL

Hi,

I was able to create an MSSQL database with the ASPNETDB.MDF file. But how do I get the Login Control to point to the MSSQL rather than the \App_Data\ASPNETDB.MDF file?

Hi

you need to see This

Configuring ASP.NET 2.0 Application Services to use SQL Server 2000 or SQL Server 2005

|||

check out below solved thread..

Login control And DB - ASP.NET Forums

you might need to include the tables and stored procedure which requires for login control into your DB...

hope it helps./.

Microsoft Web Data Administrator, hangs on log in

Hi
I have downloaded MS Web Data Administrator to conenct to my MSDE
database. It hangs when i login using "SQL Login"
When i open up Web Data Administrator, it defaults to Port 80 and
Cassini Personal Web Server (the "IIS" button has been disabled).
Once I start Web DA with this information, and enter in the following
under an "SQL login"
Username: sa
Password: ****
Server: myServerName\myMSDEDatabase
and press "Login" it does nothing (seems to hang) and im left on the
log in page...I never get an error message, it just keeps on trying to
log in, i presume.
I am running MSDE on Win 2000 Server. MSDE is set up to use SQL
authentication (instead of Windows)
Any suggestions?
--Pam
Hi, I found this floating around on the web and did as it instructed,
but it still doesn't work!
___________________________________________
Christopher Hill Feb 7, 6:40 am show options
Newsgroups: microsoft.public.sqlserver.msde
From: "Christopher Hill" <min...@.ntlworld.com> - Find messages by this
author
Date: Mon, 7 Feb 2005 03:40:46 -0800
Local: Mon,Feb 7 2005 6:40 am
Subject: SOLUTION: SQL Web Data Administrator hangs on login
Reply to Author | Forward | Print | View Thread | Show original |
Report Abuse
(Also posted to
http://register.microsoft.com/=ADmswish/suggestion.asp)
The SQL Web Data Administrator (available here:
http://www.microsoft.com/downl=ADoad...C03=AD9A798-C=
57...
2A332CB7F959&displaylang=3Den) is a very useful tool, but
there is a problem when it is installed with the .net
Framework 1.1 with Service Pack 1. The copy of
WebUIValidation.js that is included with the Web Data
Administrator is out of date and means that it hangs when
you click the 'login' button. If you copy the updated
WebUIValidation.js file from
WINDOWS\Microsoft.NET\Framewor=ADk\v1.1.4322
\ASP.NETClientFiles into {SQL Web Administrator
installation path}\Web\aspnet_client\system=AD_web\1_1_4322\
then the problem with hanging is instantly solved.
Message to Microsoft: Please could you update the SQL Web
Administrator package to fix this problem?
By the way, this is not my solution - I found it on
http://sqljunkies.com/Forums/S=ADhow...PostID=3D2084.
|||Oops, ID-10-T error (IDIOT error!)
the fix I posted above does work, I must have been copying it in the
wrong spot or the copy hadn't "kicked in" just yet.
But the fix truly does work!
--Pam

Microsoft SQL-DMO(ODBC SQLState:42000)

I am getting the following error message in SQL 2K when I try to give
database access to a login Id "LogInId1".
****************************************
*************
Microsoft SQL-DMO(ODBC SQLState:42000)
Error 15023: User or role 'LogInId1' already exists in the current database.
****************************************
************************************
*
The "public" role in the above "current database" has a user Id "LogInId1".
This is the one it is generating the above error message. I can not remove
the above user ID from that role (public).
What I did to generate the above error message?
I restored one user database on SQL 2K (running under windows 2003) from the
backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
database from which back was ran.
How to add database access permissions to the login Id ""LogInId1"?
Thank you,
SmithYou can try:
exec sp_changedbowner 'LogInId1'
"John Smith" wrote:

> I am getting the following error message in SQL 2K when I try to give
> database access to a login Id "LogInId1".
>
> ****************************************
*************
> Microsoft SQL-DMO(ODBC SQLState:42000)
> Error 15023: User or role 'LogInId1' already exists in the current databas
e.
> ****************************************
**********************************
**
> *
>
> The "public" role in the above "current database" has a user Id "LogInId1"
.
> This is the one it is generating the above error message. I can not remove
> the above user ID from that role (public).
>
> What I did to generate the above error message?
> I restored one user database on SQL 2K (running under windows 2003) from t
he
> backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
> database from which back was ran.
>
> How to add database access permissions to the login Id ""LogInId1"?
> Thank you,
> Smith
>
>
>|||Take a look at sp_resolve_logins in BOL, etc.
The internal (to the database) user tables have entries that are either not
in the Master SYSLOGINS table or have different pointers to that table. You
need to either repoint(resolve) or remove those logins.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Fahim" wrote:
[vbcol=seagreen]
> You can try:
> exec sp_changedbowner 'LogInId1'
>
> "John Smith" wrote:
>

Microsoft SQL-DMO(ODBC SQLState:42000)

I am getting the following error message in SQL 2K when I try to give
database access to a login Id "LogInId1".
*****************************************************
Microsoft SQL-DMO(ODBC SQLState:42000)
Error 15023: User or role 'LogInId1' already exists in the current database.
****************************************************************************
*
The "public" role in the above "current database" has a user Id "LogInId1".
This is the one it is generating the above error message. I can not remove
the above user ID from that role (public).
What I did to generate the above error message?
I restored one user database on SQL 2K (running under windows 2003) from the
backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
database from which back was ran.
How to add database access permissions to the login Id ""LogInId1"?
Thank you,
SmithYou can try:
exec sp_changedbowner 'LogInId1'
"John Smith" wrote:
> I am getting the following error message in SQL 2K when I try to give
> database access to a login Id "LogInId1".
>
> *****************************************************
> Microsoft SQL-DMO(ODBC SQLState:42000)
> Error 15023: User or role 'LogInId1' already exists in the current database.
> ****************************************************************************
> *
>
> The "public" role in the above "current database" has a user Id "LogInId1".
> This is the one it is generating the above error message. I can not remove
> the above user ID from that role (public).
>
> What I did to generate the above error message?
> I restored one user database on SQL 2K (running under windows 2003) from the
> backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
> database from which back was ran.
>
> How to add database access permissions to the login Id ""LogInId1"?
> Thank you,
> Smith
>
>
>|||Take a look at sp_resolve_logins in BOL, etc.
The internal (to the database) user tables have entries that are either not
in the Master SYSLOGINS table or have different pointers to that table. You
need to either repoint(resolve) or remove those logins.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Fahim" wrote:
> You can try:
> exec sp_changedbowner 'LogInId1'
>
> "John Smith" wrote:
> > I am getting the following error message in SQL 2K when I try to give
> > database access to a login Id "LogInId1".
> >
> >
> >
> > *****************************************************
> >
> > Microsoft SQL-DMO(ODBC SQLState:42000)
> >
> > Error 15023: User or role 'LogInId1' already exists in the current database.
> >
> > ****************************************************************************
> > *
> >
> >
> >
> > The "public" role in the above "current database" has a user Id "LogInId1".
> > This is the one it is generating the above error message. I can not remove
> > the above user ID from that role (public).
> >
> >
> >
> > What I did to generate the above error message?
> >
> > I restored one user database on SQL 2K (running under windows 2003) from the
> > backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
> > database from which back was ran.
> >
> >
> >
> > How to add database access permissions to the login Id ""LogInId1"?
> >
> > Thank you,
> >
> > Smith
> >
> >
> >
> >
> >

Microsoft SQL-DMO(ODBC SQLState:42000)

I am getting the following error message in SQL 2K when I try to give
database access to a login Id "LogInId1".
************************************************** ***
Microsoft SQL-DMO(ODBC SQLState:42000)
Error 15023: User or role 'LogInId1' already exists in the current database.
************************************************** **************************
*
The "public" role in the above "current database" has a user Id "LogInId1".
This is the one it is generating the above error message. I can not remove
the above user ID from that role (public).
What I did to generate the above error message?
I restored one user database on SQL 2K (running under windows 2003) from the
backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
database from which back was ran.
How to add database access permissions to the login Id ""LogInId1"?
Thank you,
Smith
You can try:
exec sp_changedbowner 'LogInId1'
"John Smith" wrote:

> I am getting the following error message in SQL 2K when I try to give
> database access to a login Id "LogInId1".
>
> ************************************************** ***
> Microsoft SQL-DMO(ODBC SQLState:42000)
> Error 15023: User or role 'LogInId1' already exists in the current database.
> ************************************************** **************************
> *
>
> The "public" role in the above "current database" has a user Id "LogInId1".
> This is the one it is generating the above error message. I can not remove
> the above user ID from that role (public).
>
> What I did to generate the above error message?
> I restored one user database on SQL 2K (running under windows 2003) from the
> backup of SQL2K running under Win2K. The user Id "LogInId1" existed in the
> database from which back was ran.
>
> How to add database access permissions to the login Id ""LogInId1"?
> Thank you,
> Smith
>
>
>
|||Take a look at sp_resolve_logins in BOL, etc.
The internal (to the database) user tables have entries that are either not
in the Master SYSLOGINS table or have different pointers to that table. You
need to either repoint(resolve) or remove those logins.
Joseph R.P. Maloney, CSP,CCP,CDP
"Fahim" wrote:
[vbcol=seagreen]
> You can try:
> exec sp_changedbowner 'LogInId1'
>
> "John Smith" wrote:

Microsoft SQL Server Login

I'm getting the following message trying to connect through ODBC:
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
I've been troubleshooting for about a month and haven't solve the problem.
Could anyone told me what to do in order to fix the problem?
Thanks in advance.Can you post the connection string you are using?
"Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> I'm getting the following message trying to connect through ODBC:
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> I've been troubleshooting for about a month and haven't solve the problem.
> Could anyone told me what to do in order to fix the problem?
> Thanks in advance.|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
Someone already suggest me to remove:
OPEN=ODBC
and it didn't connect.
Hope you can help me.
Thanks in advance
"Adam David Moss" wrote:
> Can you post the connection string you are using?
>
> "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
> news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> > I'm getting the following message trying to connect through ODBC:
> >
> > "Connection failed:
> > SQLState: '01S00'
> > SQL Server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > Connection failed:
> > SQLState: 'S1T00'
> > SQL server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >
> > I've been troubleshooting for about a month and haven't solve the problem.
> >
> > Could anyone told me what to do in order to fix the problem?
> >
> > Thanks in advance.
>
>|||Try removing the database=... Your DSN already specifies this does it not?
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:175EC6DB-10AF-41B0-9DB2-A9AC10D1DCF3@.microsoft.com...
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> Someone already suggest me to remove:
> OPEN=ODBC
> and it didn't connect.
> Hope you can help me.
> Thanks in advance
>
> "Adam David Moss" wrote:
> > Can you post the connection string you are using?
> >
> >
> > "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in
message
> > news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> > > I'm getting the following message trying to connect through ODBC:
> > >
> > > "Connection failed:
> > > SQLState: '01S00'
> > > SQL Server Error: 0
> > > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > > Connection failed:
> > > SQLState: 'S1T00'
> > > SQL server Error: 0
> > > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> > >
> > > I've been troubleshooting for about a month and haven't solve the
problem.
> > >
> > > Could anyone told me what to do in order to fix the problem?
> > >
> > > Thanks in advance.
> >
> >
> >|||Just out of curiosity:
If you test the connection using the ODBC admin applet does it successfully
connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||No, connection fail.
"Rand Boyd [MSFT]" wrote:
> Just out of curiosity:
> If you test the connection using the ODBC admin applet does it successfully
> connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Microsoft SQL Server Login

I'm getting the following message trying to connect through ODBC:
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribu
te
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
I've been troubleshooting for about a month and haven't solve the problem.
Could anyone told me what to do in order to fix the problem?
Thanks in advance.Can you post the connection string you are using?
"Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> I'm getting the following message trying to connect through ODBC:
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attri
bute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> I've been troubleshooting for about a month and haven't solve the problem.
> Could anyone told me what to do in order to fix the problem?
> Thanks in advance.|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
Someone already suggest me to remove:
OPEN=ODBC
and it didn't connect.
Hope you can help me.
Thanks in advance
"Adam David Moss" wrote:

> Can you post the connection string you are using?
>
> "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
> news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
>
>|||Try removing the database=... Your DSN already specifies this does it not?
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:175EC6DB-10AF-41B0-9DB2-A9AC10D1DCF3@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
> Someone already suggest me to remove:
> OPEN=ODBC
> and it didn't connect.
> Hope you can help me.
> Thanks in advance
>
> "Adam David Moss" wrote:
>
message[vbcol=seagreen]
problem.[vbcol=seagreen]|||Just out of curiosity:
If you test the connection using the ODBC admin applet does it successfully
connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||No, connection fail.
"Rand Boyd [MSFT]" wrote:

> Just out of curiosity:
> If you test the connection using the ODBC admin applet does it successfull
y
> connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Microsoft SQL Server Login

I'm getting the following message trying to connect through ODBC:
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
I've been troubleshooting for about a month and haven't solve the problem.
Could anyone told me what to do in order to fix the problem?
Thanks in advance.
Can you post the connection string you are using?
"Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> I'm getting the following message trying to connect through ODBC:
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> I've been troubleshooting for about a month and haven't solve the problem.
> Could anyone told me what to do in order to fix the problem?
> Thanks in advance.
|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
Someone already suggest me to remove:
OPEN=ODBC
and it didn't connect.
Hope you can help me.
Thanks in advance
"Adam David Moss" wrote:

> Can you post the connection string you are using?
>
> "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
> news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
>
>
|||Try removing the database=... Your DSN already specifies this does it not?
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:175EC6DB-10AF-41B0-9DB2-A9AC10D1DCF3@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> Someone already suggest me to remove:
> OPEN=ODBC
> and it didn't connect.
> Hope you can help me.
> Thanks in advance
>
> "Adam David Moss" wrote:
message[vbcol=seagreen]
problem.[vbcol=seagreen]
|||Just out of curiosity:
If you test the connection using the ODBC admin applet does it successfully
connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||No, connection fail.
"Rand Boyd [MSFT]" wrote:

> Just out of curiosity:
> If you test the connection using the ODBC admin applet does it successfully
> connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>