Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

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

Set Task Properties

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

/Anders

Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

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

Set Task Properties

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

/Anders

Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

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

Set Task Properties

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

/Anders

Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

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

Set Task Properties

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

/Anders

Mirror database and users

We are mirroring to a server used to generate reports and datamarts. Is
there a technique of synching up the database users with the principle
server?
We use snapshots to generate reports and datamarts off of.Best approach is to make sure the logins on that other SQL Server has the co
rrect SID in the first
place. Search KB for sp_help_revlogin and check it out. If that isn't an opt
ion for you, you need to
do something with sp_change_users_login, something you run after the failove
r has taken place...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:ekB9rBEeGHA.1320@.TK2MSFTNGP04.phx.gbl...
> We are mirroring to a server used to generate reports and datamarts. Is t
here a technique of
> synching up the database users with the principle server?
> We use snapshots to generate reports and datamarts off of.
>

Mirror database and users

We are mirroring to a server used to generate reports and datamarts. Is
there a technique of synching up the database users with the principle
server?
We use snapshots to generate reports and datamarts off of.Best approach is to make sure the logins on that other SQL Server has the correct SID in the first
place. Search KB for sp_help_revlogin and check it out. If that isn't an option for you, you need to
do something with sp_change_users_login, something you run after the failover has taken place...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:ekB9rBEeGHA.1320@.TK2MSFTNGP04.phx.gbl...
> We are mirroring to a server used to generate reports and datamarts. Is there a technique of
> synching up the database users with the principle server?
> We use snapshots to generate reports and datamarts off of.
>sql

Minimum permission to attach / detach databases

Hi group,
I've got a problem determining permissions for users. I got one group
of users which only should have the abilitiy to attach / detach any
database to the SQL Server.
I just thought the SQL server wide user role dbcreator seems to be
sufficient for them but if I try to attach a database on which this
group does not have any permission within (its a database from an
external vendor), attaching the database fails.
Any hints on this?
Thanks,
HeikoHeiko
Can you elaborate a little bit?
>but if I try to attach a database on which this
> group does not have any permission within (its a database from an
> external vendor), attaching the database fails.
>
"Heiko Schuler" <hschuler@.gmail.com> wrote in message
news:1192693343.587584.291710@.v29g2000prd.googlegroups.com...
> Hi group,
> I've got a problem determining permissions for users. I got one group
> of users which only should have the abilitiy to attach / detach any
> database to the SQL Server.
> I just thought the SQL server wide user role dbcreator seems to be
> sufficient for them but if I try to attach a database on which this
> group does not have any permission within (its a database from an
> external vendor), attaching the database fails.
>
> Any hints on this?
>
> Thanks,
>
> Heiko
>|||> Can you elaborate a little bit?
Sure - I got one user which has the database role "dbcreator". When I
now try to attach a database, I got an error. the strange thing is - I
got 2 different depending using the GUI or T-SQL.
When I use the GUI, after selecting the mdf file, I got the following
error:
"User 'guest' does not have permission to run DBCC checkprimeryfile.
OK, this error message itself is clear because only members of the
sysadmin or server admin role can run DBCC commands. But why does the
GUI wants to run DBCC checkprimeryfile?
When I try to attach the database via T-SQL with sp_attach_db in Query
Analyzer, I got the following error:
"Unable to open the physical fiel <path to the mdf>. Operating system
error 5 (error not found).
Depending on the message error message above I first thougt it was a
permisson error on the file system. But if I put the user in the
sysadmin server role - everything works fine. So NTFS permission on
the file system is OK.
Heiko

million rows user table and growing

