I have a concern with a clustered SQL server pair which had a failed node recently replaced with a new server. I am understanding that when I replaced the node, the install of SQL from the original node copied over all binaries, including SP3 files to the new node. But, with the original node as
active,the SQL version shows as 8.00.760 with [SP3]. With
the new node active, the version shows 8.00.194 with [RTM].

SQL seems to be operating fine, however we are receiving
lots of timeout messages at various places in the app.
Because of these messages, I investigated the version and
found the discrepancy mentioned above. Any advice??

TIA,
Ken

I've since read that, and it states what you're telling me. Unfortunately, it directly contradicts what I've seen posted here

Thanks

The install copies RTM binaries from the CD or other install source, not
updated binaries from a working node. You can apply service packs to local
binaries only do handle a situation like yours. See the README file on the
SP for exact instructions.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

[quoted text, click to view]
recently replaced with a new server. I am understanding that when I replaced
the node, the install of SQL from the original node copied over all
binaries, including SP3 files to the new node. But, with the original node
as
[quoted text, click to view]

This is a public newsgroup. Sometimes the answers you get may not be
perfect. Anyone with MS or MVP in the name usually knows what they are
doing or at least gets corrected quickly.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

[quoted text, click to view]