St.louie

.editorconfig

@@ -0,0 +1,14 @@
+; This file is for unifying the coding style for different editors and IDEs.
+; More information at http://editorconfig.org
+
+root = true
+
+[*.php]
+indent_style = space
+indent_size = 4
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.bat]
+end_of_line = crlf

.gitignore

@@ -162,7 +162,7 @@ DocProject/Help/html
 
 # Publish Web Output
 *.azurePubxml
-# TODO: Comment the next line if you want to checkin your web deploy settings 
+# TODO: Comment the next line if you want to checkin your web deploy settings
 # but database connection strings (with potential passwords) will be unencrypted
 *.pubxml
 *.publishproj
@@ -441,3 +441,7 @@ samples/features/sql-management-objects/src/out/CodeCoverage/CodeCoverage.config
 # Certificates
 *.pem
 *.p12
+
+# Composer
+/vendor/
+/samples/databases/wide-world-importers/wwi-ssdt/wwi-ssdt/WideWorldImporters.publish.xml

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "dotnet.defaultSolution": "disable"
+}

README.md

@@ -1,27 +1,33 @@
 ![](./media/solutions-microsoft-logo-small.png)
 
-# SQL Server Samples Repository
-This GitHub repository contains code samples that demonstrate how to use Microsoft's SQL products including SQL Server, Azure SQL Database, and Azure SQL Data Warehouse. Each sample includes a README file that explains how to run and use the sample.
+# Azure Data SQL Samples Repository
+This GitHub repository contains code samples that demonstrate how to use Microsoft's Azure Data products including SQL Server, Azure SQL Database, Azure Synapse, and Azure SQL Edge. Each sample includes a README file that explains how to run and use the sample.
 
-Note that certain features like In-Memory OLTP are edition specific for SQL Server and would be possible to implement if the edition which supports that feature is being used to run the sample. 
+Please note that specific features, such as In-Memory OLTP, are edition-specific for SQL Server. These features will only be available if the edition that supports them is used to run the sample.
 
 ## Releases in this repository
 
-Releases allow you to conveniently download sample databases or applications without the need to build them from source code. This SQL Server samples repository has the following notable releases:
+Releases provide convenient downloads of sample databases and applications, eliminating the need to build them from source code. This SQL Server samples repository offers the following notable releases:
 
   - [Wide World Importers sample database v1.0](https://github.com/Microsoft/sql-server-samples/releases/tag/wide-world-importers-v1.0) is the main sample for SQL Server 2016 and Azure SQL Database. It contains both an OLTP and an OLAP database.
   - [In-Memory OLTP Performance Demo v1.0](https://github.com/Microsoft/sql-server-samples/releases/tag/in-memory-oltp-demo-v1.0) illustrates the performance benefits of the In-Memory OLTP technology built into SQL Server and Azure SQL Database.
   - [IoT Smart Grid sample v1.0](https://github.com/Microsoft/sql-server-samples/releases/tag/iot-smart-grid-v1.0) illustrates how SQL Server can be leveraged to ingest data from IoT devices and sensors, and how you can run analytics on that data.
 
 To see the complete list of resources in this repository, navigate to [Releases](https://github.com/Microsoft/sql-server-samples/releases)
+(this now includes an entity diagram of Northwind database) to help visual learners.
 
 ## Working in GitHub
-To work in GitHub, go to https://github.com/microsoft/sql-server-samples and fork the repository. Work in your own fork and when you are ready to submit to make a change or publish your sample for the first time, submit a pull request into the master branch of sql-server-samples. One of the approvers will review your request and accept or reject the pull request.
+To contribute on GitHub, follow these steps:
+
+- Visit https://github.com/microsoft/sql-server-samples and fork the repository.
+- Work in your forked repository.
+- When you're ready to make changes or publish your sample for the first time, submit a pull request into the 'master' branch of 'sql-server-samples'.
+- One of the approvers will review your request and either accept or reject the pull request.
 
 Each sample should be in its own folder with a README.md file that follows the [template](README_samples_template.md). Generated files (e.g., .exe or .bacpac) and user configuration settings (e.g., .user) should not be committed to GitHub.
 
 ## Cloning only a subset of the repo (with sparse checkout)
-You can follow the steps below to clone individual files from the sql-server-samples git repo. Note: The following script clones only the files under the **features** and **demos** folders. 
+You can follow the steps below to clone individual files from the sql-server-samples git repo. Note: The following script clones only the files under the **features** and **demos** folders.
 ```
 git clone -n https://github.com/Microsoft/sql-server-samples
 cd sql-server-samples

README_samples_template.md

@@ -59,7 +59,7 @@ To run this sample, you need the following prerequisites.
 
 2. In Visual Studio Build menu, select **Build Solution** (or Press F6).
 
-3. Step 3 ... 
+3. Step 3 ...
 
 <a name=sample-details></a>
 

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.7 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc).
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

composer.json

@@ -0,0 +1,17 @@
+{
+    "name": "microsoft/sql-server-samples",
+    "description": "Official Microsoft GitHub Repository containing code samples for SQL Server",
+    "type": "project",
+    "require": {
+        "php": ">=7.0.0"
+    },
+    "require-dev": {
+        "squizlabs/php_codesniffer": "^3.5"
+    },
+    "license": "MIT",
+    "minimum-stability": "stable",
+    "scripts": {
+        "cs-check": "phpcs -p --runtime-set ignore_errors_on_exit 1 --runtime-set ignore_warnings_on_exit 1",
+        "cs-fix": "phpcbf -p --runtime-set ignore_errors_on_exit 1 --runtime-set ignore_warnings_on_exit 1"
+    }
+}

media/demos/sql-sampledb/sampledb1/README.md

@@ -1,3 +1,3 @@
 # Sample Database 1 (Employee DB Dummy Data)
 
-This is a fundamental database that houses data based on a conventinal Sales environment. Sourced from progress.com with slight modifications.
+This is a fundamental database that houses data based on a conventional Sales environment. Sourced from progress.com with slight modifications.

media/demos/sql-sampledb/sampledb1/sampleDB1.sql

@@ -1,4 +1,4 @@
-/* 
+/*
 This is sourced from progress.com, variation by lightofodin.
 Basic database housing a sales scenario, that features employees and departments.
 */

phpcs.xml.dist

@@ -0,0 +1,52 @@
+<?xml version="1.0"?>
+<ruleset name="MS SQL Server Examples">
+    <description>The coding standard for MS SQL Server PHP Examples.</description>
+
+    <!-- Folders & files to be checked -->
+    <file>samples/tutorials/php</file>
+
+    <!-- File extensions to be checked -->
+    <arg name="extensions" value="php"/>
+
+    <!-- PSR-2 base standard -->
+    <rule ref="PSR2"/>
+
+    <!-- Disable code style sniff on side effects -->
+    <rule ref="PSR1">
+        <exclude name="PSR1.Files.SideEffects"/>
+    </rule>
+
+    <!-- General sniffs -->
+    <rule ref="Generic.Files.LineLength"/>
+    <rule ref="Squiz.Arrays.ArrayBracketSpacing"/>
+    <rule ref="Squiz.Commenting.FunctionCommentThrowTag"/>
+    <rule ref="Squiz.Classes.LowercaseClassKeywords"/>
+    <rule ref="Generic.CodeAnalysis.ForLoopShouldBeWhileLoop"/>
+    <rule ref="Generic.CodeAnalysis.ForLoopWithTestFunctionCall"/>
+    <rule ref="Generic.CodeAnalysis.JumbledIncrementer"/>
+    <rule ref="Generic.CodeAnalysis.UnconditionalIfStatement"/>
+    <rule ref="Generic.CodeAnalysis.UnnecessaryFinalModifier"/>
+    <rule ref="Squiz.Commenting.DocCommentAlignment"/>
+    <rule ref="Generic.Formatting.NoSpaceAfterCast"/>
+    <rule ref="Squiz.Operators.ValidLogicalOperators"/>
+    <rule ref="Generic.PHP.DeprecatedFunctions"/>
+    <rule ref="Squiz.PHP.DisallowSizeFunctionsInLoops"/>
+    <rule ref="Squiz.PHP.Eval"/>
+    <rule ref="Generic.PHP.ForbiddenFunctions"/>
+    <rule ref="Squiz.PHP.NonExecutableCode"/>
+    <rule ref="Squiz.Classes.ClassFileName"/>
+    <rule ref="Squiz.Scope.MemberVarScope"/>
+    <rule ref="Squiz.Scope.StaticThisUsage"/>
+    <rule ref="Squiz.WhiteSpace.CastSpacing"/>
+    <rule ref="Squiz.WhiteSpace.LanguageConstructSpacing"/>
+    <rule ref="Squiz.WhiteSpace.LogicalOperatorSpacing"/>
+    <rule ref="Squiz.WhiteSpace.SemicolonSpacing"/>
+    <rule ref="Squiz.WhiteSpace.SuperfluousWhitespace"/>
+    <rule ref="Squiz.WhiteSpace.ScopeClosingBrace"/>
+    <rule ref="Squiz.Functions.FunctionDeclarationArgumentSpacing">
+        <properties>
+            <property name="equalsSpacing" value="1"/>
+        </properties>
+    </rule>
+
+</ruleset>

samples/applications/azure-data-studio/README.md

@@ -0,0 +1,65 @@
+<!-- Always leave the MS logo -->
+![](./media/solutions-microsoft-logo-small.png)
+
+# Azure Data Studio Notebook Samples
+
+Helpful notebooks for troubleshooting and new features in Azure Data Studio.
+
+
+### Contents
+
+[About this sample](#about-this-sample)<br/>
+[Before you begin](#before-you-begin)<br/>
+[Run this sample](#run-this-sample)<br/>
+[Sample details](#sample-details)<br/>
+[Related links](#related-links)<br/>
+
+
+<a name=about-this-sample></a>
+
+## About this sample
+
+<!-- Delete the ones that don't apply -->
+- **Applies to:** Azure Data Studio
+- **Key features:** Notebook Samples
+- **Programming Language:** SQL & Python Notebooks
+- **Authors:** Vasu Bhog [vabhog]
+
+<a name=before-you-begin></a>
+
+## Before you begin
+
+To run this sample, you need the following prerequisites.
+
+**Software prerequisites:**
+
+<!-- Examples -->
+1. Azure Data Studio 1.30.0
+2. Python
+
+
+## Run this sample
+
+<!-- Step by step instructions. Here's a few examples -->
+
+For Parameterization.ipynb Sample:
+1. From Azure Data Studio, open the **Notebook** file.
+2. Follow docs for paremeteization [here](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/parameterize-papermill).
+
+
+## Sample details
+
+This Notebook allows users to follow along the docs as well as use a already parameterized notebook.
+
+## Related Links
+<!-- Links to more articles. Remember to delete "en-us" from the link path. -->
+
+For more information, see these articles:
+* [Notebooks Overview](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/notebooks-guidance)
+* [SQL Kernel](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/notebooks-sql-kernel)
+* [Python Kernel](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/notebooks-python-kernel)
+* [Kusto Kernel](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/notebooks-kusto-kernel)
+* [KqlMagic](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/notebooks-kqlmagic)
+* [Papermill Parameterization](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/parameterize-papermill)
+* [URI Parameterization](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/parameterize-uri)
+* [Run with Parameters](https://docs.microsoft.com/en-us/sql/azure-data-studio/notebooks/run-with-parameters)