Hello,
We have a vendor supplied application that only supports SQL 2000 (for at least another 6 months.) Our team also wants to use SQL 2005 for some of the native XML benefits with custom code.
Several of our team wants to install both versions of SQL (2k, 2005) on the same server even in our production environment. I am wary of supporting this for a high availability application, and am concerned that the next service pack or hotfix could cause problems.
1) Though I have read it is supported, are any Fortune 100 type companies using this configuration for high availability applications?
2) Does SQL's fundamental capability to support multiple instances make this more trivial than I am thinking?
3) Would anyone have points that would support the conservative approach against this without just sounding paranoid?
Thank You,
Mike
You can do that but you need to implement high availability on the server level using approaces like clustering, etc. We are doing that in our environment, of course, using clustering for high availability (MSCS, Veritas Cluster, etc.)
No comments:
Post a Comment