Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


windows cluster quorum setting on windows server 2012


windows cluster quorum setting on windows server 2012

Author
Message
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8777 Visits: 16547
muthyala_51 (2/14/2014)
I am facing the following issues while setting up alwayson.

1) Not able to set the listener to the alwayson group. Error--

The WSFC cluster could not bring the Network Name resource with DNS name 'MyAGListener' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. (Microsoft SQL Server, Error: 19471)

This is pretty descriptive, the virtual networkname and \or IP address supplied for the listener are not unique. Supply a unique name and IP


muthyala_51 (2/14/2014)
2) Also we are planning to have 3 replicas with one server acts as principal and the other two replicas one synchronous and other asynchronous setup. We kind of planning to achieve both HA + DR by using alwayson feature. But we cannot replicate system databases. Is there any way to achive this?

No, this requires a failover cluster instance.


muthyala_51 (2/14/2014)
3) to setup transactional replication can we use listener virtual name or it asks for physical name? If it accepts physical server name we can't go with servername as it causes issues when failover happens.

Never set it up myself.
Section 2 of this link details

MSDN-SQL Server
Create a DNS listener for the availability group that will be used by the replication agents to connect to the current primary. The listener name that is specified will be used as the target of redirection for the original publisher/published database pair. For example, if you are using DDL to configure the availability group, the following code example can be used to specify an availability group listener for an existing availability group named MyAG:


ALTER AVAILABILITY GROUP 'MyAG'
ADD LISTENER 'MyAGListenerName' (WITH IP (('10.120.19.155', '255.255.254.0')));





muthyala_51 (2/14/2014)
4) Also I have a table with identity column on in a database which is in alwayson group. For some reason the values jumped from 1,2,3,2002,2003? What could be the reason behind this?

The only possible explanation is that the seed value changed, can't see how though

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
muth_51
muth_51
Mr or Mrs. 500
Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)

Group: General Forum Members
Points: 532 Visits: 2860
About the identity column, I just truncated the table on pricipal and inserted few rows and failed over to the other server. When i started inserting the rows again the value jumped into 1000s. Everytime i failover to the other it's incrementing to 1000's.

fid   fname
6   pears
7   pears
1002   pears---failed over
1003   pears
1010   pears
2002   pears--failed over
2003   pears
2004   pears
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8777 Visits: 16547
yep that's what i'm seeing, jumps by 1000 each failover

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Sreekanth B
Sreekanth B
SSC-Addicted
SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)

Group: General Forum Members
Points: 417 Visits: 1945
Perry Whittle (2/20/2014)
muthyala_51 (2/14/2014)
I am facing the following issues while setting up alwayson.

1) Not able to set the listener to the alwayson group. Error--

The WSFC cluster could not bring the Network Name resource with DNS name 'MyAGListener' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. (Microsoft SQL Server, Error: 19471)

This is pretty descriptive, the virtual networkname and \or IP address supplied for the listener are not unique. Supply a unique name and IP


muthyala_51 (2/14/2014)
2) Also we are planning to have 3 replicas with one server acts as principal and the other two replicas one synchronous and other asynchronous setup. We kind of planning to achieve both HA + DR by using alwayson feature. But we cannot replicate system databases. Is there any way to achive this?

No, this requires a failover cluster instance.


muthyala_51 (2/14/2014)
3) to setup transactional replication can we use listener virtual name or it asks for physical name? If it accepts physical server name we can't go with servername as it causes issues when failover happens.

Never set it up myself.
Section 2 of this link details

MSDN-SQL Server
Create a DNS listener for the availability group that will be used by the replication agents to connect to the current primary. The listener name that is specified will be used as the target of redirection for the original publisher/published database pair. For example, if you are using DDL to configure the availability group, the following code example can be used to specify an availability group listener for an existing availability group named MyAG:


ALTER AVAILABILITY GROUP 'MyAG'
ADD LISTENER 'MyAGListenerName' (WITH IP (('10.120.19.155', '255.255.254.0')));





muthyala_51 (2/14/2014)
4) Also I have a table with identity column on in a database which is in alwayson group. For some reason the values jumped from 1,2,3,2002,2003? What could be the reason behind this?

The only possible explanation is that the seed value changed, can't see how though


Unfortunately This(restarting SQL Server(or Failover of AG) forces reseed of Identity) behavior is by design as per microsoft...Crazy
see below connect items for more information.
http://connect.microsoft.com/SQLServer/feedback/details/743300/identity-column-jumps-by-seed-value
https://connect.microsoft.com/SQLServer/feedback/details/739013/alwayson-failover-results-in-reseed-of-identity
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8777 Visits: 16547
after checking there is a trace flag

-T272



This will revert to the behaviour in previous versions of the product

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
muth_51
muth_51
Mr or Mrs. 500
Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)

Group: General Forum Members
Points: 532 Visits: 2860
Perry Whittle (2/21/2014)
after checking there is a trace flag

-T272



This will revert to the behaviour in previous versions of the product


I did check on that one. But what would be the affect on server behaviour if this trace runs continuously. Our environment is OLTP we can't run trace all day 24X7.
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8777 Visits: 16547
It forces identities in sql server to behave as it did in previous versions. The trace flag is added to the service startup list to persist it on service restarts.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
muth_51
muth_51
Mr or Mrs. 500
Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)

Group: General Forum Members
Points: 532 Visits: 2860
Perry Whittle (2/23/2014)
It forces identities in sql server to behave as it did in previous versions. The trace flag is added to the service startup list to persist it on service restarts.


So you mean no affect on the server performance ??
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8777 Visits: 16547
why would it affect performance, it basically tells sql server not to use the new style of identity maintenance and act like a sql 2008 instance in that respect

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
muth_51
muth_51
Mr or Mrs. 500
Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)Mr or Mrs. 500 (532 reputation)

Group: General Forum Members
Points: 532 Visits: 2860
Perry,

Just to let you know...

If you require the same identity generation semantics as previous versions of SQL Server there are two options available:
• Use trace flag 272
o This will cause a log record to be generated for each generated identity value. The performance of identity generation may be impacted by turning on this trace flag.
• Use a sequence generator with the NO CACHE setting(http://msdn.microsoft.com/en-us/library/ff878091.aspx)
o This will cause a log record to be generated for each generated sequence value. Note that the performance of sequence value generation may be impacted by using NO CACHE.
o Example:

CREATE SEQUENCE s1 AS INT START WITH 1 NO CACHE;
CREATE TABLE t1 (Id INT PRIMARY KEY DEFAULT NEXT VALUE FOR s1, col INT NOT NULL);
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search