Collation error

hi,

Our SQL servers have been setup to collate American. However, our pc's are setup for South Africa. This is creating a nightmare for us as we use Great Plains, which is an American product with American date format.

We are having difficulties in doing any development due to this issue.

Can someone please advise me as to whether there is another way around this ?

ThanksI hear you with this problem as i have experienced the exact same thing.

The only way that i know to cope with it is to use the collate keyword which 'casts' the tables to a common collation so the join makes sense.

Collations specify the way values are compared (eg Case sensitive, sort order), so be careful when choosing the one to cast to.
UPDATE tblPrepTemplate
SET Reason = 'Do not contact'
FROM tblPrepTemplate A
inner join [Do Not Contact].DoNotContact.dbo.TblDoNotContacts B
ON a.TeleW = b.ContactNumber
collate Latin1_General_CS_AS
WHERE Reason Is Null

It is possible to change the collation of a table as well, for example


CREATE TABLE MyTable (PrimaryKey int PRIMARY KEY, CharCol varchar(10) COLLATE French_CI_AS NOT NULL )
GO

ALTER TABLE MyTable ALTER COLUMN CharCol varchar(10)COLLATE Latin1_General_CI_AS NOT NULL


I don't think that Collations do not affect the date format

Collation Conflict with Snapshot Rep

I'm trying to setup replication from an external web server to internal sql
box. The internal box with do a pull subscription to external webbox. I ran
snapshot and all works successfully. As soon as I try to run Pull
subscription, I get an error a Collation Conflict on a table. I tweaked the
settings and copy the collation to destination in the publication properties
tab. This runs but gives me the following:
Error Message: Cannot resolve collation conflict for equal to operation.
Error Detail: Cannot resolve collation conflict for equal to operation.
(Source: WIN2K3 (Data source); Error number: 446)
ANy ideas on how to correct this?
Thanks in Advance
Rob
Is there anything odd about the particular table you are having a problem
with? Could you post its schema here? What sort of content is inside this
table?
Also it sounds like you are doing filtering. Are you?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:18B8B552-CC29-4F84-B073-34FF3FF6BBED@.microsoft.com...
> I'm trying to setup replication from an external web server to internal
> sql
> box. The internal box with do a pull subscription to external webbox. I
> ran
> snapshot and all works successfully. As soon as I try to run Pull
> subscription, I get an error a Collation Conflict on a table. I tweaked
> the
> settings and copy the collation to destination in the publication
> properties
> tab. This runs but gives me the following:
> Error Message: Cannot resolve collation conflict for equal to operation.
> Error Detail: Cannot resolve collation conflict for equal to operation.
> (Source: WIN2K3 (Data source); Error number: 446)
> ANy ideas on how to correct this?
> Thanks in Advance
> Rob
>
|||No filtering, straight snapshot. Nothing odd about the table or its data.
Its a third
party program so I cannot change the table structure.
Heres the table setup.
CREATE TABLE [TABLE1] (
[nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
[no_next_internal_id] [int] NOT NULL ,
[no_next_parameter_id] [int] NULL ,
[no_next_code_suffix] [int] NULL ,
CONSTRAINT [Table1_PK] PRIMARY KEY CLUSTERED
(
[nm_entity]
) WITH FILLFACTOR = 90 ON [PRIMARY]
) ON [PRIMARY]
When SQL creates snapshot this is the table structure on the
pull subscriber:
CREATE TABLE [THINQ_ID_MANAGER] (
[nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
[no_next_internal_id] [int] NOT NULL ,
[no_next_parameter_id] [int] NULL ,
[no_next_code_suffix] [int] NULL
) ON [PRIMARY]
GO
thanks
rob
"Hilary Cotter" wrote:

> Is there anything odd about the particular table you are having a problem
> with? Could you post its schema here? What sort of content is inside this
> table?
> Also it sounds like you are doing filtering. Are you?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Rob" <Rob@.discussions.microsoft.com> wrote in message
> news:18B8B552-CC29-4F84-B073-34FF3FF6BBED@.microsoft.com...
>
>
|||What is the default collation sequence on your publisher and the default
collation sequence on your subscriber?
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:4B47392D-0477-4842-9173-762D00AE5267@.microsoft.com...[vbcol=seagreen]
> No filtering, straight snapshot. Nothing odd about the table or its
> data.
> Its a third
> party program so I cannot change the table structure.
> Heres the table setup.
> CREATE TABLE [TABLE1] (
> [nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
> [no_next_internal_id] [int] NOT NULL ,
> [no_next_parameter_id] [int] NULL ,
> [no_next_code_suffix] [int] NULL ,
> CONSTRAINT [Table1_PK] PRIMARY KEY CLUSTERED
> (
> [nm_entity]
> ) WITH FILLFACTOR = 90 ON [PRIMARY]
> ) ON [PRIMARY]
> When SQL creates snapshot this is the table structure on the
> pull subscriber:
> CREATE TABLE [THINQ_ID_MANAGER] (
> [nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
> [no_next_internal_id] [int] NOT NULL ,
> [no_next_parameter_id] [int] NULL ,
> [no_next_code_suffix] [int] NULL
> ) ON [PRIMARY]
> GO
> thanks
> rob
>
>
> "Hilary Cotter" wrote:

Clustering with W2K3 and SQL 2005 (64bit) - best practice setup

Hi
I'm a little confused how best to setup a new 2005 deployment. I'm
moving from a 2000 environment, which used Legato's AAM software to
support failover. The new environment will use MS clustering.
The 2000 setup has multiple instances on each node, and each instance
can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
instance has to have it's own 'virtual server'. So, in this setup,
named instances seem a bit redundant, since you can name the virtual
server. EG Why use Server1\Inst1, Server2\Inst2, when
Server1\<default>, Server2\<default> is just as informative
So, my questions are: 1) is it good practice to use named instances in
a clustered setup;
and 2) what is the rationale behind restricting a virtual server to a
single instance
Thanks.
You only get one default instance per cluster, not per virtual server.
Personally, I only use named instances to avoid name style confusion.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"steve" <stevester@.freeuk.com> wrote in message
news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
> Hi
> I'm a little confused how best to setup a new 2005 deployment. I'm
> moving from a 2000 environment, which used Legato's AAM software to
> support failover. The new environment will use MS clustering.
> The 2000 setup has multiple instances on each node, and each instance
> can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
> instance has to have it's own 'virtual server'. So, in this setup,
> named instances seem a bit redundant, since you can name the virtual
> server. EG Why use Server1\Inst1, Server2\Inst2, when
> Server1\<default>, Server2\<default> is just as informative
> So, my questions are: 1) is it good practice to use named instances in
> a clustered setup;
> and 2) what is the rationale behind restricting a virtual server to a
> single instance
> Thanks.
|||On 3 Dec, 14:23, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> You only get one default instance per cluster, not per virtual server.
> Personally, I only use named instances to avoid name style confusion.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
> "steve" <steves...@.freeuk.com> wrote in message
> news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
>
>
>
>
> - Show quoted text -
Thanks Geoff. So I can't use deafult instances with each additional
virtual server.
I'm still puzzled why you can only have one instance per virtual
server tho. - seems overly restrictive.
|||It has to do with how SQL organizes binaries for different instances. Or
mor accurately, how multiple instances were handled in SQL 2000.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"steve" <stevester@.freeuk.com> wrote in message
news:1a8e02f1-ca6b-44b3-84ee-b0589802b2c8@.j20g2000hsi.googlegroups.com...
> On 3 Dec, 14:23, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Thanks Geoff. So I can't use deafult instances with each additional
> virtual server.
> I'm still puzzled why you can only have one instance per virtual
> server tho. - seems overly restrictive.
|||"steve" <stevester@.freeuk.com> wrote in message
news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...

