.\sqlsim\x64\sqlsim.exe --version .\sqlsim\x64\sqlsim.exe -h #41

Activity

1. GUIBLAR#sqens (poiraudauguillaume140-prog)

   added

   preview-requestRequest for Private Preview accessRequest for Private Preview access

   on Oct 17, 2026
2. Bob Ward (rgward)

   closed this as completedin #45on Oct 20, 2026
3. Bob Ward (rgward)

   reopened this on Oct 20, 2026
4. rgward commented on Oct 20, 2026

   

   Bob Ward (rgward)

   on Oct 20, 2026

   Member

   More actions

   GUIBLAR#sqens (@poiraudauguillaume140-prog) - thanks for offering to test Studio on Ubuntu x64 and Windows ARM64. The same maintained tester-kit approach used for our macOS preview is now available for both platforms.

   Private Preview - testing only

   These platforms remain experimental and unsupported for production. Please use this existing request issue for preview testing assistance and feedback; no new request is needed. Anyone else seeking preview testing assistance should open a Private Preview request. This is not a production-support commitment.

   PR #45 is merged. These packages were built from main, commit 767dba350d19a836343e0e82620a30778b6b4ec7, and are separate from public release assets. No public release or tag was created.

   Download and choose your platform

   Download the validated Private Preview tester kits while signed into GitHub. This Actions artifact expires January 18, 2027. Private Preview describes the testing stage, not confidential or access-restricted downloads.

   Extract the outer download ZIP, then choose:

   Your machine	Subfolder	Kit archive
   Ubuntu 24.04 or 26.04 LTS x64	studio-preview-input-linux-x64	sqlsimstudio-linux-x64-private-preview-tester-kit.tar.gz
   Windows 11 ARM64	studio-preview-input-win-arm64	sqlsimstudio-win-arm64-private-preview-tester-kit.zip

   Windows ARM64 is not Intel/AMD Windows x64. Each kit includes Studio, matching native sqlsim, sqlpysim, examples, manuals, the canonical Studio test suites, and a reporting runner. No source checkout, compiler, or .NET installation is needed.

   Before extracting the selected kit, verify it against the accompanying SHA256SUMS: on Ubuntu run sha256sum -c SHA256SUMS from that platform subfolder; on Windows compare Get-FileHash .\sqlsimstudio-win-arm64-private-preview-tester-kit.zip -Algorithm SHA256 with Get-Content .\SHA256SUMS. Stop if the hash differs. Extract the verified kit into a new writable folder, without mixing files from other builds.

   Full setup, launch, live-test and reporting guide for this exact build. The same guide is included as the kit's root README.

   Start with the offline checks

   Run these from the extracted kit root, not the outer download folder.

   Ubuntu 24.04/26.04 x64

   Install PowerShell 7 using Microsoft's Ubuntu instructions, then:

   sudo apt-get update
   sudo apt-get install -y python3 python3-venv unixodbc libltdl7 libkrb5-3 libgssapi-krb5-2
   python3 -m venv .venv
   source .venv/bin/activate
   python -m pip install -r ./sqlsimstudio/sqlpysim/requirements.txt
   pwsh -NoProfile -File ./run-tests.ps1 -Tier Offline -Python python

   Windows 11 ARM64

   Install native ARM64 PowerShell 7 and native ARM64 Python 3.11 or later, not their emulated x64 versions. In ARM64 PowerShell:

   python -m venv .venv
   .\.venv\Scripts\python.exe -m pip install -r .\sqlsimstudio\sqlpysim\requirements.txt
   pwsh -NoProfile -File .\run-tests.ps1 -Tier Offline -Python .\.venv\Scripts\python.exe

   These checks do not require a SQL target. On the merged-main build, all seven checks passed on native Windows ARM64 and Ubuntu 24.04, and the same Linux archive, unchanged, passed on Ubuntu 26.04. Each platform's Studio suite reported 75 passed, 0 failed, 4 live-only skips. Both archive checksums were also verified in CI. That establishes repeatable offline validation, not live SQL, clean-machine installation, signing, or real-browser readiness.

   Then try a small Studio run

   For live native-engine use, install Microsoft ODBC Driver 18 matching your OS and architecture; Windows ARM64 needs the ARM64 driver. The included guide links the Linux installation instructions too.

   Launch from the extracted kit root:

   • Ubuntu: keep the virtual environment active and run ./sqlsimstudio/sqlsimstudio.
   • Windows ARM64: select the venv Python, then launch:

   $env:SQLSIM_STUDIO_PYTHON_PATH = (Resolve-Path .\.venv\Scripts\python.exe).Path
   .\sqlsimstudio\sqlsimstudio.exe

   If Windows blocks an unsigned executable, stop and report the exact message. Do not disable SmartScreen, antivirus, or other security controls.

   Use a dedicated non-production database you are authorized to test. Start with connection and SELECT 1, one thread and one iteration, then results, a small included example, and cancellation. Try both engines if convenient. On Ubuntu, start with a database access token rather than interactive Entra authentication. You do not need to cover every SQL product/authentication option in your first response.

   For the help/version checks in your request, this kit's Windows engine is .\sqlsimstudio\sqlsim\sqlsim.exe, not the sqlsim\x64 layout. Run --version or -h separately. On Ubuntu it is ./sqlsimstudio/sqlsim/sqlsim, with --version or --help.

   The optional smoke/full suites are not required for initial feedback. They generate load and can create/drop test objects; the runner requires explicit live/load consent and credential files. Follow the included guide rather than placing passwords/tokens in command-line arguments. Use Studio's Shut down control when finished.

   Reply here with results

   Please include hardware/chip, OS version, browser, build commit, engine, test tier, SQL product/version and authentication mode, plus what passed, failed or skipped. The runner writes results/<timestamp>-<id>/results.json and separate logs; it uploads nothing automatically.

   Review and sanitize anything you share: no passwords, tokens, private hostnames, credential-bearing connection strings, SQL/customer data, or result rows. Sanitized error text and report/log excerpts are helpful.

   We will keep this request open for feedback. Maintainers own the native build/offline gates and the remaining live, installation, browser and promotion work; your testing supplements those responsibilities rather than replacing them.