Hi people.
I would like to know if anybody knows if there's any
problem use SQL Server 2000 with SP2 and SQL 2000 Client
with SP3a.
Tks in advance.It seems to work OK without any issues. Do you find any problems?
--
- Anith
( Please reply to newsgroups only )|||Tks for your help.
>--Original Message--
>I have installations with Server on SP2 & client machines
with SP3a and I
>haven't found any issues either with setup or
connectivity. Before
>installing it, make sure you read through the readme.htm
that comes with
>SP3a for any additional information.
>--
>- Anith
>( Please reply to newsgroups only )
>
>.
>|||No... I didn't install it yet. But is it recommended?
>--Original Message--
>It seems to work OK without any issues. Do you find any
problems?
>--
>- Anith
>( Please reply to newsgroups only )
>
>.
>|||The only problem you may have would be related to DTS packages. If a client
machine (with SP3) creates or modifies a DTS package and saves it back to
the server with SP2 on it, it is conceivable that the package will no
longer run or may not be able to be modified by a users using the SP2
version of the SQL Server clients.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have installations with Server on SP2 & client machines with SP3a and I
haven't found any issues either with setup or connectivity. Before
installing it, make sure you read through the readme.htm that comes with
SP3a for any additional information.
--
- Anith
( Please reply to newsgroups only )|||Tks Rand!!!
>--Original Message--
>The only problem you may have would be related to DTS
packages. If a client
>machine (with SP3) creates or modifies a DTS package and
saves it back to
>the server with SP2 on it, it is conceivable that the
package will no
>longer run or may not be able to be modified by a users
using the SP2
>version of the SQL Server clients.
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>
Showing posts with label sps. Show all posts
Showing posts with label sps. Show all posts
Friday, March 9, 2012
Wednesday, March 7, 2012
Different sp:s on cluster nodes
Hi all!
I'm in the starting phase on planning a cluster enviorment. I'm really a newbie at clustering. I have one question that I will be very glad if you could help me with.
I thinking of configuring a 2 node, single instance cluster. The reason for the cluster if of course high availability. To achive the high availability demands we need to make sure that we can do maintenance on our servers without taking them down. The mo
st specific case is that we want to upgrade SQL Server servicepacks and hotfixes while users still can access the databases(useing the other node).
Is this how it works? Upgrade the passive node, switch passive node to active, upgrade the passive node? How does the cluster handle the fact that after the passive node has been upgraded with let's say SP3A and put in active mode, it will "connect" to
the database files that are on a different servicepack level?
Hope you understand what I'm thinking and that you have some info for me.
Thanks!!
/Fredrik
Unfortunately, it doesn't work that way. SQL requires single-user access
during the SP or Hotfix to update system objects within the database. It is
possible to do a 'binary-only' application of a SP or Hotfix, but that is
only when a node is repaired or replaced. SQL must already have the SP or
Hotfix applied to the current host node. For now, you will have to schedule
downtime to apply a SP or a hotfix. I suspect this may be addressed in the
next version since many people have complained about the downtime
requirement.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Fredrik" <anonymous@.discussions.microsoft.com> wrote in message
news:0C99300E-22B6-4B0B-9B00-2FC4241DE899@.microsoft.com...
> Hi all!
> I'm in the starting phase on planning a cluster enviorment. I'm really a
newbie at clustering. I have one question that I will be very glad if you
could help me with.
> I thinking of configuring a 2 node, single instance cluster. The reason
for the cluster if of course high availability. To achive the high
availability demands we need to make sure that we can do maintenance on our
servers without taking them down. The most specific case is that we want to
upgrade SQL Server servicepacks and hotfixes while users still can access
the databases(useing the other node).
> Is this how it works? Upgrade the passive node, switch passive node to
active, upgrade the passive node? How does the cluster handle the fact that
after the passive node has been upgraded with let's say SP3A and put in
active mode, it will "connect" to the database files that are on a different
servicepack level?
> Hope you understand what I'm thinking and that you have some info for me.
> Thanks!!
> /Fredrik
I'm in the starting phase on planning a cluster enviorment. I'm really a newbie at clustering. I have one question that I will be very glad if you could help me with.
I thinking of configuring a 2 node, single instance cluster. The reason for the cluster if of course high availability. To achive the high availability demands we need to make sure that we can do maintenance on our servers without taking them down. The mo
st specific case is that we want to upgrade SQL Server servicepacks and hotfixes while users still can access the databases(useing the other node).
Is this how it works? Upgrade the passive node, switch passive node to active, upgrade the passive node? How does the cluster handle the fact that after the passive node has been upgraded with let's say SP3A and put in active mode, it will "connect" to
the database files that are on a different servicepack level?
Hope you understand what I'm thinking and that you have some info for me.
Thanks!!
/Fredrik
Unfortunately, it doesn't work that way. SQL requires single-user access
during the SP or Hotfix to update system objects within the database. It is
possible to do a 'binary-only' application of a SP or Hotfix, but that is
only when a node is repaired or replaced. SQL must already have the SP or
Hotfix applied to the current host node. For now, you will have to schedule
downtime to apply a SP or a hotfix. I suspect this may be addressed in the
next version since many people have complained about the downtime
requirement.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Fredrik" <anonymous@.discussions.microsoft.com> wrote in message
news:0C99300E-22B6-4B0B-9B00-2FC4241DE899@.microsoft.com...
> Hi all!
> I'm in the starting phase on planning a cluster enviorment. I'm really a
newbie at clustering. I have one question that I will be very glad if you
could help me with.
> I thinking of configuring a 2 node, single instance cluster. The reason
for the cluster if of course high availability. To achive the high
availability demands we need to make sure that we can do maintenance on our
servers without taking them down. The most specific case is that we want to
upgrade SQL Server servicepacks and hotfixes while users still can access
the databases(useing the other node).
> Is this how it works? Upgrade the passive node, switch passive node to
active, upgrade the passive node? How does the cluster handle the fact that
after the passive node has been upgraded with let's say SP3A and put in
active mode, it will "connect" to the database files that are on a different
servicepack level?
> Hope you understand what I'm thinking and that you have some info for me.
> Thanks!!
> /Fredrik
Saturday, February 25, 2012
Different result in SP vs Query Analyzer
I'm getting some very odd behaviour which I can currently
duplicate. One of my SPs fails when it can't find a
record. I copy the SQL from the SP and execute it via
query analyzer and ta-da, the record appears.
Further investigation shows that the sql checks that a
record doesn't have a "completed" status. Comment this
out and the SP works fine.
Continuing the investigation, the developers run this SP
through debug and find the value being returned
= 'COMPLETED'. Run the *same* code in query analyzer and
the value being returned is 'PLANNED'... How is this
possible' The sql returns the correct value when run
through query analyzer, but the incorrect value when run
as a part of the SP!!
Below is the 'where' clause:
.
.
.
Where
(vtt.Trip_Id = @.FCTripId)
And (eqm.eqm_sequence_no = 2)
And (cst.cst_consign_status_desc <> 'COMPLETED')
TIA,
SJT> I'm getting some very odd behaviour which I can currently
> duplicate.
Can you give us enough information so we can try to duplicate? Table
schema, sample data, the code for the procedure maybe, desired results. See
http://www.aspfaq.com/5006
> Further investigation shows that the sql checks that a
> record doesn't have a "completed" status.
What datatype is this? How does sql "check"? What is the exact syntax you
are using? What data is actually stored in the column?
> Continuing the investigation, the developers run this SP
> through debug and find the value being returned
> = 'COMPLETED'. Run the *same* code in query analyzer and
> the value being returned is 'PLANNED'... How is this
> possible'
You're looking at a different row? The stored procedure is being executed
against the test database, and query analyzer is connected to production?
> And (cst.cst_consign_status_desc <> 'COMPLETED')
I'm going to guess that (shudder) "cst_consign_status_desc" is a CHAR
column. You should use VARCHAR so that trailing spaces are ignored, and
ensure that ANSI_PADDING is set the same in both environments to ensure that
you get consistent results.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
duplicate. One of my SPs fails when it can't find a
record. I copy the SQL from the SP and execute it via
query analyzer and ta-da, the record appears.
Further investigation shows that the sql checks that a
record doesn't have a "completed" status. Comment this
out and the SP works fine.
Continuing the investigation, the developers run this SP
through debug and find the value being returned
= 'COMPLETED'. Run the *same* code in query analyzer and
the value being returned is 'PLANNED'... How is this
possible' The sql returns the correct value when run
through query analyzer, but the incorrect value when run
as a part of the SP!!
Below is the 'where' clause:
.
.
.
Where
(vtt.Trip_Id = @.FCTripId)
And (eqm.eqm_sequence_no = 2)
And (cst.cst_consign_status_desc <> 'COMPLETED')
TIA,
SJT> I'm getting some very odd behaviour which I can currently
> duplicate.
Can you give us enough information so we can try to duplicate? Table
schema, sample data, the code for the procedure maybe, desired results. See
http://www.aspfaq.com/5006
> Further investigation shows that the sql checks that a
> record doesn't have a "completed" status.
What datatype is this? How does sql "check"? What is the exact syntax you
are using? What data is actually stored in the column?
> Continuing the investigation, the developers run this SP
> through debug and find the value being returned
> = 'COMPLETED'. Run the *same* code in query analyzer and
> the value being returned is 'PLANNED'... How is this
> possible'
You're looking at a different row? The stored procedure is being executed
against the test database, and query analyzer is connected to production?
> And (cst.cst_consign_status_desc <> 'COMPLETED')
I'm going to guess that (shudder) "cst_consign_status_desc" is a CHAR
column. You should use VARCHAR so that trailing spaces are ignored, and
ensure that ANSI_PADDING is set the same in both environments to ensure that
you get consistent results.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
Subscribe to:
Posts (Atom)