MigsLab SDKARX.SDK documentation
Ctrl K

Providers

SQL Server

Using ARX.SDK with SQL Server: every page below comes from a sample that was built and run.

ARX.SDK.SQL

Start here

Get startedThe .NET SDK, a new project, the packages, the database and its sample schema, and the connection string: once, before any sample.The sample applicationThe few files the samples share: the application's service and catalog, output, read-back. Progressive samples build on them.TypesThe ARX types an application uses, grouped by purpose, with the samples that use each one.Supported data typesWhat each .NET type is stored as, and what each SQL Server type reads back as.

Operations

Create24 samples · 24 verified against SQL ServerCreateMultiple7 samples · 7 verified against SQL ServerUpdate13 samples · 13 verified against SQL ServerUpdateMultiple6 samples · 6 verified against SQL ServerDelete12 samples · 12 verified against SQL ServerDeleteMultiple5 samples · 5 verified against SQL ServerRetrieve6 samples · 6 verified against SQL ServerRetrieveMultiple22 samples · 22 verified against SQL ServerExecute17 samples · 17 verified against SQL Server

How to read a sample page

  • Standalone: every file the sample needs is on its page. Copy them into a new project and run it.
  • Progressive: builds on the sample application: add those files once, then the sample's own.
  • Advanced: a complete workflow, with every file and package it needs on its page.
  • Each scenario ends with a query to check what it did in the database (SQL, mongosh for MongoDB, PartiQL for DynamoDB), ready to copy.