For our web site, we now have a million users and we have one user table
right now..
We would like to consider scaling this out as we grow to 5 -10 million users
and not have it in one table.
Every time a user logs on or changes profile,etc, we dont want to cause
contention or blocking on this table.. so whats the best way to go about
this ?
If i partition the table, whats the best way to go about partitioning it ?
Thanks> Every time a user logs on or changes profile,etc, we dont want to cause
> contention or blocking on this table.. so whats the best way to go about
> this ?
As long as you have appropriate indexing, I wouldn't expect performance or
concurrency problems regardless of table size. A few million rows really
isn't that large nowadays and, in my option, doesn't warrant partitioning.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.test.com> wrote in message
news:%23ytph$8XIHA.4196@.TK2MSFTNGP04.phx.gbl...
> For our web site, we now have a million users and we have one user table
> right now..
> We would like to consider scaling this out as we grow to 5 -10 million
> users and not have it in one table.
> Every time a user logs on or changes profile,etc, we dont want to cause
> contention or blocking on this table.. so whats the best way to go about
> this ?
> If i partition the table, whats the best way to go about partitioning it ?
> Thanks|||Perhaps your company should consider hiring an experienced DBA' One that
can guide you proactively instead of reactively and successfully get you to
the level you wish to achieve.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Hassan" <hassan@.test.com> wrote in message
news:%23ytph$8XIHA.4196@.TK2MSFTNGP04.phx.gbl...
> For our web site, we now have a million users and we have one user table
> right now..
> We would like to consider scaling this out as we grow to 5 -10 million
> users and not have it in one table.
> Every time a user logs on or changes profile,etc, we dont want to cause
> contention or blocking on this table.. so whats the best way to go about
> this ?
> If i partition the table, whats the best way to go about partitioning it ?
> Thanks|||Focus on indexing strategy , statistics , as 1 million rows is not that
much.
--
Jack Vamvas
___________________________________
Search IT jobs from multiple sources- http://www.ITjobfeed.com
"Hassan" <hassan@.test.com> wrote in message
news:%23ytph$8XIHA.4196@.TK2MSFTNGP04.phx.gbl...
> For our web site, we now have a million users and we have one user table
> right now..
> We would like to consider scaling this out as we grow to 5 -10 million
> users and not have it in one table.
> Every time a user logs on or changes profile,etc, we dont want to cause
> contention or blocking on this table.. so whats the best way to go about
> this ?
> If i partition the table, whats the best way to go about partitioning it ?
> Thanks

Million Records Problem

Is there any way or approach on handling reports with million of records retrieved?

Had a problem for 25 silmultaneous users accessing the report.
Problems are:
- Timeout Expired.
- Server unavailable.
- Page cannot be displayed.

Please let me know if there is... Thanks in advance...

You should set the report to execute from a snapshot, otherwise each user access results in another 1M rows put into memory.

|||I am curious... why do your users want to see all million rows? Is it possible to reduce the amount of data coming into the report server by pushing filters down into the query expressions?

Migration to SQL 2005 ... how to setup the new enviroment

Hello,

I have been made the point person for our migration to SQL2005. We are a law firm with approximately 750 users. The first SQL environment we will be upgrading is our document management system (DMS). This is an intensive SQL product. After this migration we will more of to our finical system, records system and then all home grown databases.

What we would like to do is consolidate servers and scale out the new SQL environment to a farm. After some initial research it does not look like we will be able to scale out, since the data in the DMS is always changing.

Does anyone have some advice or guidance on what direction we should be looking? I have done tons a online searches and can find out information on everything to do with SQL, except this.

Thanks in advance,

Jeff Carroll

See this link and watch webcast #4...

http://www.microsoft.com/events/series/technetsqlserver2005.mspx

Migrating to a new database server

I need to migrate the DTS, the jobs, users and everything from a
database on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to
another (Windows Server 2003, SQL 2000). The databases that do not
already exist on the new server I can restore those from a backup just fine.
The ones that exist (master, model, msdb) I can't copy over from a
restore. It tells me that exclusive access could not be obtained
because the database is in use.
Is there an easy/straightforward way to get everything - especially DTS
and the batch jobs - from my old server to the new one?
Any advice appreciated.
BCSee this post from yesterday: "Moving a DB from 1 Server 2 another".
HTH
Jerry
"Blasting Cap" <goober@.christian.net> wrote in message
news:Ogobt0qeGHA.2456@.TK2MSFTNGP04.phx.gbl...

>I need to migrate the DTS, the jobs, users and everything from a database
>on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to another
>(Windows Server 2003, SQL 2000). The databases that do not already exist
>on the new server I can restore those from a backup just fine.
> The ones that exist (master, model, msdb) I can't copy over from a
> restore. It tells me that exclusive access could not be obtained because
> the database is in use.
> Is there an easy/straightforward way to get everything - especially DTS
> and the batch jobs - from my old server to the new one?
> Any advice appreciated.
> BC
>

Migrating to a new database server

I need to migrate the DTS, the jobs, users and everything from a
database on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to
another (Windows Server 2003, SQL 2000). The databases that do not
already exist on the new server I can restore those from a backup just fine.
The ones that exist (master, model, msdb) I can't copy over from a
restore. It tells me that exclusive access could not be obtained
because the database is in use.
Is there an easy/straightforward way to get everything - especially DTS
and the batch jobs - from my old server to the new one?
Any advice appreciated.
BCSee this post from yesterday: "Moving a DB from 1 Server 2 another".
HTH
Jerry
"Blasting Cap" <goober@.christian.net> wrote in message
news:Ogobt0qeGHA.2456@.TK2MSFTNGP04.phx.gbl...
>I need to migrate the DTS, the jobs, users and everything from a database
>on a Windows 2000 server (SQL 2000, upgraded from SQL 7), to another
>(Windows Server 2003, SQL 2000). The databases that do not already exist
>on the new server I can restore those from a backup just fine.
> The ones that exist (master, model, msdb) I can't copy over from a
> restore. It tells me that exclusive access could not be obtained because
> the database is in use.
> Is there an easy/straightforward way to get everything - especially DTS
> and the batch jobs - from my old server to the new one?
> Any advice appreciated.
> BC
>

Migrating to 64 bit.

I just finished installing MSSQL 2000 to an Itanium cluster and all went
well, but when I tried to use DTS to transfer the users, it says you can't
use 32-bit DTS to transfer to 64-bit. Does anyone have a good trick to
transfer user accounts since I have several and don't know all the
passwords. I can move the databases, jobs, etc...
Nevermind, I just found this...
http://support.microsoft.com/kb/246133/
"Shawn" <shawn.camner@.ccci.org> wrote in message
news:OhRpg3Q3GHA.324@.TK2MSFTNGP05.phx.gbl...
>I just finished installing MSSQL 2000 to an Itanium cluster and all went
>well, but when I tried to use DTS to transfer the users, it says you can't
>use 32-bit DTS to transfer to 64-bit. Does anyone have a good trick to
>transfer user accounts since I have several and don't know all the
>passwords. I can move the databases, jobs, etc...
>

Migrating to 64 bit.

I just finished installing MSSQL 2000 to an Itanium cluster and all went
well, but when I tried to use DTS to transfer the users, it says you can't
use 32-bit DTS to transfer to 64-bit. Does anyone have a good trick to
transfer user accounts since I have several and don't know all the
passwords. I can move the databases, jobs, etc...Nevermind, I just found this...
http://support.microsoft.com/kb/246133/
"Shawn" <shawn.camner@.ccci.org> wrote in message
news:OhRpg3Q3GHA.324@.TK2MSFTNGP05.phx.gbl...
>I just finished installing MSSQL 2000 to an Itanium cluster and all went
>well, but when I tried to use DTS to transfer the users, it says you can't
>use 32-bit DTS to transfer to 64-bit. Does anyone have a good trick to
>transfer user accounts since I have several and don't know all the
>passwords. I can move the databases, jobs, etc...
>

Migrating to 64 bit.

I just finished installing MSSQL 2000 to an Itanium cluster and all went
well, but when I tried to use DTS to transfer the users, it says you can't
use 32-bit DTS to transfer to 64-bit. Does anyone have a good trick to
transfer user accounts since I have several and don't know all the
passwords. I can move the databases, jobs, etc...Nevermind, I just found this...
http://support.microsoft.com/kb/246133/
"Shawn" <shawn.camner@.ccci.org> wrote in message
news:OhRpg3Q3GHA.324@.TK2MSFTNGP05.phx.gbl...
>I just finished installing MSSQL 2000 to an Itanium cluster and all went
>well, but when I tried to use DTS to transfer the users, it says you can't
>use 32-bit DTS to transfer to 64-bit. Does anyone have a good trick to
>transfer user accounts since I have several and don't know all the
>passwords. I can move the databases, jobs, etc...
>