Is there a way to transfer logins with sids AND passwords from 2000
server to 2005 server? There is a way when coming from SQL 7 to 2000,
but the system tables have changed slightly now, and that way doesn't
work any longer. The "Transfer logins" task in SSIS includes the
following disclaimer....
When the Transfer Logins task is executed, logins are created on the
destination server with random passwords and the passwords are
disabled. To use these logins, a member of the sysadmin fixed server
role must change the passwords and then enable them. The sa login
cannot be transferred.
This sucks - I don't want to go to each login & reset their password.
I want it to be more seamless. Does anyone know of a workaround?Hi,
You can use sp_help_revlogin stored procedure
(http://support.microsoft.com/default.aspx?kbid=246133) on SQL 2000 instance
and execute the output on SQL 2005.
This will create the login with the password however other settings will not
be transfered. (Default DB, Language ...)
"Corey Bunch" wrote:
> Is there a way to transfer logins with sids AND passwords from 2000
> server to 2005 server? There is a way when coming from SQL 7 to 2000,
> but the system tables have changed slightly now, and that way doesn't
> work any longer. The "Transfer logins" task in SSIS includes the
> following disclaimer....
> When the Transfer Logins task is executed, logins are created on the
> destination server with random passwords and the passwords are
> disabled. To use these logins, a member of the sysadmin fixed server
> role must change the passwords and then enable them. The sa login
> cannot be transferred.
> This sucks - I don't want to go to each login & reset their password.
> I want it to be more seamless. Does anyone know of a workaround?
>|||One of my counterparts tried this & told me b/c of the system table
changes, this wouldn't work. I'll check back with him. The link that
you refer to only specifies between 7.0 & 2000. It doesn't say
anything about 2005.
Umut Nazlica wrote:
> Hi,
> You can use sp_help_revlogin stored procedure
> (http://support.microsoft.com/default.aspx?kbid=246133) on SQL 2000 instance
> and execute the output on SQL 2005.
> This will create the login with the password however other settings will not
> be transfered. (Default DB, Language ...)
>
> "Corey Bunch" wrote:
> > Is there a way to transfer logins with sids AND passwords from 2000
> > server to 2005 server? There is a way when coming from SQL 7 to 2000,
> > but the system tables have changed slightly now, and that way doesn't
> > work any longer. The "Transfer logins" task in SSIS includes the
> > following disclaimer....
> >
> > When the Transfer Logins task is executed, logins are created on the
> > destination server with random passwords and the passwords are
> > disabled. To use these logins, a member of the sysadmin fixed server
> > role must change the passwords and then enable them. The sa login
> > cannot be transferred.
> >
> > This sucks - I don't want to go to each login & reset their password.
> > I want it to be more seamless. Does anyone know of a workaround?
> >
> >|||Hi,
We upgrade our SQL 2005 CTP installations several times with this method and
worked fine.(15 to 16 16 to RC1, RC1 to RC2)
AFAIK during installation it also upgrades the system tables if necessary.
Article is for SQL 2000/7.0 yes, but you mention in your message you want to
move logins from SQL 2000 to SQL 2005, and i suggest that run
sp_help_revlogin on SQL 2000 it will create the create login statements for
you with passwords, and you can run that output on SQL 2005 with no problem.
You can easily test it..
If you want to move logins from SQL 2005 to SQL 2005 it won't work but you
are asking for SQL 2000 to SQL 2005.
"Corey Bunch" wrote:
> One of my counterparts tried this & told me b/c of the system table
> changes, this wouldn't work. I'll check back with him. The link that
> you refer to only specifies between 7.0 & 2000. It doesn't say
> anything about 2005.
>
> Umut Nazlica wrote:
> > Hi,
> >
> > You can use sp_help_revlogin stored procedure
> > (http://support.microsoft.com/default.aspx?kbid=246133) on SQL 2000 instance
> > and execute the output on SQL 2005.
> >
> > This will create the login with the password however other settings will not
> > be transfered. (Default DB, Language ...)
> >
> >
> > "Corey Bunch" wrote:
> >
> > > Is there a way to transfer logins with sids AND passwords from 2000
> > > server to 2005 server? There is a way when coming from SQL 7 to 2000,
> > > but the system tables have changed slightly now, and that way doesn't
> > > work any longer. The "Transfer logins" task in SSIS includes the
> > > following disclaimer....
> > >
> > > When the Transfer Logins task is executed, logins are created on the
> > > destination server with random passwords and the passwords are
> > > disabled. To use these logins, a member of the sysadmin fixed server
> > > role must change the passwords and then enable them. The sa login
> > > cannot be transferred.
> > >
> > > This sucks - I don't want to go to each login & reset their password.
> > > I want it to be more seamless. Does anyone know of a workaround?
> > >
> > >
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment