SQL2K SP4 backwards with SQL2K SP3 (Instcat.sql)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

news.microsoft.com - 30 Aug 2005 16:11 GMT

Hi,
I am evaluating upgrading to SP4 on one of our main SQL2K SP3 servers.
The SP4 upgrade will only be to this single SQL2K SP3 server, but we have 2
other production SQL2K SP3 servers that it will need to talk to (linked
servers)

In trying to understand the readme, I am looking at the section titled,
"Update the Catalog of Linked Servers". I have never had an instance of
SQL2K versions being "out of sync" on our production servers, and finding
some clarification on this issue is hard to come by.

Is it completely safe to run Instcat.sql on my SQL2K SP3 servers so that
the linked server situation will work between SP4 and SP3? Will the
existing links between the SP3 boxes continue to work? (all 3 servers link
to one another for cross-server queries, etc.)

I am only hesitant because running the script "updates the system
catalogs" on the linked servers, is it safe?

Thank you in advance for time and advice,
Aaron

Reply to this Message

Sophie Guo [MSFT] - 31 Aug 2005 07:46 GMT

Hello,

I suggest that you setup three test machines to test it before applying
SQL SP4 to the production server. Make sure you have backed up all the
databases before installing.

Based on my knowledge, you need to run Instcat.sql on all SQL servers,
including the Server that is being upgraded since this is not run during
SP4 setup. I hope the information is helpful.

Sophie Guo
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message