> The 2000 setup has multiple instances on each node, and each instance
> can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
> instance has to have it's own 'virtual server'. So, in this setup,
> named instances seem a bit redundant, since you can name the virtual
> server. EG Why use Server1\Inst1, Server2\Inst2, when
> Server1\<default>, Server2\<default> is just as informative
Each virtual server must be an instance. You can only have one default
instance per cluster and the rest have to be named instances.

> So, my questions are: 1) is it good practice to use named instances in
> a clustered setup;
You should only used named instances in a cluster. There are some known
issues around patching that can cause problems, for example, if you service
pack a named instance before the default.

> and 2) what is the rationale behind restricting a virtual server to a
> single instance
Each instance requires its own resources, thus, each requires its own
virtual server.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Dec 10 - 13 in Denver
Jan 18 - 31 in Denver
|||Thanks for your answers - very helpful.
Steve

Clustering with 2 active nodes and 1 passive node

Normally, clustering is setup as a 1-to-1 relationship between active and
passive nodes, at least that is my understanding. We have a situation where
we are being asked to setup a 2 active node, 1 passive node environment.
Here's the question - if one of the active nodes fails, it fails over to the
passive node. Now what happens if the 2nd active node fails? Will the other
active node (originally the passive node) handle the failover or will it try
to failover to the first active node that failed or will the whole thing just
grind to a screeching halt? I know we can setup a 2 active/ 2passive node
setup, but we wanted to research the 2-to-1 possibility as well.
Thanks!
Message posted via http://www.droptable.com
Hi
You don't need a 1:1 relationship between nodes.
And forget the terms active / passive, it is totally out of date and does
not describe SQL Server 2000/2005 clustering.
You have an instance of SQL Server running on an node.
If you have 2 nodes, it could run on any of those nodes at any one time. If
you had 3 nodes, it could run on any of those nodes, at any one time.
If you have 2 nodes, one sits around waiting for a failover. If you have 3
nodes, 2 sit around waiting for a failover.
If you have more than one SQL Server instance running on the cluster, then
the instances can run on any of the nodes.
The instances could be all running on the same node, or dispersed over the
various nodes.
Quite often, people run with 3 nodes and 2 instances or 4 nodes with 3
instances. There is nothing stopping you running 3 instances on 3 nodes, 4
instances on 4 nodes, or any combination of up to 16 instances over 4 nodes.
You just need to make sure that you have enough resources, that in worst
case, one node could run all instances.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Michael G via droptable.com" <forum@.droptable.com> wrote in message
news:541CE6C54F90F@.droptable.com...
> Normally, clustering is setup as a 1-to-1 relationship between active and
> passive nodes, at least that is my understanding. We have a situation
> where
> we are being asked to setup a 2 active node, 1 passive node environment.
> Here's the question - if one of the active nodes fails, it fails over to
> the
> passive node. Now what happens if the 2nd active node fails? Will the
> other
> active node (originally the passive node) handle the failover or will it
> try
> to failover to the first active node that failed or will the whole thing
> just
> grind to a screeching halt? I know we can setup a 2 active/ 2passive node
> setup, but we wanted to research the 2-to-1 possibility as well.
> Thanks!
>
> --
> Message posted via http://www.droptable.com
|||Very helpful. Question: So now, even with RAID 10, the single point of
failure becomes the shared drive array? How does one go about creating a
failover for this?
Respectfully,
Michael Wiederhold
michael@.auctionarms.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%230j6BCZtFHA.3236@.TK2MSFTNGP14.phx.gbl...
> Hi
> You don't need a 1:1 relationship between nodes.
> And forget the terms active / passive, it is totally out of date and does
> not describe SQL Server 2000/2005 clustering.
> You have an instance of SQL Server running on an node.
> If you have 2 nodes, it could run on any of those nodes at any one time.
> If you had 3 nodes, it could run on any of those nodes, at any one time.
> If you have 2 nodes, one sits around waiting for a failover. If you have 3
> nodes, 2 sit around waiting for a failover.
> If you have more than one SQL Server instance running on the cluster, then
> the instances can run on any of the nodes.
> The instances could be all running on the same node, or dispersed over the
> various nodes.
> Quite often, people run with 3 nodes and 2 instances or 4 nodes with 3
> instances. There is nothing stopping you running 3 instances on 3 nodes, 4
> instances on 4 nodes, or any combination of up to 16 instances over 4
> nodes. You just need to make sure that you have enough resources, that in
> worst case, one node could run all instances.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Michael G via droptable.com" <forum@.droptable.com> wrote in message
> news:541CE6C54F90F@.droptable.com...
>
|||Hi
Most high end SAN's have a block level copy mechanism so that you can
"mirror" that data to another SAN, preferably at another location.
EMC has SRDF that can run synchronous or asynchronous over fast WAN links.
Tape backups must never be forgotten either.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"michael wiederhold" <michael@.auctionarms.com> wrote in message
news:%23RhSzuztFHA.3068@.TK2MSFTNGP14.phx.gbl...
> Very helpful. Question: So now, even with RAID 10, the single point of
> failure becomes the shared drive array? How does one go about creating a
> failover for this?
> Respectfully,
> Michael Wiederhold
> michael@.auctionarms.com
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%230j6BCZtFHA.3236@.TK2MSFTNGP14.phx.gbl...
>
|||Thanks. Really do appreciate your participation in this newsgroup.
Respectfully,
Michael Wiederhold
michael@.auctionarms.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ONHGyz8tFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi
> Most high end SAN's have a block level copy mechanism so that you can
> "mirror" that data to another SAN, preferably at another location.
> EMC has SRDF that can run synchronous or asynchronous over fast WAN links.
> Tape backups must never be forgotten either.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "michael wiederhold" <michael@.auctionarms.com> wrote in message
> news:%23RhSzuztFHA.3068@.TK2MSFTNGP14.phx.gbl...
>

Clustering under Windows 98SE/XP

Is there a way to setup a cluster on a network running Windows 98SE and
Windows XP? We've succeeded at doing things like distributing our files
among other computers in the network and mapping their drives for use with
built in search functions but now we want to tap processor power of the
other computes for running applications on any networked machine. We've seen
this done using Linux but we are loyal Windows fans and do not want to make
the move unless we have no other choice.
VMWare or Virtual Server 2005 will allow you to build a test cluster!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Tom" <trendor@.yahoo.com> wrote in message
news:44120704$0$3755$39cecf19@.news.twtelecom.net.. .
> Is there a way to setup a cluster on a network running Windows 98SE and
> Windows XP? We've succeeded at doing things like distributing our files
> among other computers in the network and mapping their drives for use with
> built in search functions but now we want to tap processor power of the
> other computes for running applications on any networked machine. We've
> seen this done using Linux but we are loyal Windows fans and do not want
> to make the move unless we have no other choice.
>

Clustering SQL Servers in a Workgroup

I have setup a couple of SQL Server 2 node clusters in the past and was
always in a domain environment. I now have to setup a 2 node cluster in a
none domain workgroup environment if anyone has any tips I would appreciate
the advice.
Thanks,
Andrew
It's not supported. You need a domain.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"chabotwvu" <chabotwvu@.discussions.microsoft.com> wrote in message
news:C64FA1A9-86BC-4438-9A66-809EF466883B@.microsoft.com...
I have setup a couple of SQL Server 2 node clusters in the past and was
always in a domain environment. I now have to setup a 2 node cluster in a
none domain workgroup environment if anyone has any tips I would appreciate
the advice.
Thanks,
Andrew

Clustering or log shipping MS SQL 2000?

