Patching SQL in a Clustered Environment

We are running a SQL within an Active Active Windows
Cluster setup. Will I run into any issues when attempting
to patch SQL with SQL SP3? Are there any issues I should
be aware of when patching the SQL cluster or any
prerequisite patches that need to be applied before
patching SQL in a cluster?
This is a rather open ended question. Are you talking about a specific
patch or just patches in general
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I am speaking of a general Serivce Pack 3a update. When dealing with virtual servers, are there any issues when applying the SP3a update?
rp
-- Rand Boyd [MSFT] wrote: --
This is a rather open ended question. Are you talking about a specific
patch or just patches in general
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Not really anything special. Make sure all nodes are online and are capable
of hosting the service. You will need to run the service pack from the node
hosting the particular instance you wish to update. If you have more than
one instance, you will need to apply the Service Pack to each instance
independantly. It is possible to run different instances at different
service pack and hotfix levels without a problem. Of course all instances
on a particular host will run against the same level MDAC installation. If
you run into any issues, you know where to find help.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Bob" <anonymous@.discussions.microsoft.com> wrote in message
news:02068577-4EB9-472E-A36E-D21EF109FC91@.microsoft.com...
> I am speaking of a general Serivce Pack 3a update. When dealing with
virtual servers, are there any issues when applying the SP3a update?
> rp
> -- Rand Boyd [MSFT] wrote: --
> This is a rather open ended question. Are you talking about a
specific
> patch or just patches in general
> Rand
> This posting is provided "as is" with no warranties and confers no
rights.
>
|||Before applying any service pack, always review the readme. For sp3a on a
cluster, see:
811168 INF: SQL Server 2000 Service Pack 3 or Service Pack 3a
Pre-Installation
http://support.microsoft.com/?id=811168
And you should strongly consider applying the MS03-031 security rollup as
well.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Cindy. I didn't know you had joined Microsoft.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Passing second column of table as index

We are working on C++ in eVC++ 3.0 environment (CE 3.0) with SQL CE 2.0.

We are trying with IRowsetIndex:: Seek method to access the data from the database.

We are facing problem when we try to access data from the table having composite index other than the first column.

For example:
The table ITEM contains the following columns:
1. ItemCode
2. PcNo
3. SubPcNo
4. BrandNo
5. DescText

6. ProductionKind

7. ProductionState

8. ClearingState

9. ST

10. TS

I’ve two indexes for this table where the two indexes are

1. ItemKey1 on ITEM (ItemCode).

2. ItemKey2 on ITEM (PcNo, SubPcNo, BrandNo).

If I mention ItemKey1 as the index then the Seek method works perfectly.

But if I mention ItemKey2 as the index, then I’m getting the error as “DB_E_BADBINDINFO”.

When we visted the MSDN for this problem we noted that:

1. When you use the Seek method on multiple fields, the Seek fields must be in the same order as the fields in the underlying table. If they are not, the Seek method fails.

2. When passing key values to an index rowset, the consumer performs these actions only for the number of key columns specified in the cKeyValues argument in IRowsetIndex:: Seek.

So we had the composite index such that columns of a composite index are physically aligned next to each other as in the table.

When the first column of the index is the first column of the table as in index ItemKey1 we found that the seek method works perfectly.

If we pass the index ItemKey2, we are again getting the error “DB_E_BADBINDINFO”.

What else have we missed out while passing the keys in IRowsetIndex:: Seek?

Thanks in advance.

Regards,

Sasi.

I saw this error when tried to use the table accessor for seeking. When you use IRowsetIndex you must create a separate accessor for the index columns and use that accessor for the Seek method, not the table's own accessor.

|||

Thanks for your reply Joao Paulo Figueira.

I was not able to understand the solution you provided, could you kinldy explain in detail.

Thanks & Regards,

Sasi.

|||

You must create a second memory buffer where to store the values to seek. This is built the same way as the memory buffer for accessing table data, but it must have the index columns and in the same order. You should use code similar to the one for binding the table columns in order to create the index accessor.

The only situation when you can share the same accessor between the table and the index is when the first N columns of the index are the same as the first N columns of the table. In all other situations you must create a different accessor for entering the data to seek.

|||

Thanks a lot Sir.

Its working now.

Thanks & Regards,

Sasi.