That's exactly what I needed to know. Yes, I'm assuming
that they're trying to do something that's possible.
Risk mitigation would be simplified if they were trying to do something
impossible.
Question:
I have some folks considering upgrading SQL in place from SQL2005 x32
Workgroup to SQL2008 x64 Standard on the same server. Does anyone have
any thoughts and experience here as to the impact on an existing MOSS
farm on the server?
I think I've heard for other situations that it's best practice to do a
fresh install on a new server for database upgrades, does that apply
here as well?
Responce:
Unless he's running 32 bit SQL 2005 on a 64 bit OS already, he can't
upgrade. You can't upgrade the underlying OS from 32 bit to 64 bit.
SQL is damned good at upgrading itself and its databases. When I've done
it in the past I've just detached the databases from SQL and upgraded
the OS and SQL, then reattached the databases. I've gone 2000 to 2005,
2005 to 2005 (single to cluster) and 2005 to 2008. It's all good.
For the most part, all MOSS cares about is the SQL instance name, and
the database name. If that doesn't change then MOSS doesn't care what
you do. If the instance will change, then look into SQL Aliases to
minimize that pain.