github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity
Files
05270ad82c33cd67bc3c7e4fd10dc9158267b0bc
sql-server-samples/samples/databases/wide-world-importers/wwi-ssasmd
History
Jos de Bruijn efa54273da Wwi update (#257) 
* 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
2017-06-29 14:47:18 -07:00
..
wwi-ssasmd
Wwi update (#257)
2017-06-29 14:47:18 -07:00
README.md
Wwi update (#255)
2017-06-28 14:48:06 -07:00
wwi-ssasmd.sln
Wwi update (#257)
2017-06-29 14:47:18 -07:00

README.md

SSAS Multidimensional Project for WideWorldImporters

This is the SQL Services Analysis Services (SSASMD) project for the analytics database WideWorldImportersDW. It creates Analysis Services cubes based on the WideWorldImportersDW schema, and can be used to run MDX queries against the WideWorldImporters data.

Contents

About this sample
Before you begin
Running the sample
Sample details
Disclaimers
Related links

About this sample

  1. Applies to: SQL Server 2016 (or higher)
  2. Key features: Analysis Services Multidimensional
  3. Workload: Analytics
  4. Programming Language:
  5. Authors: Robert Cain, Jos de Bruijn
  6. Update history: 21 June 2017 - initial revision

Before you begin

To run this sample, you need the following prerequisites.

Software prerequisites:

  1. SQL Server 2016 (or higher) with the database WideWorldImportersDW.
  2. Visual Studio 2015 Update 3 or higher. If you are using Visual Studio 2017, download and install the following: Analysis Services
  3. SQL Server 2016 (or higher) Analysis Services.
    1. This needs to be installed on the same machine as Visual Studio to be able to build the project.

Running the sample

  1. Open the solution file wwi-ssasmd.sln in Visual Studio.

  2. Build the solution.

  3. Make sure you have permission on the SSAS server. From SQL Server Management Studio:

    1. Connect to the Analysis Services server.
    2. In Object Explorer, right-click on the server and select Properties to open the properties dialog.
    3. Click on Security to navigate to the security page.
    4. Verify that you are listed among server administrators. If not, click Add to add your account to the server administrators.

  4. Publish the SSASMD database:

    1. In Solution Explorer, open the project WWI-SSASMD, and open the Data Source node.
    2. Double-click the data source WideWorldImportersDW.ds to open the Data Source Designer.
    3. Click Edit to update the connection string to point to the server that has the existing WideWorldImportersDW database, and verify that the database name is WideWorldImportersDW.
    4. Click Impersonation Information -> Use a specific Windows user name and password, and fill in you user name and password.
    5. Click Ok to close the dialog.
    6. Right-click the WWI-SSASMD project and select Properties to open the properties dialog.
    7. Click on Deployment to open the deployment properties.
    8. Update the target server to point to the Analysis Services server, and click Ok.
    9. Right-click the WWI-SSASMD project and select Deploy to deploy the Analysis Services database.

Sample details

TBD

Disclaimers

The code included in this sample is not intended to be used for production purposes.

Related Links

For more information, see these articles: