Merge pull request #2 from MicrosoftDocs/master

Update doc

Author: v-sutso

.openpublishing.publish.config.json

@@ -6,11 +6,17 @@
       "build_source_folder": "docs",
       "build_output_subfolder": "sql",
       "locale": "en-us",
+      "monikers": [],
+      "moniker_ranges": [
+        "= sql-server-2014",
+        "= azuresqldb-current || = azuresqldb-mi-current || = azure-sqldw-latest || >= aps-pdw-2016 || >= sql-server-2016 || >= sql-server-linux-2017 || = sqlallproducts-allversions"
+      ],
       "open_to_public_contributors": true,
       "type_mapping": {
         "Conceptual": "Content",
         "ManagedReference": "Content",
-        "RestApi": "Content"
+        "RestApi": "Content",
+        "LandingData": "Content"
       },
       "build_entry_point": "docs",
       "template_folder": "_themes",
@@ -43,6 +49,10 @@
     }
   ],
   "branch_target_mapping": {
+    "release-sqlseattle": [
+      "Publish",
+      "PDF"
+    ],
     "live": [
       "Publish",
       "PDF"
@@ -55,9 +65,11 @@
   "need_generate_pdf_url_template": true,
   "need_generate_pdf": false,
   "need_generate_intellisense": false,
+  "enable_branch_build_custom_validation": true,
+  "enable_pull_request_custom_validation": true,
   "Targets": {
     "Pdf": {
       "template_folder": "_themes.pdf"
     }
   }
-}
+}

.openpublishing.redirection.json