Our current SAP production environment consists of a window 2000 advanced
server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
server which contains an exact copy of the production database which is
up-to-date all the time during the day.
I started looking into log shipping but it appears there will be some down
time when the transaction logs are shipped from one sql server to the second
sql server. If the second sql server takes 10 minutes to apply the
transaction logs then the database is unavailable for that time period. Are
there any other options? What are other Basis admins doing? Are they using
Microsoft Clustering services to replicate the database? Or using SAN
imaging technology to replicate the data to another server?
Please advise,
Clustering won't get you there...its a high-availability solution, not
distributed processing.
The requirement of near-time data pretty much says you are looking at
transactional replication, or a 3rd party utility.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Chris,
There are several SAN Solutions that accomplish exactly what you want. This
is probably the way to go, although expensive.
-- Bill
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||replication is ideal for this. Some SAN solutions allow you to do this sort
of a thing but they tend to be very expensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Would Transactional Replication that is built into SQL 2000 work for this?
Or is this log shipping?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
> replication is ideal for this. Some SAN solutions allow you to do this
> sort of a thing but they tend to be very expensive.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Chris T." <tatroc@.donotspam.gmail.com> wrote in message
> news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
>
|||Transactional repl.
Log shipping is not going to give you the up to date you are looking for AND
the ability to use it as a reporting server. Either one, not both
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:OH%23EOy0MHHA.1252@.TK2MSFTNGP02.phx.gbl...
> Would Transactional Replication that is built into SQL 2000 work for this?
> Or is this log shipping?
>
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
>

Clustering concepts...

We have just setup two servers running a copy of SQL 2000 on Windows 2000
server. Each of these servers is running vendor software that interrracts
with the databases. One server is primary and one is backup. Clients only
interract with the vendor process on the servers and not the SQL directly.
Some general questions on SQL 2000 high availability options...
Does Active/Passive and Active/Active refer to clustering options that
require that the servers be clustered on the OS level? Is this the only
option that keeps the databases syncronized in real time?
Is replication a good method if the failover will be done manually?
Thanks!
Karl Albrecht
Active/Active and Active/Passive are obsolete concepts from SQL 7.0 when
each SQL instance had a primary owner host node and a partner owner node.
Under SQL 2000, all nodes are interchangable in a cluster. Some people
mistakenly use teh terms to refer to single and multiple instance SQL
clustering.
Clustering involves a single data store on a 'shared' storage system (SCSI
Array, SAN, etc. NOT NAS). Shared is not exactly correct since the cluster
software arbitrates ownership so that only one host node owns the
resource(s) at a time. Therefore, you have to have a working MSCS cluster
in order to create a SQL cluster.
Replication is not a good technique for creating a warm standby server.
Replication has VERY limited ability to handle schema changes without a
total resynch. It also does not replicate stored procedures or views.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Karl Albrecht" <karlman@.pacbell.net> wrote in message
news:O8QGJUplEHA.2340@.TK2MSFTNGP11.phx.gbl...
> We have just setup two servers running a copy of SQL 2000 on Windows 2000
> server. Each of these servers is running vendor software that interrracts
> with the databases. One server is primary and one is backup. Clients only
> interract with the vendor process on the servers and not the SQL directly.
>
> Some general questions on SQL 2000 high availability options...
> Does Active/Passive and Active/Active refer to clustering options that
> require that the servers be clustered on the OS level? Is this the only
> option that keeps the databases syncronized in real time?
> Is replication a good method if the failover will be done manually?
>
> Thanks!
> Karl Albrecht
>
|||Geoff, you can replicate stored procs and views.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:u%23O18vplEHA.3712@.TK2MSFTNGP15.phx.gbl...
Active/Active and Active/Passive are obsolete concepts from SQL 7.0 when
each SQL instance had a primary owner host node and a partner owner node.
Under SQL 2000, all nodes are interchangable in a cluster. Some people
mistakenly use teh terms to refer to single and multiple instance SQL
clustering.
Clustering involves a single data store on a 'shared' storage system (SCSI
Array, SAN, etc. NOT NAS). Shared is not exactly correct since the cluster
software arbitrates ownership so that only one host node owns the
resource(s) at a time. Therefore, you have to have a working MSCS cluster
in order to create a SQL cluster.
Replication is not a good technique for creating a warm standby server.
Replication has VERY limited ability to handle schema changes without a
total resynch. It also does not replicate stored procedures or views.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Karl Albrecht" <karlman@.pacbell.net> wrote in message
news:O8QGJUplEHA.2340@.TK2MSFTNGP11.phx.gbl...
> We have just setup two servers running a copy of SQL 2000 on Windows 2000
> server. Each of these servers is running vendor software that interrracts
> with the databases. One server is primary and one is backup. Clients only
> interract with the vendor process on the servers and not the SQL directly.
>
> Some general questions on SQL 2000 high availability options...
> Does Active/Passive and Active/Active refer to clustering options that
> require that the servers be clustered on the OS level? Is this the only
> option that keeps the databases syncronized in real time?
> Is replication a good method if the failover will be done manually?
>
> Thanks!
> Karl Albrecht
>
|||> Clustering involves a single data store on a 'shared' storage system (SCSI
> Array, SAN, etc. NOT NAS).
Actually, you can cluster to a shared resource on a NAS. We have a NetApp
880 Filer and have been running SQL clusters quite nicely using Snapdrive
over Gig fiber for a couple of years using the procedures outlined at this
NetApp link:
http://www.netapp.com/tech_library/3248.html#2.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:u%23O18vplEHA.3712@.TK2MSFTNGP15.phx.gbl...
> Active/Active and Active/Passive are obsolete concepts from SQL 7.0 when
> each SQL instance had a primary owner host node and a partner owner node.
> Under SQL 2000, all nodes are interchangable in a cluster. Some people
> mistakenly use teh terms to refer to single and multiple instance SQL
> clustering.
> Clustering involves a single data store on a 'shared' storage system (SCSI
> Array, SAN, etc. NOT NAS). Shared is not exactly correct since the
> cluster
> software arbitrates ownership so that only one host node owns the
> resource(s) at a time. Therefore, you have to have a working MSCS cluster
> in order to create a SQL cluster.
> Replication is not a good technique for creating a warm standby server.
> Replication has VERY limited ability to handle schema changes without a
> total resynch. It also does not replicate stored procedures or views.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Karl Albrecht" <karlman@.pacbell.net> wrote in message
> news:O8QGJUplEHA.2340@.TK2MSFTNGP11.phx.gbl...
>

