https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-ps-module
Fix for error: Microsoft.SqlServer.Management.Dmf.PolicyEvaluationException: Exception encountered while executing policy Table Name Pattern. ---> Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Arithmetic overflow error for data type tinyint, value = -1.<?char 13?> The statement has been terminated.<?char 13?>
* wwi revision from Robert Cain
* added .sln files
* adding publish.xml files for ssdt projects
* correct DB names in publish.xml
* renaming project names to align with DB names
* removing redundant config procs from OLAP DB; adding version table
* moving full-text indexing to post-deployment script
* updated SampleVersion, and added version to post-deployment script
* aligning start date with v1 start date
* reduce rowcount to accomodate low-end systems
* fixing T-SQL syntax error
* fixing T-SQL syntax issue
* aligning naming of SSIS package with v1
* update RLS sample to work with v2 of wwi
City IDs are no longer hard-coded
* updating DB names for SSIS
* aligning publish name with DB name
* updating DB settings
* aligning DB name
* improved perf for coldroomtemperature
Improved process, such that all data for a given day is generated as a
single native proc execution, which accumulates the data in a
non-durable table. this data is then bulk-moved to the archive table,
before adding the most recent data to the current table.
* aligning names of memory_optimized_data filegroups
* updated filegroups in project files
* commenting ApplyPolyBased from post-deployment
deployment of the SSDT project should not fail if connection with the
Azure storage account cannot be established. Therefore, applying the
PolyBase piece to the sample DB is something the user needs to do after
deploying the DB.
* removing ApplyPolybase from post-deployment
* aligning DB set options
* cleaning up FTS artifacts
* aligning data source name
* facilitating publication to azure
- removing explicit filegroup references from index definitions
- adding snapshot hints to references for memory-optimized tables, to
facilicate publication in DBs without the
MEMORY_OPTIMIZED_ELEVATE_TO_SNAPSHOT hint
* initial updated docs for OLTP DB
* initial documentation for WideWorldsImportersDW
* docs for SSIS package
* initial documentation for SSASMD project
* Update README.md
* Update README.md
* Update README.md
* Update README.md
* Update README.md
* adding Azure SQL DB sections to docs
* Update README.md
* Update README.md
* cleaning up local solution files
- cleaning up bad references in local solution files
- calling out SSAS and SSIS dependencies more explicitly in the READMEs
* replacing inner join to BuyingGroups with LEFT JOIN
Fixing logical error in the integration proc. Not all customers are in
buying groups.
* removing redundant reference to release
* correction around Azure deployment
* corrections around Azure deployment
* Update README.md
* Update README.md
* Update README.md
* clarified how 2012 data is generates
* Update README.md
* minor updates
* implementing PR comments
* Update README.md
* Update README.md
* clarifying VS2017 caveats
* adding caveat for VS2017
* caveat for VS2017
* removing stale file reference
* removing stale folder
* adding DB option to post-deployment scripts for Azure SQL DB purposes
* fixes for migration Azure SQL Premium->Standard
* fixes for enabling/disabling In-Memory OLTP
* renaming to avoid confusion
* aligning project structure with best practice - aligning SSAS DB name with others
Sergio Fonseca
Jovan Popovic
Barbara Kess
Pedro Lopes
sabotta
Jos de Bruijn
Umachandar Jayachandran
nelgson
Mihaela Blendea
Mihaela Blendea
Estienne Granet
Bob Ward
Bader Nasser
Yasuhiro Matsumoto
Brett Cannon
Perry Skountrianos - MSFT