@@ -1,65 +1,33 @@
+## Index
+1. [Microsoft Open Source Code of Conduct](#microsoft-open-source-code-of-conduct)
+2. [Microsoft SQL Server Technical Documentation](#microsoft-sql-server-technical-documentation)
+    * [Contribute to documentation](#contribute-to-documentation)
+      + [Minor corrections](#minor-corrections)
+      + [Larger submissions](#larger-submissions)
+    * [Next steps](#next-steps)
+
 ## Microsoft Open Source Code of Conduct
 
 This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
 For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
 
-# Microsoft Technical Documentation Contributor Guide
-You've found the GitHub repository that houses the source for the technical documentation published on [https://docs.microsoft.com](https://docs.microsoft.com).
+# Microsoft SQL Server Technical Documentation
 
-This repository also contains guidance to help you contribute to our technical documentation. For a list of the articles in the contributors' guide, see [the index](https://github.com/MicrosoftDocs/azure-docs/blob/master/contributor-guide/contributor-guide-index.md).
+You've found the GitHub repository that houses the source for the SQL Server technical documentation published on [https://docs.microsoft.com](https://docs.microsoft.com).
 
 ## Contribute to documentation
 
-* [Ways to contribute](#ways-to-contribute)
-* [Code of conduct](#code-of-conduct)
-* [About your contributions to content](#about-your-contributions-to-azure-content)
-* [Repository organization](#repository-organization)
-* [Use GitHub, Git, and this repository](#use-github-git-and-this-repository)
-* [How to use markdown to format your topic](#how-to-use-markdown-to-format-your-topic)
-* [More resources](#more-resources)
-* [Index of all contributors' guide articles](contributor-guide/contributor-guide-index.md) (opens new page)
-
-## Ways to contribute
-
-* GitHub user interface. Either find the article in this repository, or visit the article on [https://docs.microsoft.com](https://docs.microsoft.com) and click the Edit link in upper right hand corner of the topic. That takes you to the the article file in GitHub.
-* For substantial changes, adding or changing images, or contributing a new article, you need to fork this repository, install Git Bash, Markdown Pad, and learn some git commands.
+Anyone can submit changes to the SQL Server documentation. For more information, see [How to contribute to SQL Server Documentation](https://aka.ms/editsqldocs).
 
-## About your contributions to content
 ### Minor corrections
-Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the [docs.microsoft.com Terms of Use](https://docs.microsoft.com/legal/termsofuse).
+Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the [docs.microsoft.com - Terms of Use](https://docs.microsoft.com/legal/termsofuse).
 
 ### Larger submissions
 If you submit a pull request with significant changes to documentation and code examples or new content, we'll send a comment in GitHub asking you to submit an online Contribution License Agreement (CLA) if you are not an employee of Microsoft. We need you to complete the online form before we can accept your pull request.
 
-## Use GitHub, Git, and this repository
-For information about how to contribute, how to use the GitHub user interface to contribute small changes, and how to fork and clone the repository for more significant contributions, see [Install and set up tools for authoring in GitHub](https://github.com/MicrosoftDocs/azure-docs/blob/master/contributor-guide/tools-and-setup.md).
-
-If you install GitBash and work locally, the steps for creating a new local working branch, making changes, and submitting the changes back to the main branch are listed in [Git commands for creating a new article or updating an existing article](https://github.com/MicrosoftDocs/azure-docs/blob/master/contributor-guide/git-commands-for-master.md)
-
-### Branches
-Create local working branches that target a specific scope of change. Each branch should be limited to a single concept/article both to streamline work flow and reduce the possibility of merge conflicts. Appropriate scope for a new branch:
-
-* A new article (and associated images)
-* Spelling and grammar edits on an article.
-* Applying a single formatting change across a large set of articles (e.g. new copyright footer).
-
-## How to use markdown to format your topic
-All the articles in this repository use GitHub flavored markdown. [Markdown basics](https://help.github.com/articles/getting-started-with-writing-and-formatting-on-github/)
-
-
-## Article metadata
-Article metadata enables certain functionalities such as author and contributor attribution, breadcrumbs, article descriptions, and SEO optimizations as well as reporting Microsoft uses to evaluate content performance. [Here's the guidance for making sure your metadata is done right](contributor-guide/article-metadata.md).
-
-### Labels
-Automated labels are assigned to pull requests to help us manage the pull request workflow and to help let you know what's going on with your pull request:
-
-* Contribution License Agreement related
-  * cla-not-required: The change is relatively minor and does not require that you sign a CLA.
-  * cla-required: The scope of the change is relatively large and requires that you sign a CLA.
-  * cla-signed: The contributor signed the CLA, so the pull request can now move forward for review.
-* Pillar labels: Labels such as PnP, Modern Apps, and TDC help categorize the pull requests by the internal organization that needs to review the pull request.
-* Change sent to author: The author has been notified of the pending pull request.
+## Next steps
 
-## More resources
-See the [index of our contributor's guide](https://github.com/MicrosoftDocs/azure-docs/blob/master/contributor-guide/contributor-guide-index.md) for all our guidance topics.
+Explore the following resources:
 
+- [How to contribute to SQL Server Documentation](https://aka.ms/editsqldocs)
+- [SQL Server documentation home](https://docs.microsoft.com/sql/index)

ReadMe.md

@@ -236,6 +236,6 @@ GUIDELINES for Next Steps
 
 ## Next steps
 
-Database backups are an essential part of any business continuity and disaster recovery strategy because they protect your data from accidental corruption or deletion. To see how database backups into a broader strategy, see [Business continuity overview](sql-database-business-continuity.md).
+Database backups are an essential part of any business continuity and disaster recovery strategy because they protect your data from accidental corruption or deletion. To see how database backups fit into a broader strategy, see [Business continuity overview](sql-database-business-continuity.md).
 
 

contributor-guide/templates/overview-template-annotated-example.md

@@ -1,7 +1,7 @@
 ---
 <!------------------
 
-This is an annotated example of a tutorial with high CSAT (https://docs.microsoft.com/en-us/azure/app-service-web/web-sites-dotnet-get-started). 
+This is an annotated example of a tutorial with high CSAT (https://docs.microsoft.com/azure/app-service-web/web-sites-dotnet-get-started). 
 
 Tutorials show users how to solve a problem. They include prerequisites and steps. They are not "learn concepts" topics. 
 

contributor-guide/templates/tutorial-template-annotated-example.md

@@ -1,7 +1,7 @@
 ---
 <!------------------
 
-This is an outline of a tutorial that has high CSAT (https://docs.microsoft.com/en-us/azure/app-service-web/web-sites-dotnet-get-started). 
+This is an outline of a tutorial that has high CSAT (https://docs.microsoft.com/azure/app-service-web/web-sites-dotnet-get-started). 
 
 Tutorials show users how to solve a problem. They include prerequisites and steps. They are not "learn concepts" topics. 
 
@@ -53,7 +53,7 @@ GUIDELINES for procedures (steps)
 
 ## Procedure title (H2)
 
-Add procedures and include screenshots where helpful.
+Add procedures and include screenshots (of equal dimensions) where helpful.
 
 ## Next steps (H2)
 

contributor-guide/templates/tutorial-template.md

@@ -1,8 +1,3 @@
-# Install and set up tools for authoring in Git
+# How to contribute to SQL Documentation
 
-> [!NOTE]
-> See the contributors guide in the [azure-docs repo](https://github.com/MicrosoftDocs/azure-docs/tree/master/contributor-guide).
-The guide contains informaton on permissions, installation of tools, and the basics for making edits and pull erquests.
-
-- [Git basics] (https://git-scm.com/book/en/v2/Getting-Started-Git-Basics).
-- [Visual Studio Code - VS Code,](https://www.visualstudio.com/products/code-vs.aspx) A good markdown editor with git integration.  It's updated often and keeps getting better.
+This guide has been moved. Please see [How to contribute to SQL Server Documentation](https://aka.ms/editsqldocs).

contributor-guide/tools-and-setup.md

@@ -0,0 +1,66 @@
+---
+title: "Books Online for SQL Server 2014 | Microsoft Docs"
+ms.date: "05/25/2017"
+ms.prod: "sql-server-2014"
+ms.technology: release-landing
+ms.reviewer: ""
+ms.topic: "index-page "
+f1_keywords: 
+  - "sql12.portal.f1"
+helpviewer_keywords: 
+  - "documentation [SQL Server], home page"
+  - "Help [SQL Server]"
+  - "SQL Server, documentation"
+  - "home page [SQL Server]"
+  - "Help [SQL Server], documentation home page"
+  - "Books Online [SQL Server], home page"
+  - "portal page [SQL Server]"
+ms.assetid: 674933a8-e423-4d44-a39b-2a997e2c2333
+author: craigg-msft
+ms.author: craigg
+manager: craigg
+---
+# Books Online for SQL Server 2014
+
+  Welcome to [!INCLUDE[msCoName](../includes/msconame-md.md)]® Books Online for [!INCLUDE[msCoName](../includes/msconame-md.md)] [!INCLUDE[ssCurrent](../includes/sscurrent-md.md)]®. Books Online contains the task descriptions and reference documentation that describes how to perform data management and business intelligence work by using [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)].  
+  
+ **Try it out:**  
+ ![Azure Virtual Machine small](../sql-server/media/what-s-new-in-sql-server-2016/azure-virtual-machine-small.png) Have an Azure account?  Then go **[Here](https://ms.portal.azure.com/?flight=1#create/Microsoft.SQLServer2016RTMEnterpriseWindowsServer2012R2)** to spin up a Virtual Machine with SQL Server 2014 Service Pack 1 (SP1) already installed. For more information on SQL Server 2014 (SP1), see [SQL Server 2014 Service Pack 1 release information ](https://support.microsoft.com/en-us/kb/3058865). 
+  
+## SQL Server Technologies  
+
+ [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] includes several data management and analysis technologies. Click on the links in the following table to find the feature, task, and reference documentation for each technology.  
+  
+|||  
+|-|-|  
+|![Database Engine icon](media/database-engine.gif "Database Engine icon")|[Database Engine](../database-engine/sql-server-database-engine-overview.md)<br /><br /> The Database Engine is the core service for storing, processing and securing data. The Database Engine provides controlled access and rapid transaction processing to meet the requirements of the most demanding data consuming applications within your enterprise. The Database Engine also provides rich support for sustaining high availability.|  
+|![DQS Logo for BOL home topic](media/dqs-logo.jpg "DQS Logo for BOL home topic")|[Data Quality Services](../data-quality-services/data-quality-services.md)<br /><br /> SQL Server Data Quality Services (DQS) provides you with a knowledge-driven data cleansing solution. DQS enables you to build a knowledge base, and then use that knowledge base to perform data correction and deduplication on your data, using both computer-assisted and interactive means. You can use cloud-based reference data services, and you can build a data management solution that integrates DQS with SQL Server Integration Services and Master Data Services.|  
+|![Analysis Services icon](media/analysisserver.gif "Analysis Services icon")|[Analysis Services](../analysis-services/analysis-services.md)<br /><br /> [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] is an analytical data platform and toolset for personal, team, and corporate business intelligence. Servers and client designers support traditional OLAP solutions, new tabular modeling solutions, as well as self-service analytics and collaboration using PowerPivot, Excel, and a SharePoint Server environment. [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] also includes Data Mining so that you can uncover the patterns and relationships hidden inside large volumes of data.|  
+|![Integration Services icon](media/dts.gif "Integration Services icon")|[Integration Services](../integration-services/sql-server-integration-services.md)<br /><br /> [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] is a platform for building high performance data integration solutions, including packages that provide extract, transform, and load (ETL) processing for data warehousing.|  
+|![mds_cm_icon](media/mds-cm-icon.gif "mds_cm_icon")|[Master Data Services](../master-data-services/master-data-services.md)<br /><br /> [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)] is the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] solution for master data management. A solution built on [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)] helps ensure that reporting and analysis is based on the right information. Using [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)], you create a central repository for your master data and maintain an auditable, securable record of that data as it changes over time.|  
+|![Replication icon](media/replication.gif "Replication icon")|[Replication](../relational-databases/replication/sql-server-replication.md)<br /><br /> Replication is a set of technologies for copying and distributing data and database objects from one database to another, and then synchronizing between databases to maintain consistency. By using replication, you can distribute data to different locations and to remote or mobile users by means of local and wide area networks, dial-up connections, wireless connections, and the Internet.|  
+|![Reporting Services icon](media/reportingservices.gif "Reporting Services icon")|[Reporting Services](../reporting-services/create-deploy-and-manage-mobile-and-paginated-reports.md)<br /><br /> Reporting Services delivers enterprise, Web-enabled reporting functionality so you can create reports that draw content from a variety of data sources, publish reports in various formats, and centrally manage security and subscriptions.|  
+  
+## SQL Server Information on the Web  
+
+ [!INCLUDE[msCoName](../includes/msconame-md.md)] publishes additional information about [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] in several Web sites.  
+  
+ **SQL Server Web Sites**  
+  
+-   [SQL Server on Microsoft.com](https://go.microsoft.com/fwlink/?linkid=8504)  
+  
+-   [SQL Server Resource Center](https://go.microsoft.com/fwlink/?linkid=218841)  
+  
+-   [SQL Server TechCenter](https://go.microsoft.com/fwlink/?linkid=28107)  
+  
+-   [SQL Server Developer Center](https://go.microsoft.com/fwlink/?LinkId=42457)  
+  
+-   [Data Platform Developer Center](https://go.microsoft.com/fwlink/?LinkId=17386)  
+  
+-   [XML Developer Center](https://go.microsoft.com/fwlink/?LinkId=42458)  
+  
+## See Also  
+
+ [SQL Server Configuration Manager Help](../tools/configuration-manager/sql-server-configuration-manager-help.md)  
+  
+  

docs/2014/2014-toc/books-online-for-sql-server-2014.md

@@ -0,0 +1,34 @@
+---
+title: "Case Study: Building an Enterprise Ecosystem with Microsoft Dynamics ERP and SQL Server 2014 Replication for Scalability and Performance | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/06/2017"
+ms.prod: "sql-server-2014"
+ms.reviewer: ""
+ms.topic: conceptual
+ms.assetid: 2b0b5ab7-4e08-431a-bd59-360177c4565c
+author: mashamsft
+ms.author: mathoma
+manager: craigg
+---
+# Case Study: Building an Enterprise Ecosystem with Microsoft Dynamics ERP and SQL Server 2014 Replication for Scalability and Performance
+
+  **Summary:** This paper covers the following scenarios:  
+How to use transactional replication in SQL Server 2014 to distribute the transactions from Dynamics AX clients across multiple nodes. Because data is maintained across the nodes in real-time, transactional replication provides data redundancy, which increases the availability of data, includes data available for more efficient performance analysis.  
+How to understand the specifics involved while leveraging transactional replication to build highly scalable Enterprise ecosystems in Microsoft Dynamics ERP. Deliver high performance and scalability without customizing the AX out-of-box features.  
+  
+ Transactional replication is typically used in server-to-server workflows that require high throughput. These include scenarios, such as improving scalability and availability, data warehousing and reporting, integrating data from multiple sites, integrating heterogeneous data, and offloading batch processing. This white paper describes a distinct scenario and associated patterns where transactional replication is leveraged in Microsoft Dynamics ERP. It also covers the challenges and best practices when considering transactional replication to build enterprise solutions specific to Enterprise Resource Planning (ERP), as well as the performance analysis at different stages.  
+  
+ This content is suitable for developers, architects, and database administrators. It is assumed that readers of this white paper have basic knowledge of SQL Server 2008, 2012, or 2014 as well as SQL Server administration experience.  
+  
+ **Writer:**Prabhakaran Sethuraman (PRAB), Microsoft  
+  
+ **Technical Reviewers:**Prabhakaran Sethuraman (PRAB), Microsoft; Santosh Padhy, Microsoft; Pavel Majstrov, Microsoft; Karthik Sankaranarayanan, Microsoft; Jon Acone, Microsoft; David Stahlkopf, Microsoft;Kent Oldenburger, Microsoft; Mandi Ohlinger, Microsoft; Jason Roth, Microsoft  
+  
+ **Published:**October 2015  
+  
+ **Applies to:**SQL Server 2008, SQL Server 2012, and SQL Server 2014  
+  
+ To review the document, please download the  
+        [Case Study: Building an Enterprise Ecosystem with Microsoft Dynamics ERP and SQL Server 2014 Replication for Scalability and Performance](https://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/A%20Case%20Study%20Using%20Replication%20to%20Build%20an%20Enterprise%20Ecosystem%20in%20Microsoft%20Dynamics%20ERP%20for%20Scalability%20and%20Performance.docx) Word document.  
+  
+