Replace hardware with other architecture (IA64 -> X64)

#91

First, thanks for your wellwritten replys.

I agree, it would be perfect to have both the new and the old one up
at the same time. In this case I talked to the application vendor and
they have problems see this be done at all. They more or less said
that "we don't support it if you change VS name".

About my earlier question, can you point me to a Microsoft
article/document that said it's not supported to move systemdatabases
(between architecture)? I can't find it!

I

On Wed, 14 May 2008 09:34:27 -0400, "Geoff N. Hiten"
<SQLCraftsman (AT) gmail (DOT) com> wrotc:

Quote:

OK. I see what you are doing. That process will work.

Most folks try and run BOTH virtual servers at the same time to do the data
synch. That won't work for reasons you have undoubtably discovered.

Again, I usually simplify the process using DNS records to point the old
name to the new server. This is especially easy if the name is already
abstracted via DNS to begin with. This has the advantage of allowing me to
have both servers up and running. I can keep my cutover downtime to 15-30
minutes this way with the right setup.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Replace hardware with other architecture (IA64 -> X64)

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Replace hardware with other architecture (IA64 -> X64) - 05-14-2008 , 09:33 AM