Moved database, need to set the login name for DBO.

Hello,
I have moved a database to a new server (DR scenario). I have sucessfully
recreated one of the SQL user accounts needed, but the other one (lets call
it ACCOUNT2) is more of a problem.
When I look at the users on the database in question, dbo should have a
login of ACCOUNT2. I can't figure out how to recreate this. ACCOUNT2
currently exists on the new server.
I have tried looking at SP_CHANGE_USERS_LOGIN but don't think it will do the
job.
Any ideas?
Cheers
Remember that you are an Englishman, and have consequently won first
prize in the lottery of life" -Cecil Rhodes
"For a century and a half now, America and Japan have formed one of the
great and enduring alliances of modern times."
George W Bush -Tokyo, Japan, Feb. 18, 2002
Happy shall he be, that taketh and dasheth thy little ones against the
stones. Psalms 137:9.
Behold, I will corrupt your seed, and spread dung upon your faces.
Malachi 2:3.
"He who rises up to kill us, we will pre-empt it and kill him first,"
- Ariel Sharon 8th May 2002See this kb.
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] <kevmc@.online.microsoft.com> wrote:
> See this kb.
> 314546 HOW TO: Move Databases Between Computers That Are Running SQL
> Server http://support.microsoft.com/?id=314546
Thanks very much.
Remember that you are an Englishman, and have consequently won first
prize in the lottery of life" -Cecil Rhodes
"For a century and a half now, America and Japan have formed one of the
great and enduring alliances of modern times."
George W Bush -Tokyo, Japan, Feb. 18, 2002
Happy shall he be, that taketh and dasheth thy little ones against the
stones. Psalms 137:9.
Behold, I will corrupt your seed, and spread dung upon your faces.
Malachi 2:3.
"He who rises up to kill us, we will pre-empt it and kill him first,"
- Ariel Sharon 8th May 2002

Move FTC from SS2K to SS2K5

Morning,

Here is my scenario:

I have a SQL Server 2000 server with 10 clients.

Each client has 5 Full-Text Catalogs. For ease of explanation let’s call the FTCs C1 thru C5.

Now each client’s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.

I need to move the clients to our new SQL Server 2005 Enterprise server.

I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.

So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.

Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?

If so, how do I overcome this event?

Thanks for any and all help!

JJKusch,

In SQL Server 2005, the format of full-text catalogs has changed significantly. This change requires all full-text catalogs from previous versions of SQL Server to be rebuilt.

Move FTC from SS2K to SS2K5

Morning,

Here is my scenario:

I have a SQL Server 2000 server with 10 clients.

Each client has 5 Full-Text Catalogs. For ease of explanation let’s call the FTCs C1 thru C5.

Now each client’s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.

I need to move the clients to our new SQL Server 2005 Enterprise server.

I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.

So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.

Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?

If so, how do I overcome this event?

Thanks for any and all help!

JJKusch,

In SQL Server 2005, the format of full-text catalogs has changed significantly. This change requires all full-text catalogs from previous versions of SQL Server to be rebuilt.