Alteryx Server Implementation case studies
Alteryx Server Implementation · Put your knowledge to work in context.
The Alteryx Server Implementation credential is aimed at administrators and platform engineers who install, secure, and operate an Alteryx Server environment rather than build workflows alone. It validates that you can plan a deployment that matches an organization's topology and governance needs, stand the platform up correctly, control who can publish and run what, and keep scheduled jobs and the underlying services healthy over time. The Alteryx Server Implementation case studies are 5 cases and about 2,016 words.
1Sizing a Second Worker Node for a Burst-Prone Gallery
A company runs Alteryx Server with a single Worker node (16 vCPU, 64 GB RAM) and a separate Controller. Overnight batches of 40 workflows run between 01:00 and 05:00; daytime users run ad hoc workflows that finish in under 2 minutes.
446 words, about 2 min2Windows Authentication Rollout Across a Distributed Server
An organization is deploying Alteryx Server across a Controller, two Workers, and a separate Gallery/MongoDB host, all domain-joined Windows servers. The security team wants users to log into the Gallery with their Active Directory credentials (single sign-on) and wants workflow run-as credentials to use a dedicated service account rather than the logged-in user.
417 words, about 2 min3Scheduling Failures After a Database Host Migration
After migrating the Alteryx Server MongoDB and the Controller's persistence to a new host, the team finds that scheduled workflows no longer fire. Manual runs from the Gallery succeed.
408 words, about 2 min4Gallery Permissions for a Shared Workflow Collection
A data team publishes 60 workflows to a Gallery collection used by three departments. Today everyone in the company has Viewer access to the collection, and Artisans in each department can edit any workflow.
361 words, about 2 min5Diagnosing Slow Gallery Response Under Load
A Gallery host (8 vCPU, 32 GB RAM) serving 300 users becomes sluggish every weekday between 09:00 and 11:00. Page loads take 8-12 seconds, and users report timeouts when opening large workflow results.
384 words, about 2 min