April 23, 2010 at 5:50 am
Hi guys,
From more than three years I used the standard Microsoft script to move logins from sql2000 to sql2005 using sp_help_revlogin_2000_to_2005 within http://support.microsoft.com/kb/246133/en-us.
Even a few months ago it ran, but tow weeks ago, I'm discovering it is failing or I'm forgetting something.
In fact I run the creation script for the sp, then exec it, copy to the target server, the result script and run it.
Login is created good, but, the password is not the same.
Please someone has faced similar issues
Francisco Racionero
twitter: @fracionero
April 23, 2010 at 6:45 am
maybe this?
During a transfer of logins between instances of SQL Server, if the sort order of the source server is case-insensitive and the sort order of the destination server is case-sensitive, you must enter all alphabetical characters in passwords as uppercase characters after the transfer of logins to the destination server. If the sort order of the source server is case-sensitive and the sort order of the destination server is case-insensitive, you will not be able to log in with the logins transferred using the procedure outlined in this article, unless the original password contains no alphabetical characters or unless all alphabetical characters in the original password are uppercase characters. If both servers are case-sensitive or both servers are case-insensitive, you will not experience this problem. This is a side effect of the way that SQL Server handles passwords. For more information, see the "Effect on Passwords of Changing Sort Orders" topic in SQL Server 7.0 Books Online.
April 23, 2010 at 12:33 pm
It's not the case same instances have same collation, thanks
Francisco Racionero
twitter: @fracionero
April 23, 2010 at 3:13 pm
What does the following query produce on each server? Can you post the results?
select serverproperty('Collation')
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 24, 2010 at 1:32 am
Hi guys,
Please, this setting is already checked from me the server collation Latin1_General_CI_AS.
I think I didn't explain good.
Using the Microsoft standard script to move login between SQL 2000 and SQL 2005, in the step deploying logins in SQL 2005, the script doesn't remains the original password.
Anyone faced this issue?
Francisco Racionero
twitter: @fracionero
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply