Aw, come on SQLBill, that makes too much sense!

Have you attempted running the SP4 upgrade on the named instance that's giving you an issue with that named instance on the physical node that's reporting SP3? In other words,...

Do the following:

EXEC sp_helpdb master

Where are the master and mastlog files located? Are they on one of the drives attached to the cluster group?

There was a software project I was working on that still burns me up to this day. We were asked if in house we could build an e-commerce type catalog...

How are you checking the SP version? Via SELECT @@VERSION? If so, for the instance giving you problems, where is the master database actually located?

So you basically want one contact per company, right?

• 1. Uninstall SQL Server
• 2. Install SQL Server to the version that it was when the backup was taken
• 3. Restore the backup
• 4. Apply the service pack

The reason you must do it...

Then you would need to revoke all permissions from the public role. To do so would leave your SQL Server in an unsupported state as per Microsoft. And there are...

If you have to support SQL Server 7, yes. You install it first because SQL Server 7 does not support named instances. Then you can install SQL Server 2000 as...

The /3GB switch refers to the virtual memory space. SQL Server will use up to 3 GB, the OS will load in the upper 1 GB of virtual memory space,...

If you're using over 4 GB of RAM for SQL Server (that would have to be specifically configured). You mentioned Windows Server 2003 Enterprise Edition. SQL Server 2000 Enterprise Edition...

The user should be able to do so. As the owner of the table the user can certain grant himself/herself the permissions to this.

Microsoft support then looks to be your best option.

The sqlstp.log file is the log file for the installation. It tells you what the installation program is attempting, what completed successfully and what failed. Therefore, don't delete it. Copy...

Found this... never tried it myself but since you're running short of options...

http://geekswithblogs.net/travis/archive/2005/07/27/48400.aspx

BTW, you'll need to get SQL Server back to the build it was at...