SQL Server 2012 Always On ?

Hi all,
If the PB application uses a Sql Server 2012 database well configured for high availability ("Always On"), is there something to deal with in PowerBuilder or is it totally transparent on client side ?
In previous version there were a FailOverPartner database parameter to fill but it seems useless with Sql Server 12 am I right ?
Is there something about it in the Pb 12.6 documentation (we use 12.5.2) ?
Or is it just not supported in 12.5.2 ?
Thanks in advance

Things depend upon what your expectations are when using the failover features of SQL Server2012. You will not be able to have the somewhat seamless failover as you did using the FailOverPartner parameter (which is unfortunate) if you utilize failover clustering. You will need to detect the original connection fail and then reconnect the transaction object.
If you set up 2012 with a failover partner as in 2008R2 things should work the same (but we are talking about Microsoft however...)
Matt

Similar Messages

Good device to put Instance root directory on a SQL Server 2012 Always On Failover Cluster ?

Hello, I'm currently testing SQL Server 2012 AlwaysOn Failover Cluster.
I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
The reason why I'm not sure is because, when I wanted to upgrade from SP1 to SP2, I wanted to do it first on the passive node, but it failed for most of the components it had to upgrade. So I first upgraded the active node then failover and upgraded the
newly active node.
I installed SQL Server this way because our system admins don't like us to install in on C:\ for their own reasons (maybe backup, or something ...)
I'm pretty sure there is something wrong. What's your point ?
Thanks in advance.

>I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
Nope.
SQL Server 2012 and earlier don't support data files on CSV volumes (SQL 2014 does).
And for any version of SQL Server the SQL Server instance directory should not be on a clustered disk. The Installation is local to each node, so should be on a non-clustered disk. It may be supported to put the instances in different locations
on the same clustered disk, but I wouldn't recommend it.
Installing the SQL Binaries on C:\ is fine. If you have another local volume you can also install them there.
David
David http://blogs.msdn.com/b/dbrowne/

Can you minimize logging in a SSIS data flow when the database is in a SQL Server 2012 Always On Group?

We have a file that we are loading 1st into a staging database then into a production database that contains over 5 million rows. Both databases belong to a SQL Server 2012 AG. We would like to minimize the logging in the staging database but t
the same time keep the staging database in the AG. I know about fast load and setting the buffer settings in SSIS but I've read that this doesn't work on replicated tables and I am assuming that speaks to the AG.
Are there any articles or someone's personal experiences with this type of scenario that could point us in the right direction and offset some of the initial data load into staging by minimizing logging?
Thanks,
Sue
Sue

Hi Sue,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SQL Server 2012 Always ON routing to particular server based on User Name

I have configured SQL Server 2012 with AlwaysON availability groups. I could route my connections to Secondary node when I put the applicationintent = readonly on the connection string. However I would like to route all of my connections from particular
user name to my read only node. How can I accomplish this without changing connection string (Reason is I would like to be able to route connections for read only query to some older application client that doesn't support applicationintent parameter).

Hello,
There is nothing built in that will allow you to dynamically re-route connections based on usernames. This may be achieved outside of SQL Server through some sort of network appliance, but I can't say for sure.
Would it be possible to upgrade the SQL Client (to 2012+) for the old application and then change the connection string?
Sean Gallardy | Blog |
Twitter

SQL Server 2012 Always ON Users Sync

Team,
We have a development cluster which is configured on Windows Server 2012. Recently we had an issue where the cluster failover happened momentarily and the roles were interchanged wrt to AlwaysON. During this process users lost connectivity and upon further
investigation, the users were orphaned on the other node and had to manually permission the users. Now that we have fixed the permission issue, please let me know whether this happens everytime whenever the cluster failover happens?
Also would like to seek your help in any user sync script which I can incorporate for the issue to sync up the logins.
SQL Version: 11.0.3000
Any help on this is much appreciated.
Regards,
Sharath

Hello,
During this process users lost connectivity and upon further investigation, the users were orphaned on the other node and had to manually permission the users. Now that we have fixed the permission issue, please let me know whether this happens
everytime whenever the cluster failover happens?
This can be two fold.
The first issue is the logins, as the logins exist on a server level and not a database level. If the logins don't exist, end users can't connect - simple.
The second issue is orphaned users. When using Windows Authentication, the SID (security identifier) for the login is pulled from AD and stays the same inside AD boundaries. When using SQL Authentication, the SID changes and is not the same even if the login
name is the same. In the situation you had, the logins may have existed but their SIDs are different and thus the user->login mapping is not correct, hence the orphaned user.
In order to have this not happen, the SQL Logins must be created on all other replicas using the SID= optional argument of
CREATE LOGIN statement. This ensures that the SID matches across all instances and orphaned users will not be an issue.
I'm not sure how you fixed the orphaned users for the databases when they failed over, but chances are if you just re-linked them you're going to have the same issue as you did before when it fails again. You'll need to remove the logins and re-create them
with the current login's SID that is working. You can find the SIDs in sys.sql_logins.
Sean Gallardy | Blog | Microsoft Certified Master

Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation. The documentation takes me windows 2008 R2 which is different than 2012!
Tired and trying to pick myself up off the floor!
Greg
Gman

In general, DTC is not required for SQL 2012. But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum. They would be more likely to know those situations where FTC might be needed by SharePoint.
.:|:.:|:. tim

Datastore config to connect Readonly SQL Server 2012

We upgrade our source database server from SQL Server 2008 to SQL Server 2012 Always On with High Availability model. There is a read-only mirror db server in this availabilty group.
We plan to use the read-only node for etl sources. In a oledbb connection string, we can connect the read-only instance by adding "ApplicationIntent=READONLY" string but i can not find any property in SAP BO Dataservices - data store object.
How can i connect to read-only instance with Data services 4.1.
Sample atl of a datastore object:
#__AW_Repository_Version '14.1.1.0000';
#__AW_Product_Version '14.1.1.354';
#__AW_ATL_Locale 'tur_tr.utf-8';
AlGUIComment ("ActaName_1" = 'RSavedAfterCheckOut', "ActaName_2" = 'RDate_created', "ActaName_3" = 'RDate_modified', "ActaValue_1" = 'YES', "ActaValue_2" = 'Thu Mar 14 15:24:46 2013', "ActaValue_3" = 'Mon Feb 10 17:40:07 2014', "x" = '-1', "y" = '-1')
CREATE DATABASE DATASTORE DS_SIS_INTEGRATION::'550a10ab-4313-4d6b-969f-d3a0d25bde37' SET ("DBLiveLoad" = 'no', "application_type" = 'Custom', "cdc_enabled" = 'no', "datastore_repotype" = 'local', "ds_configuration_enabled" = 'yes', "ds_configurations" = '<?xml version="1.0" encoding="WINDOWS-1254" ?>
<DSConfigurations>
<DSConfiguration default="true" name="Test">
<case_sensitive>yes</case_sensitive>
<database_type>Microsoft_SQL_Server</database_type>
<loader_xact_size>1000</loader_xact_size>
<locale_codepage>iso-8859-9</locale_codepage>
<locale_language>tur</locale_language>
<locale_territory><default></locale_territory>
<mssql_windows_authentication>no</mssql_windows_authentication>
<password>lorem ipsum</password>
<server_codepage>iso-8859-9</server_codepage>
<sql_server_database>SIS_INTEGRATION_TEST</sql_server_database>
<sql_server_dataserver>Pandoradev</sql_server_dataserver>
<sql_server_version>Microsoft SQL Server 2008</sql_server_version>
<user>boETLTest</user>
</DSConfiguration>
<DSConfiguration default="false" name="Production2012">
<database_type>Microsoft_SQL_Server</database_type>
<loader_xact_size>1000</loader_xact_size>
<locale_codepage>iso-8859-9</locale_codepage>
<locale_language>tur</locale_language>
<locale_territory><default></locale_territory>
<mssql_windows_authentication>no</mssql_windows_authentication>
<password>lorem ipsum</password>
<server_codepage>iso-8859-9</server_codepage>
<sql_server_database>SIS_INTEGRATION</sql_server_database>
<sql_server_dataserver>drake</sql_server_dataserver>
<sql_server_version>Microsoft SQL Server 2012</sql_server_version>
<user>boETL</user>
</DSConfiguration>
</DSConfigurations>
', "enable_data_transfer" = 'yes', "import_unknown_type" = 'no', "name" = 'DS_SIS_INTEGRATION', "pcache_force_utf16" = 'no', "unknown_type_size" = '255');
Thanks for your help

This is not about the security. There are two replicated sql servers. One of them is working read / write and one of them is working in read-only mode. We plan to decrease read load by connecting the read-only instance. But we do not know which server is read-only, sql server manages it.
If i can use oledb connection i can reach the read-only instance by adding ApplicationIntent=READONLY statement in connection string.
I'd like to know that i can connect to read-only instance of sql server in Data services.

I get one or the other error when i install SQL server 2012 SP1 in my Lab server

I get multiple errors when i install SQL server 2012 SP1 In my lab server.
Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
Below are error codes, screen shots and also a log of the error.
1. Eror code 0X84B40000
Also dint understand any thing from this article related to the above error
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
2. Eror code 0x851A001A
Can any one plz help as i always get one or the other error.
====================================
Screen shot:
Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
2. Log file content.
=================================
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-04 21:15:35
End time: 2014-05-04 21:51:45
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: SERVER1
Machine processor count: 2
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Basic
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Complete
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools SDK
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Integration Services
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: ms\sql
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SCOM
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SCOM
INSTANCENAME: SCOM
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SCOM
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: ms\sql
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: MS\Gautam, MS\SCOM Users
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
Detailed results:
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htm

Sorry about the error in the path, but you find the files that's the main thing.
Indeed it is a certificate problem:
2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
Anyway, this blog post,
http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
suggests the issue is a corrupted user profile, and you should try to use a different service account.
This blog also seems to have a simple solution, but I cannot vouch for that it will work:
http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
Erland Sommarskog, SQL Server MVP, [email protected]

Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"

Hello,
I have a big problem.
I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".
I already tried all solutions from Google for this problem but nothing works.
Can someone help me plase?
My System: Window 8 Pro with Visual Studio 2012.
Thanks
Sven

Would you please uplaod/share SQL Server setup logs
C:\Program
Files\Microsoft
SQL Server\110\Setup
Bootstrap\Log\20130125_133342
to file sharing service like SkyDrive.com
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread.

SQL Server 2012 with SP2 Slipstream ISO images do not install SP2

We see the same issue as described here:
http://support.microsoft.com/kb/2783963
when using the newly posted en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4351704.iso from MSDN.
We end up with SQL Server 2012 RTM instead of SP2 and have to run a second pass to install SP2 on top of RTM.
Is this a confirmed problem with an expected solution soon to follow?

Hi,
As per the link this seems to me a known issue. I cannot 100 % say because I have seen/faced this issue with
SP1 and you mentioned SP2. I would always suggest to install RTM only there is option to un select SP2 during installing.
Well thank you for reporting I guess Microsoft would take this as feedback.
Can you share setup log files please just for analysis
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL Server 2012 - Wat Is The Best Solution For Creating a Read Only Replicated/AlwaysOn Database

Hi there I was wondering if someone may have a best recommendation for the following requirement I have with regards setting up a third database server for reporting?
Current Setup
SQL Server 2012 Enterprise setup at two sites (Site A & Site B).
Configured to use AlwaysOn Availability groups for HA and DR.
Installed on Windows 2012 Servers.
This is all working and failover works fine and no issues. So…
Requirement
A third server needs to be added for the purpose of reporting, to be located on another site (Site C) possibly in another domain. This server needs to have a replicated read only copy of the live database from site A or Site B, whichever is in use. The Site
C reporting database should be as up-to-date to the Site A or Site B database as possible – preferably within a few seconds anyway….
Solution - What I believe are available to me
I believe I can use AlwaysOn and create a ReadOnly replica for the Site C. If so do I assume Site C needs to have the Enterprise version of SQL server i.e. to match Site A & Site B?
Using log shipping which if I am correct means the Site C does not need to be an Enterprise version.
Any help on the best solution for this would be greatly appreciated.
Thanks, Steve

for always on - all nodes should be part of one windows cluster..if there site C is on different domain - I do not think it works.
Logshipping works --as long as the sql on site C is is same or higher version(sql 2012 or above). you can only do read only.
IMHo, if you can make site C in the same domain then, Always is better solution else log shipping
also, if your database has enterprise level features such as - partitonin, data compression -- you cannot restore the database on lower editions- so you need to have enterprise edition.
Hope it Helps!!

SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
Keegan

Hi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

How to join a Domain Controller Server to an two-tier (SQL Server 2012) and Sharepoint 2013 (SP2013) farm

Hi,
I am trying to build a 3-tier SharePoint 2013 farm.
1. SQL Server 2012, Windows 2012 VM
2. DC Server, Windows 2012 VM
3. SharePoint 2013, Windows 2012 VM
I didn't built the DC server. Someone else did. However, I created about 14 service domain user accounts for SQL Server and SharePoint install and operation.
I was able to join the SQL Server into the SharePoint server farm using SharePoint 2013 Product Configuration Wizard. When I start the Central Admin, and click on Servers in the Farm, I only see the SharePoint server and SQL server,
but the DC server is not listed. Any suggestion on what did I miss?
Thanks
Jean

You cannot join the Domain Controller to your SharePoint farm. You must instead join each server from that farm to the domain that is served up by that DC. You will want to uninstall SharePoint and probably SQL before you do this. If it's
an option, I would re-provision your VMs completely and start fresh. Once you login to a new server, join that server to the target domain like this:
http://www.petri.co.il/join-windows-server-2012-to-domain.htm
You'd have to ensure that your DNS resolves to the target domain on the server being joined to the domain. If it doesn't, you can always use HOSTS entries to overcome that in the short term.
Once you've joined both the future SQL and SharePoint servers to the domain, you can install SQL Server and then SharePoint on their prospective servers to create your farm.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

SQL Server 2012 Infrastructure Best Practice

Hi,
I would welcome some pointers (direct advice or pointers to good web sites) on setting up a hosted infrastructure for SQL Server 2012. I am limited to using VMs on a hosted site. I currently have a single 2012 instance with DB, SSIS, SSAS on the same server.
I currently RDP onto another server which holds the BI Tools (VS2012, SSMS, TFS etc), and from here I can create projects and connect to SQL Server.
Up to now, I have been heavily restricted by the (shared tenancy) host environment due to security issues, and have had to use various local accounts on each server. I need to put forward a preferred environment that we can strive towards, which is relatively
scalable and allows me to separate Dev/Test/Live operations and utilise Windows Authentication throughout.
Any help in creating a straw man would be appreciated.
Some of the things I have been thinking through are:
1. Separate server for Live Database, and another server for Dev/Test databases
2. Separate server for SSIS (for all 3 environments)
3. Separate server for SSAS (not currently using cubes, but this is a future requirement. Perhaps do not need dedicated server?)
4. Separate server for Development (holding VS2012, TFS2012,SSMS etc). Is it worth having local SQL Server DB on this machine. I was unsure where SQL Server Agent Jobs are best run from i.e. from Live Db only, from another SQL Server Instance, or to
utilise SQL ServerAgent on all (Live, Test and Dev) SQL Server DB instances. Running from one place would allow me to have everything executable from one place, with centralised package reporting etc. I would also benefit from some license cost
reductions (Kingsway tools)
5. Separate server to hold SSRS, Tableau Server and SharePoint?
6. Separate Terminal Server or integrated onto Development Server?
7. I need server to hold file (import and extract) folders for use by SSIS packages which will be accessible by different users
I know (and apologise that) I have given little info about the requirement. I have an opportunity to put forward my requirement for x months into the future, and there is a mass of info out there which is not distilled in a way I can utilise. It would
be helpful to know what I should aim for, in terms of separate servers for the different services and/or environments (Live/Test/Live), and specifically best practice for where SQL Server Agent jobs should be run from , and perhaps a little info on how to
best control deployment/change control . (Note my main interest is not in application development, it is in setting up packages to load/refresh data marts fro reporting purposes).
Many thanks,
Ken

Hello,
On all cases, consider that having a separate server may increase licensing or hosting costs.
Please allow to recommend you Windows Azure for cloud services.
Answers.
This is always a best practice.
Having SSIS on a separate server allows you isolate import/export packages, but may increase network traffic between servers. I don’t know if your provider charges
money for incoming traffic or outgoing traffic.
SSAS on a separate server certainly a best practice too.
It contributes to better performance and scalability.
SQL Server Developer Edition cost about $50 dollars only. Are you talking about centralizing job scheduling on an on-premises computer than having jobs enable on a
cloud service? Consider PowerShell to automate tasks.
If you will use Reporting Services on SharePoint integrated mode you should install Reporting Services on the same server where SharePoint is located.
SQL Server can coexist with Terminal Services with the exception of clustered environments.
SSIS packages may be competing with users for accessing to files. Maybe copying them to a disk resource available for the SSIS server may be a better solution.
A few more things to consider:
Performance storage subsystem on the cloud service.
How Many cores? How much RAM?
Creating a Domain Controller or using active directory services.
These resources may be useful.
http://www.iis.net/learn/web-hosting/configuring-servers-in-the-windows-web-platform/sql-2008-for-hosters
http://azure.microsoft.com/blog/2013/02/14/choosing-between-sql-server-in-windows-azure-vm-windows-azure-sql-database/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How do you create a buffer of a geometry in SQL Server 2012?

Hello,
I am new to SQL Server 2012 and spatial data. I built a geometry object of coordinates from a polygon that I stored in a database. The code is below:
DECLARE @digb GEOMETRY;
SET @digb = GEOMETRY::STGeomFromText('POLYGON ((-79.927138 40.362654, -79.91883 40.364224, -79.915966 40.361067, -79.917897 40.359266, -79.927398 40.360142, -79.927138 40.362654))', 4269);
I am using SRID 4269 (Latitude/Longitude NAD83). I have no issues getting this geometry to load properly when the query is executed. (shown below)
My problem is that I am unable to create a valid buffer of 150 feet on this geometry. I have tried using these 3 statements below (I assumed BufferWithCurves() would be the one that would work); however, ALL of them returned to an invalid buffer of
the polygon (shown below):
- DECLARE @digbb GEOMETRY = @digb.STBuffer(2);
- DECLARE @digbb GEOMETRY = @digb.BufferWithCurves(2)
- DECLARE @digbb GEOMETRY = @digb.BufferWithTolerance(@BufferSize,250.0,1);
Does anyone have any idea of how creating this buffer of a geometry object (polygon mentioned above) in SQL Server 2012?
Thanks in advance for any help.
Nick

Hi Nick,
BTW, please do ask questions on the forum, that's what it's for. I only meant "if my explanation in that specific answer was unclear, let me know and I'll clarify". Feel free to start a new thread for each topic because that way, it's
might be easier for folks to search on.
Specific answers:
I haven't worked directly with the MapInfo loader but if you're working with SQL Server, I assume what they may be doing is looking for "geodesic SRIDs" that SQL Server supports (the ones listed in sys.spatial_reference_systems) and loading those
as geography, else geometry. That may be a good thing to do.
If you want to decide yourself, here's some (short) background.
Only SQL Server (I think PostGIS might have added it) has separate geography and geometry types. Everyone else always uses "geometry" and gives you (maybe) the ability to convert between SRIDs in the database. SQL Server doesn't have
this built-in; you'd need to use a library like PROJ4.
You can use geometry type to refer to geodesic SRIDs, but it doesn't have a way to "take the area using spatial instances in decimal degrees and come up with meters". So, if you only use it to display on a map, it will display correctly.
Or close enough. Same with intersects, intersection and the like. But anything like area, distance, or, in your case buffer using a specific number of meters, you need to use geography. You could have gotten somewhat similar-looking
results with geometry by making your input to STBuffer a sufficiently small fraction, but it would be a guess on your part, not a "150 feet" buffer.
You can't CAST/CONVERT between geometry and geography because they didn't want people to assume that these would do SRID conversion. However, there is a codeplex library "SQL Server Spatial Tools" (http://sqlspatialtools.codeplex.com/) that
has two methods: VacuousGeometryToGeography and vice-versa, that does the equivalent (but optimized) of taking one type, spitting it out in well-known text format, then using it to initialize the other type. Or you can do this in your own code.
In general, geography is for anything geodesic; geometry is for planar or projected coordinate systems (e.g state plane coordinate systems in US, that don't use Long/Lat). But geography is slightly slower in calculations (like intersects) because it's more
complex than simple Euclidian geometry. And folks in other platforms are used to using "geometry" and having the platform do the (sometimes fairly expensive) conversions on-the-fly. Or maybe you don't care about the area, distance, etc.
Even in the geography type, WKT specifies (Long Lat) not (Lat Long). This is because the OGC standard doesn't distinguish and calls things (X Y), and if you think about it, (X Y) is (Long Lat) not (Lat Long). The SQL Server geography-specific method MakePoint
has latitude first as a parameter. OGC or SQL/MM standard methods and property names start with "ST" in SQL Server (e.g. STIntersects); SQL Server-specific methods and properties do not (e.g. MakePoint, ReorientObject).
Finally, attempting to do spatial calculations with unlike SRIDs (e.g. intersects between SRID 4269 and 4326 instance) returns NULL.
One more post coming on this thread with some info/links.
Cheers, Bob

SQL Server 2012 Always On ?

Similar Messages

Maybe you are looking for