Private Preview request: #24

Activity

1. Joey D'Antoni (jdanton)

   added

   preview-requestRequest for Private Preview accessRequest for Private Preview access

   on Oct 14, 2026
2. rgward commented on Oct 20, 2026

   

   Bob Ward (rgward)

   on Oct 20, 2026

   Last edited by rgward

   Member

   More actions

   Hi Joey D'Antoni (@jdanton) - thank you for volunteering! The first macOS ARM64 Private Preview candidate is ready to try.

   You requested sqlpysim on macOS, particularly Azure SQL/Entra. That is the suggested starting point below. The kit also includes sqlsim and Studio if you want to try them, but they are optional; the Python-only offline command does not start either native tool.

   Download and unpack

   • Download the builds and tester kit (sign in to GitHub to download).
   • Apple Silicon, macOS 15 or later. These are unsupported Private Preview builds, not a supported macOS release.
   • Built from main after Build and validate maintained macOS ARM64 preview tester kits #44 merged. Candidate commit: 4702a27034203f94a5e763b57f6099d4097578ab. Successful Apple Silicon build and validation.
   • This Actions download expires January 18, 2027. Reply here if you need a replacement link.

   Unzip the download first. It contains three individual tool archives, SHA256SUMS, BUILD-INFO.txt, and sqlsimtools-macos-arm64-tester-kit.tar.gz.

   Use the tester kit: it already contains all three tools, examples, documentation, and the maintained test suites. You do not need to extract the three individual tool archives as well. From the unzipped download directory:

   shasum -a 256 -c SHA256SUMS

   Stop if any checksum fails. Then extract into a new, empty directory:

   mkdir sqlsimtools-macos-preview &&
   tar -xzf sqlsimtools-macos-arm64-tester-kit.tar.gz -C sqlsimtools-macos-preview &&
   cd sqlsimtools-macos-preview

   Setup and offline checks

   Follow the kit's root README.md (same instructions online). From the extracted kit root:

   brew install powershell [email protected] openssl coreutils jq
   python3.11 -m venv .venv
   source .venv/bin/activate
   python -m pip install -r ./sqlpysim/requirements.txt

   For sqlsim or Studio, also follow the included sqlsim/MACOS-PRIVATE-PREVIEW.md (ODBC/runtime installation instructions) before testing. Python-only testing does not require installing the native tool's ODBC dependencies.

   With that Python environment activated:

   pwsh -NoProfile -File ./run-tests.ps1 -Tier Offline -Tool sqlpysim -Python python

   These checks do not use your SQL target. This exact extracted kit passed all seven automated offline checks on Apple Silicon, including Studio's full offline suite (75 passed, 0 failed; four live-only tests skipped). That does not establish live SQL connectivity or installation/browser behavior on your Mac.

   Try a small live example, if convenient

   Only use a dedicated, non-production database you are authorized to test. Start with SELECT 1, one thread, and one iteration; then try an included example before increasing concurrency.

   Start with the Azure SQL access-token example in the included sqlpysim/MACOS-PRIVATE-PREVIEW.md (first-query instructions), then try an example under sqlpysim/examples/. The same guide covers SQL authentication for a non-production SQL Server if you also want to test that path. If you choose the optional smoke suite, select -Tool sqlpysim and follow the root README token-file example.

   For Azure SQL/Entra, start with an access token, not interactive Entra authentication on macOS. The packaged guides show token/password handling through stdin; the test runner accepts credential files. Never put the secret itself in process arguments or an issue.

   The root README also explains the optional smoke/full suites. They are not required for initial feedback: even native smoke includes a 100-thread test, and full suites can create/drop test objects and generate substantial load. Live/load runs require explicit consent flags.

   These binaries are not Developer ID signed or notarized. If macOS blocks a launch, stop and report the exact message; please do not disable Gatekeeper or remove quarantine recursively.

   Reply here with feedback

   Even an installation failure or a successful offline run is useful. Please include:

   • Mac chip, macOS version, and build commit.
   • Tool/engine tested; browser/version if using Studio.
   • SQL target product/version and authentication mode, if tested.
   • What passed, failed, or was skipped, plus sanitized reproduction steps.
   • Sanitized results/<run>/results.json and relevant log excerpts, if available.

   The kit uploads nothing automatically. Review reports before sharing: remove private hostnames, credentials, tokens, credential-bearing connection strings, SQL/customer data, and result rows. Report security vulnerabilities privately via the security policy.

   Private Preview - testing only. To request participation or preview testing assistance, open a Private Preview request. You already have one: please keep feedback and assistance requests in this issue. These builds do not include production support. Thank you!