clustering

HI,
I am new to sql server clustering.
can we setup sql clustering with out using windows cluster setup.
Thanks in advance
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200705/1
Hi
"pardh via droptable.com" wrote:

> HI,
> I am new to sql server clustering.
> can we setup sql clustering with out using windows cluster setup.
> Thanks in advance
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200705/1
>
A SQL Server Cluster requires Microsoft Clustering Services. With SQL 2005
you can use database mirroring to attain high availablilty without the need
for a cluster. You can also use log shipping on SQL 2000/2005 as a way to
provide resilience.
John
|||Consider www.clusterhelp.com.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"pardh via droptable.com" <u8956@.uwe> wrote in message
news:71825e9196fad@.uwe...
HI,
I am new to sql server clustering.
can we setup sql clustering with out using windows cluster setup.
Thanks in advance
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200705/1

Clustering

Hi All
Is it possible to setup up a cluster between a 32-bit version of SQL Server
2005 and a 64-bit version of SQL Server 2005?
Thanks
- David
Hi David
"David" wrote:

> Hi All
> Is it possible to setup up a cluster between a 32-bit version of SQL Server
> 2005 and a 64-bit version of SQL Server 2005?
> Thanks
> - David
Although I have not tried this, I think it should be possible. In general it
is better to keep the environment homogenous as falling over to a server that
can not cope could be worse than having no service at all.
John
|||While it may be possible, I doubt it would be supported. And in the very
unlikely event it's supported, I'd strongly discourage you from actually
doing so.
Any particular reason you may want to setup a cluster in such a way?
Linchi
"David" wrote:

> Hi All
> Is it possible to setup up a cluster between a 32-bit version of SQL Server
> 2005 and a 64-bit version of SQL Server 2005?
> Thanks
> - David

Clustering

Hi All
Is it possible to setup up a cluster between a 32-bit version of SQL Server
2005 and a 64-bit version of SQL Server 2005?
Thanks
- DavidHi David
"David" wrote:
> Hi All
> Is it possible to setup up a cluster between a 32-bit version of SQL Server
> 2005 and a 64-bit version of SQL Server 2005?
> Thanks
> - David
Although I have not tried this, I think it should be possible. In general it
is better to keep the environment homogenous as falling over to a server that
can not cope could be worse than having no service at all.
John|||While it may be possible, I doubt it would be supported. And in the very
unlikely event it's supported, I'd strongly discourage you from actually
doing so.
Any particular reason you may want to setup a cluster in such a way?
Linchi
"David" wrote:
> Hi All
> Is it possible to setup up a cluster between a 32-bit version of SQL Server
> 2005 and a 64-bit version of SQL Server 2005?
> Thanks
> - David

clustering

HI,
I am new to sql server clustering.
can we setup sql clustering with out using windows cluster setup.
Thanks in advance
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200705/1Hi
"pardh via SQLMonster.com" wrote:
> HI,
> I am new to sql server clustering.
> can we setup sql clustering with out using windows cluster setup.
> Thanks in advance
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200705/1
>
A SQL Server Cluster requires Microsoft Clustering Services. With SQL 2005
you can use database mirroring to attain high availablilty without the need
for a cluster. You can also use log shipping on SQL 2000/2005 as a way to
provide resilience.
John|||Consider www.clusterhelp.com.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"pardh via SQLMonster.com" <u8956@.uwe> wrote in message
news:71825e9196fad@.uwe...
HI,
I am new to sql server clustering.
can we setup sql clustering with out using windows cluster setup.
Thanks in advance
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200705/1

clustering

HI,
I am new to sql server clustering.
can we setup sql clustering with out using windows cluster setup.
Thanks in advance
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200705/1Hi
"pardh via droptable.com" wrote:

> HI,
> I am new to sql server clustering.
> can we setup sql clustering with out using windows cluster setup.
> Thanks in advance
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200705/1
>
A SQL Server Cluster requires Microsoft Clustering Services. With SQL 2005
you can use database mirroring to attain high availablilty without the need
for a cluster. You can also use log shipping on SQL 2000/2005 as a way to
provide resilience.
John|||Consider www.clusterhelp.com.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"pardh via droptable.com" <u8956@.uwe> wrote in message
news:71825e9196fad@.uwe...
HI,
I am new to sql server clustering.
can we setup sql clustering with out using windows cluster setup.
Thanks in advance
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200705/1

Clustering

Hi All
Is it possible to setup up a cluster between a 32-bit version of SQL Server
2005 and a 64-bit version of SQL Server 2005?
Thanks
- DavidHi David
"David" wrote:

> Hi All
> Is it possible to setup up a cluster between a 32-bit version of SQL Serve
r
> 2005 and a 64-bit version of SQL Server 2005?
> Thanks
> - David
Although I have not tried this, I think it should be possible. In general it
is better to keep the environment homogenous as falling over to a server tha
t
can not cope could be worse than having no service at all.
John|||While it may be possible, I doubt it would be supported. And in the very
unlikely event it's supported, I'd strongly discourage you from actually
doing so.
Any particular reason you may want to setup a cluster in such a way?
Linchi
"David" wrote:

> Hi All
> Is it possible to setup up a cluster between a 32-bit version of SQL Serve
r
> 2005 and a 64-bit version of SQL Server 2005?
> Thanks
> - David

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
'
Thanks for any enlightening.
Regards,audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.12
9.250.171.67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>
>

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
?
Thanks for any enlightening.
Regards,
audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> ?
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)
|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegr oups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> ?
> Thanks for any enlightening.
> Regards,
>
|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegr oups.com...
>
|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.129.250.171. 67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>

Cluster/SQL 2005/1 node install

We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
Thanks and God Bless,
ThomBeaux
The service account did not have the:
(local policy) - Act as part of the OS
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:

> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux

Cluster/SQL 2005/1 node install

We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
--
Thanks and God Bless,
ThomBeauxThe service account did not have the:
(local policy) - Act as part of the OS
--
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux