SQL Server 2012 Best Practices

We are having a lively debate about how to configure our servers. One application per instance (1 or more databases) or mix applications in one instance. Can you give me some direction as to how to pursue this question? Thanks!

It depends on the applications.
If the application needs to be in isolated instance, so you have to go for multiple instances.
if the applications need different SQL Server configuration such collation etc. so you need to install separate instances.
If the applications have heavy tempdb usage, so may be you want to have separate tempdb on separate disks, and you need multiple instances.
If the applications have integrated security model with SQL Server ( which inherit from SQL Server security model ), so you need multiple instances.
SQL Server has very strong power to handle multiple databases and we have more that 500 database on one instance, but all of them need same SQL Server configuration ( same collation, memory, cpu, etc ).
If you buy these applications, so you can ask their vendor support team. Otherwise, if you write the applications, you can make this decision.
sqldevelop.wordpress.com

Similar Messages

License type of SQL Server 2005 Best Practices Analyzer

Hi everybody.
I need to install in my organization the software "SQL Server 2005 Best Practices Analyzer" but I need to know if this application it's free licensing. I have seen on several web sites about this tool it's free but not in official microsoft
web page. So, where can I find the official microsoft information about the type of licensing of "SQL Server 2005 Best Practices Analyzer" ?
Thanks of your support

Hello Erland.
I followed your advice and I have read the terms of use of this software. I stop at point 3 (which I highlighted). Based on this point, I doubt it is about using this application. Furthermore nowhere says that this software is free to use.
Would appreciate if someone can clarify this to me.
=============================================================
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER 2005 BEST PRACTICES ANALYZER:
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you.
Please read them. They apply to the software named above, which includes the media on which you received it, if any.
The terms also apply to any Microsoft
* updates,
* supplements,
* Internet-based services, and
* support services
for this software, unless other terms accompany those items.
If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.
If you comply with these license terms, you have the rights below.
1.
INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your devices.
2.
INTERNET-BASED SERVICES. Microsoft provides Internet-based services with the software.
It may change or cancel them at any time.
3.
SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software.
Microsoft reserves all other rights.
Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement.
In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways.
You may not
* work around any technical limitations in the software;
* reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
* make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
* publish the software for others to copy;
* rent, lease or lend the software;
* transfer the software or this agreement to any third party; or
* use the software for commercial software hosting services.
4.
BACKUP COPY. You may make one backup copy of the software.
You may use it only to reinstall the software.
5.
DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes.
6.
EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the software.
These laws include restrictions on destinations, end users and end use.
For additional information, see www.microsoft.com/exporting.
7.
SUPPORT SERVICES. Because this software is "as is," we may not provide support services for it.
8.
ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services.
9.
APPLICABLE LAW.
a. United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles.
The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.
10.
LEGAL EFFECT. This agreement describes certain legal rights.
You may have other rights under the laws of your country.
You may also have rights with respect to the party from whom you acquired the software.
This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
11.
DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED "AS-IS."
YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS.
YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT CANNOT CHANGE.
TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
12.
LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00.
YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
This limitation applies to
* anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
* claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages.
The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.
Please note: As this software is distributed in Quebec, Canada, some of the clauses in this agreement are provided below in French.

SQL Server 2008 - Best Practices Analyzer

Is there a version of SQL Server 2008 Best Practices Analyzer available for download? If not, can I use BPA for SQL Server 2005 to run a DB assessment on a SQL Server 2008 database? Please let me know what your recommendation is?
Thanks

Microsoft® SQL Server® 2008 R2 Best Practices Analyzer has been released for few months.
More details here
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=0fd439d7-4bff-4df7-a52f-9a1be8725591

Storage Server 2012 best practices? Newbie to larger storage systems.

I have many years managing and planning smaller Windows server environments, however, my non-profit has recently purchased
two StoreEasy 1630 servers and we would like to set them up using best practices for networking and Windows storage technologies. The main goal is to build an infrastructure so we can provide SMB/CIFS services across our campus network to our 500+ end user
workstations, taking into account redundancy, backup and room for growth. The following describes our environment and vision. Any thoughts / guidance / white papers / directions would be appreciated.
Networking
The server closets all have Cisco 1000T switching equipment. What type of networking is desired/required? Do we
need switch-hardware based LACP or will the Windows 2012 nic-teaming options be sufficient across the 4 1000T ports on the Storeasy?
NAS Enclosures
There are 2 StoreEasy 1630 Windows Storage servers. One in Brooklyn and the other in Manhattan.
Hard Disk Configuration
Each of the StoreEasy servers has 14 3TB drives for a total RAW storage capacity of 42TB. By default the StoreEasy
servers were configured with 2 RAID 6 arrays with 1 hot standby disk in the first bay. One RAID 6 array is made up of disks 2-8 and is presenting two logical drives to the storage server. There is a 99.99GB OS partition and a 13872.32GB NTFS D: drive.The second
RAID 6 Array resides on Disks 9-14 and is partitioned as one 11177.83 NTFS drive.
Storage Pooling
In our deployment we would like to build in room for growth by implementing storage pooling that can be later
increased in size when we add additional disk enclosures to the rack. Do we want to create VHDX files on top of the logical NTFS drives? When physical disk enclosures, with disks, are added to the rack and present a logical drive to the OS, would we just create
additional VHDX files on the expansion enclosures and add them to the storage pool? If we do use VHDX virtual disks, what size virtual hard disks should we make? Is there a max capacity? 64TB? Please let us know what the best approach for storage pooling will
be for our environment.
Windows Sharing
We were thinking that we would create a single Share granting all users within the AD FullOrganization User group
read/write permission. Then within this share we were thinking of using NTFS permissioning to create subfolders with different permissions for each departmental group and subgroup. Is this the correct approach or do you suggest a different approach?
DFS
In order to provide high availability and redundancy we would like to use DFS replication on shared folders to
mirror storage01, located in our Brooklyn server closet and storage02, located in our Manhattan server closet. Presently there is a 10TB DFS replication limit in Windows 2012. Is this replicaiton limit per share, or total of all files under DFS. We have been
informed that HP will provide an upgrade to 2012 R2 Storage Server when it becomes available. In the meanwhile, how should we designing our storage and replication strategy around the limits?
Backup Strategy
I read that Windows Server backup can only backup disks up to 2TB in size. We were thinking that we would like
our 2 current StoreEasy servers to backup to each other (to an unreplicated portion of the disk space) nightly until we can purchase a third system for backup. What is the best approach for backup? Should we use Windows Server Backup to be capturing the data
volumes?
Should we use a third party backup software?

Hi,
Sorry for the delay in reply.
I'll try to reply each of your questions. However for the first one, you may have a try to post to Network forum for further information, or contact your device provider (HP) to see if there is any recommendation.
For Storage Pooling:
From your description you would like to create VHDX on RAID6 disks for increasment. It is fine and as you said it is 64TB limited. See:
Hyper-V Virtual Hard Disk Format Overview
http://technet.microsoft.com/en-us/library/hh831446.aspx
Another possiable solution is using Storage Space - new function in Windows Server 2012. See:
Storage Spaces Overview
http://technet.microsoft.com/en-us/library/hh831739.aspx
It could add hard disks to a storage pool and creating virtual disks from the pool. You can add disks later to this pool and creating new virtual disks if needed.
For Windows Sharing
Generally we will have different sharing folders later. Creating all shares in a root folder sounds good but actually we may not able to accomplish. So it actually depends on actual environment.
For DFS replication limitation
I assume the 10TB limitation comes from this link:
http://blogs.technet.com/b/csstwplatform/archive/2009/10/20/what-is-dfs-maximum-size-limit.aspx
I contacted DFSR department about the limitation. Actually DFS-R could replicate more data which do not have an exact limitation. As you can see the article is created in 2009.
For Backup
As you said there is a backup limitation (2GB - single backup). So if it cannot meet your requirement you will need to find a third party solution.
Backup limitation
http://technet.microsoft.com/en-us/library/cc772523.aspx
If you have any feedback on our support, please send to [email protected]

SQL Server 2005 Best Practices Analyzer

... has been released yesterday as an independently serviceable tool.
Looking forward to your experiences
Rudi

... has been released yesterday as an independently serviceable tool.
Looking forward to your experiences
Rudi

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

SQL Server 2008 / 2012 - Best practices document

Hello Everyone
Can anybody share SQL Server 2008 / 2012 - Best practices.
Regards
Prashanth
SharePoint Administrator

Take a look here:
http://channel9.msdn.com/Series/Tuning-SQL-Server-2012-for-SharePoint-2013/Tuning-SQL-Server-2012-for-SharePoint-2013-01-Key-SQL-Server-and-SharePoint-Server-Integration-Conce (4 part video series)
https://technet.microsoft.com/en-us/library/hh292622.aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

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!!

In sql server 2012 or 2014 which one is best for production enviornment

Dear All,
right now we are using sql server 2008 r2 we want to upgrade our production servers to latest versions.
i wnat to know which one is best in sql server 2012 & 2014.
Thanks in Advance!!!

Dear All,
right now we are using sql server 2008 r2 we want to upgrade our production servers to latest versions.
i wnat to know which one is best in sql server 2012 & 2014.
Thanks in Advance!!!
I will not qualify it as best. Best depends on your requirement. 2008 r2 is much cheaper than SS2012 and SS2014. First make sure what all features you need in your new environment. Please read below link for features supported by various editions of SQL
server
http://msdn.microsoft.com/en-us/library/cc645993.aspx
If you think 2012/2014 fits in your requirement well then go ahead.
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

Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..

Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..i mean enterprise version BI version or standard version.. i just need a detailed comparison if available please thank you

As of right this very second, SQL Server 2014 is not supported. SharePoint 2013 supports:
One of the following:
The 64-bit edition of Microsoft SQL Server 2012.
The 64-bit edition of SQL Server 2008 R2 Service Pack 1
Hardware and software requirements for SharePoint 2013
Edit: I may be mistaken. It looks like the April 2014 CU adds support for SQL Server 2014. If this is the case generally going with the latest SQL Edition provides you with the latest SQL functionality. I'm not aware of any SharePoint features that would
make use of functionality that is new to SQL Server 2014 but this could change with a future service pack.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Best procedure to downgrade a SQL Server 2012 SP2 installation from Enterprise edition to Standard edition

Hi,
following a purpose change for a database server, I need to downgrade the SQL Server 2012 SP 2 installation from Enterprise to Standard edition.
Does it exist the best procedure to do it in a secure manner with a low impact?
Many thanks

Please note that while you are downgrading by uninstalling and reinstalling and then restoring backup taken from 2012 enterprise to standard , if backup contains data about used enterprise features you would not be able to restore the backup so BE
CAREFUL.
You should , if possible, get a new box install SQL Server standard and try restoring backup if it fails disable enterprise features and again take backup and then you would be able to restore.
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 Article
MVP

SQL 2012 Best Practice Analyzer issue with nothing available in pulldown on Microsoft Baseline Configuration Analyzer V2.0

We have tried using both a Windows 7 and a Windows 8 machine and still cannot see any items available in the pulldown (ie. no sql 2012 or anything) Is this a known issue and BPA does not work for SQL 2012? Any suggestions? I've seen several
posts with the same issue but, no resolution.
Laura

Hi Laura,
I installed Microsoft Baseline Configuration Analyzer 2.0 successfully. I can select a product: SQL Server 2012 BPA. Do you mean this?
Thanks.
If you have any feedback on our support, please click
here.
Maggie Luo
TechNet Community Support

SQL Server 2012 SP2 NTService Accounts Access Denied starting services

We have an SQL Server 2012 SP1 which was running perfectly until we applied the SQL Server 2012 SP2.
After SP2 was installed and the server rebooted all the associated SQL services that uses NTService\xxxxxxx accounts failed to start with Error 5: Access Denied.
We were able to change the services to Local System account but I just want to understand why this occurred and is this ok?
Has anyone had a similar issue or can anyone assist with an explanation?

Hi Giulio,
Based on your description, I tested the scenario as yours. After applying SQL Server 2012 SP2, I reboot the server , then restart all the associated SQL Server services that use NT SERVICE\<SERVICENAME> accounts successfully.
According to the error message, it might be caused by that NT SERVICE\<SERVICENAME> accounts don’t have sufficient permissions to access the SQL Server services installation folders. You can post detailed information in the SQL Server Errorlog file
for analysis.
In addition, Local System is a very high-privileged built-in account. It has extensive privileges on the local system and acts as the computer on the network. And it is not recommend to use local system account for running SQL Server services. For more details
about configuring SQL Server Service accounts, you can review the following links.
Configure Windows Service Accounts and Permissions:
http://msdn.microsoft.com/EN-US/library/ms143504.aspx#Windows
Best Practices For Using SQL Server Service Accounts:
http://blogs.technet.com/b/canitpro/archive/2012/02/08/the-sql-guy-post-15-best-practices-for-using-sql-server-service-accounts.aspx
Thanks,
Lydia Zhang

Using SQL Server 2012 SSIS to Extract Data From SAP

Hi
What is the current best practice for using SQL Server 2012 SSIS to extract data from SAP R3? Please note we are looking for a solution that does not use SAP BW or SAP OHS.
Ideally we would like to build our ETL SSIS process to make a .NET call to an SAP RFC procedure and avoid using web services.
With SS2012 can we use any of these without using SAP BW:
- SAP .NET Connector
- MS ADO .NET
- BizTalk .NET 3.0 Adapter
Thanks and take care,
Shayne

Hi Shayne,
You can use the .NET Framework Data Provider for mySAP Business Suite along with SQL Server Integration Service (SSIS) to import data from an SAP system into SQL Server database tables, flat files, or other compatible destination types. You can create an SSIS
package that can be executed to import data from an SAP system.
You must use the SQL Server Import and Export wizard to import data into the SQL Server database. You must provide a select query to specify data to be imported. The query must confirm to the semantics supported by the Data Provider for SAP. You can start the
SQL Server Import Export Wizard either from the SQL Server Management Studio or from an Integration Service project in Visual Studio. Detail steps please see:
Importing SAP Data Using SQL Server Management Studio:
http://msdn.microsoft.com/en-us/library/cc185161(v=bts.10).aspx
Importing SAP Data Using Visual Studio:
http://msdn.microsoft.com/en-us/library/cc185254(v=bts.10).aspx
Please feel free to ask if you have any question.
Thanks,
Eileen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

SQL Server 2012 Multi-Site clustering with 2 nodes for HA and DR

Usually we setup 2 Node Prod cluster for Local HA and 1 or 2 Nodes in other data centre for DR
Given that we have an option to setup multi-site / multi-subnet clustering from SQL 2008 R2/2012. I am planning to use just 2 nodes, 1 in prod data centre and 1 in DR data centre with 2 or 3 instances. This will act as both HA and DR solution.
I would like to know if this solution is good, and any disadvantages, any best practices, etc.? By implementing this I can save some cost on physical servers.
Following will be configured:
* Will be using different subnets, quorum on different server with "Node and File Share Majority"
* All virtual IPs will be registered for virtual name, and Subnetdelay, Subnet threshold will be modified accordingly
* All nodes on same domain
* Use SAN Disk with replication to DR site

SQL 2008 R2 doesn't support multi-subnet clustering. You would still need 3rd party component like VLAN and Disk Replication. SQL 2012 is the first version to support multi-subnet clustering without using VLAN. you would still need disk replication hardware/software.
Taken from my book
Since nodes are often located in two different data centers at geographically dispersed locations, there is no shared storage between the nodes in a multi-site cluster. Clustering across two different data centers provides a higher level of availability and
protection at the storage level as we have more than a single copy of the data.
For SAN replication technology implemented in such clusters, the main activity is to keep data replicated between the sites. Typically, if we have nodes on two different sites, we would have two different network infrastructures and the nodes would be in
different subnets. In such cases, if we are on a SQL Server version before 2012, we need to use third party VLAN (Virtual LAN) technology so that one IP address travels between two sites. This is called wide-IP. Companies hesitate with this solution because
of the need to buy a third party solution to deploy the VLAN. Using VLAN technology means the same IP address would failover to the remote site in case of a local site disaster. Network administration might consider this as an overhead to maintenance and an
extra piece of the networking component that needs to be secure.
With SQL Server 2012 we do not need to use stretch VLAN technology but SAN replication is still needed for multi-site clustering. The OS version for this can be from Windows Server 2008 R2 and above. In this deployment, we can have a SQL virtual network
name having an “OR” dependency on two different IP addresses. One address would be representing each subnet. With the “OR” dependency, if IP1 or IP2 is online we just use the network name. This is one of the Enterprise Editions only features.
Other option which you can think of, without using 3rd party solutions would be AlwaysOn Availability Group. I have written details about it in my book.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

SQL Server 2012 Best Practices

Similar Messages

Maybe you are looking for