Added a table required to demo LOB support in CLUSTERE COLUMNSOTRE INDEXes.
Scenario is application logging. Applicaiton pushes log events that have large descriptions into the LOB column in CCI table. Table is compliant wiht Serilog logger for .Net and can be direclty used as a target for MSSQL Serilog sink:
In applicaition should be added the following changes to integrate serilog:
1. Download Serilog and Serilog.MSSQL.sink NuGet packages
2. Add the following packages:
using Serilog;
using Serilog.Sinks.MSSqlServer;
3. Configure logger:
var columnOptions = new Serilog.Sinks.MSSqlServer.ColumnOptions();
// Don't include the Properties XML column.
columnOptions.Store.Remove(StandardColumn.Properties);
columnOptions.Store.Remove(StandardColumn.MessageTemplate);
columnOptions.Store.Remove(StandardColumn.Exception);
// Do include the log event data as JSON.
columnOptions.Store.Add(StandardColumn.LogEvent);
var logger = new LoggerConfiguration()
.WriteTo
.MSSqlServer( ConnString, "Logs", schemaName: "Application",
autoCreateSqlTable: false,
columnOptions: columnOptions
)
.CreateLogger());
4. Log events:
var position = new { Latitude = 25, Longitude = 134 };
var elapsedMs = 34;
log.Information("Processed {@Position} in {Elapsed:000} ms.", position, elapsedMs);
log.Error(new IndexOutOfRangeException("Test"), "Error while processing {@Position} in {Elapsed:000} ms.", position, elapsedMs);
* Added WWI Website views and procedures
Added new views and procedures for WWI WebSite:
1. Views that expose main entities
2. Create, Update, and Delete procedures for WWI tables.
* Added Website views/proc into sql project
* Refactored Web APi procedures and views
* Update DeleteStateProvince.sql
* Fixing style on views
Added quoted identifiers everywhere.
* Added quoted identifiers on WebApi views
* Removed refactor log from project
* Addressing UC's comment
changed INSERTED to inserted
SearchForStockItems uses correct view in webApi schema
* Removed unnesecary alias in SalesOrders view
* Fixed bugs in SpecialDeals and Customers
Added columns in customers view.
Changed parameter name in SpecialDeals procedure.
* Added quoted identifier_on in insert customer/supplier transactions and missing columns in purchase order lines view.
* Added row-level security
* Added wrapper views for some simple entities.
* Added missing fields in suppliers view/procedure
* Handled NULL columns and some missing columns in views.
* Removed useless quoted identifier on
* Changed quoted identifier on two update customer/supplier transactions stored procedures.
Added changes required to run Automatic tuning FLGP demo in WWI database.
1. Added new package type "Unknown" for one order line
2. Added one order line in the "Unknown" package
3. Updated AT demo script to work with WWI database.
4. Included PackageTypeID column in NCCI on OrderLines table.
Minor
1. Added .gitignore file for the local folder
2. Updated UI page for AT demo.
* 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