Architecture, schema & metadata design
Review attributes, facts, relationships and reusable metrics to build a consistent semantic layer.
Solution Primary · Consulting
MicroStrategy consulting
Make enterprise analytics faster, more consistent and easier to maintain. We support MicroStrategy implementations on AWS, Azure, Google Cloud and on-premises infrastructure, including SAML 2.0 single sign-on (SSO) integration with your enterprise identity provider. Automate code and object migrations, Intelligent Cube refreshes, user management and routine administration with workflows your team can monitor and maintain. We also help assess emerging container-based approaches where appropriate.
- MicroStrategy ONE
- Dossier
- HyperIntelligence
- CLS
- SAML 2.0 SSO
- Automation
Where we can help
When the platform needs a clearer next step.
- Reports take too long to run and tuning has become trial and error.
- A platform upgrade needs a clear compatibility, testing and rollout plan.
- Metrics differ across reports because schema and metadata have grown without consistent standards.
- Users need enterprise single sign-on, or existing SAML logins fail after identity-provider or certificate changes.
- Manual object promotions, cube refreshes and user administration create repetitive work and inconsistent outcomes.
Services
Hands-on support, from design to delivery.
Upgrades to MicroStrategy ONE & cloud
Plan upgrades across on-premises, AWS, Azure or Google Cloud environments with dependency checks, validation and a practical cutover approach. Assess container-based modernisation separately against release support and operational readiness.
Dossier, mobile & HyperIntelligence
Build dossiers, mobile experiences and contextual analytics around the decisions users need to make.
Performance tuning & VLDB optimisation
Investigate SQL generation, database workloads and VLDB settings to address performance bottlenecks.
SAML 2.0 SSO integration & troubleshooting
Assess SAML 2.0 support for your exact MicroStrategy release and deployment, then plan integration with identity providers such as Microsoft Entra ID, Okta or ADFS where supported. Configure metadata, entity IDs, assertion consumer service URLs, signing certificates and identity mapping; validate sign-in flows and troubleshoot assertion, redirect and certificate errors. Authentication does not replace MicroStrategy permissions: review access separately and document certificate renewal and operational handover.
Code & object migration automation
Build repeatable code and metadata-object promotion workflows between development, test and production. Include dependency checks, migration packages, approval gates, post-migration validation and rollback planning; integrate with existing release pipelines using tooling supported by your MicroStrategy version.
Intelligent Cube refresh automation
Automate Intelligent Cube publishing and refresh workflows around data-load completion or agreed schedules. Define full or incremental refresh strategies where supported, coordinate dependencies, monitor job results and add controlled retries and failure alerts so stale data is visible to operations teams.
User management & administration automation
Automate approved user provisioning and deactivation, group membership updates and access reviews while preserving least-privilege controls and audit trails. Extend workflows to related tasks such as subscription scheduling, cache maintenance, job monitoring and administration reporting, using supported REST APIs or Command Manager where available for your release and deployment. Document service-account access, credential handling and operational ownership.
MicroStrategy automation · Delivery scope
What we automate, how we deliver, what you retain.
Begin with a focused pilot, validate it in non-production and extend only after acceptance. Tools and supported operations are checked against your exact release, licensing and hosting model; scope and deliverables are agreed for your engagement.
Code & object migration automation
- Scope & prerequisites
- Inventory reports, dossiers, metrics, attributes, facts and dependent objects. Agree development, test and production mappings, conflict handling and which environment-specific settings must remain unchanged. Database schema changes and platform upgrades are separate scopes unless agreed.
- Implementation & validation
- Prepare supported migration packages and repeatable promotion workflows. Connect approval gates to your existing release process, log promoted objects and validate report outputs and dependencies in the target environment. Rehearse rollback before production cutover.
- Handover & ownership
- Migration workflow definitions, configuration guidance, object manifests, validation evidence and release/rollback runbooks, with a named release owner.
Intelligent Cube refresh automation
- Scope & prerequisites
- Review cube sizes, source-load completion signals, refresh durations, reporting deadlines and available capacity. Select full or incremental refreshes only where supported and agree how late or incomplete source data should be handled.
- Implementation & validation
- Sequence publishing and refresh jobs using agreed schedules or data-ready triggers. Prevent overlapping runs where required, capture job status and freshness timestamps, reconcile data and route failures to operations with bounded retries and recovery steps.
- Handover & ownership
- Refresh dependency map, scheduler or orchestration configuration, monitoring and alert guidance, data-validation checks and an operational recovery runbook.
User management & administration automation
- Scope & prerequisites
- Map approved joiner, mover and leaver requests to accounts, groups and access entitlements. Identify the authoritative identity source, approval owners and account exceptions; agree deactivation versus deletion and retention requirements before making changes.
- Implementation & validation
- Implement supported provisioning and membership workflows with least-privilege service accounts. Add a preview or review step for bulk changes where feasible, handle repeat requests safely and test both allowed and denied access. Record failures for human review; keep SSO authentication separate from application permissions.
- Handover & ownership
- Account-lifecycle workflows, approved group mappings, audit records, exception-handling guidance and credential-renewal procedures, with clear identity and BI administration ownership.
Related tasks can include subscription scheduling, cache maintenance, job monitoring and administration reporting when explicitly scoped. Production changes follow your approved change process; credentials stay in approved secrets management, not in scripts or enquiry forms.
Request an automation consultationAutomation project stories · Illustrative
From repetitive administration to controlled workflows.
Three hypothetical MicroStrategy automation scenarios covering code migration, cube refresh and user management. These are not client case studies or measured results; each shows proposed work, validation and intended outcomes. Tooling depends on release and deployment support.
MicroStrategy automation FAQs
Scope, delivery and operational handover.
Common questions about code migration, Intelligent Cube refresh and user-management automation engagements.
Deployment landscape
Established environments. A practical path forward.
Cloud & on-premises implementations
AWS, Azure, Google Cloud and on-premises deployments remain central to our MicroStrategy consulting scope. We focus on reliable installation, enterprise reporting, upgrades and performance within your existing environment.
Emerging container-based approaches
OpenShift and similar Kubernetes platforms are an evolving modernisation path, not a required next step for every implementation. We assess business value, team readiness and release-specific vendor support before recommending a change.
Hosting location, cloud ownership and deployment architecture are separate decisions. An existing customer-managed cloud or on-premises installation is not automatically the vendor’s containerised CMC offering.
MicroStrategy · Architecture comparison
Four deployment views. Different operating foundations.
Illustrative, simplified reference diagrams—not client architectures or installation blueprints. Arrows show logical access and connectivity, not network rules. Identity, monitoring, backups and security controls apply across every design.
AWS
Established deployment approach
Users · Browser / mobile / tools
AWS account · VPC
HTTPS · Load balancer
EC2 / virtual machines
MicroStrategy services
Web / Library · Intelligence · Semantic layer
Metadata repository + analytics sources
Data sources may be outside the illustrated boundary; metadata, analytics databases and storage have distinct roles.
MicroStrategy application services on cloud compute, with approved database connectivity. Analytics sources may include Redshift, supported databases or external systems.
- Operations owner
- Customer / agreed operating partner
- Design checks
- Network isolation, sizing, database compatibility and recovery planning.
Other cloud
Established deployment approach
Users · Browser / mobile / tools
Azure / Google Cloud · Private network
HTTPS · Load balancer
Azure VMs / Compute Engine
MicroStrategy services
Web / Library · Intelligence · Semantic layer
Metadata repository + analytics sources
Data sources may be outside the illustrated boundary; metadata, analytics databases and storage have distinct roles.
A similar application architecture on Azure or Google Cloud, using provider-specific networking and compute. Connect supported analytics sources through approved drivers.
- Operations owner
- Customer / agreed operating partner
- Design checks
- Provider-specific services, data connectivity, supported operating systems and databases.
On-premises
Established deployment approach
Users · Browser / mobile / tools
Customer data centre · Private network
HTTPS · Reverse proxy / load balancer
Physical servers / virtual machines
MicroStrategy services
Web / Library · Intelligence · Semantic layer
Metadata repository + enterprise data sources
Data sources may be outside the illustrated boundary; metadata, analytics databases and storage have distinct roles.
Application services run on customer-owned infrastructure, with connections to internal data warehouses and approved remote sources.
- Operations owner
- Customer infrastructure and BI teams
- Design checks
- Hardware capacity, high availability, backups, patching and secure remote access.
OpenShift
Emerging option · Support validation required
Users · Browser / mobile / tools
Customer infrastructure · OpenShift cluster
HTTPS · Ingress / routing
Operator-managed container workloads
Containerised analytics services
Web / Library · Intelligence · Semantic layer
Persistent storage + approved databases / sources
Data sources may be outside the illustrated boundary; metadata, analytics databases and storage have distinct roles.
Conceptual CMC-style architecture on a customer-controlled Kubernetes platform. OpenShift can run on cloud or on-premises infrastructure; it is not another cloud provider.
- Operations owner
- Customer platform and analytics teams
- Design checks
- Confirm vendor-supported release, operator, packaging, storage and OpenShift compatibility before implementation.
These views compare deployment foundations, not CMC versus SaaS contracts. Fully hosted SaaS changes the operating responsibility; cloud-hosted virtual machines are not automatically the vendor’s containerised CMC offering.
MicroStrategy · Requirements assessment
Your deployment requirements
Cloud, on-premises or an emerging OpenShift architecture: start with your hosting policies, data and operating capacity.
An architecture that fits your constraints.
Established cloud and on-premises options remain the starting point. OpenShift requires a clear business case and release-specific support.
Indicative assessment, not vendor certification or a compliance approval. Support confirmations are client-reported and need evidence. Answers are not saved or submitted. Analytics records assessment starts, completions and recommendation categories, not your answers or release description.
MicroStrategy ONE · Decision guide
Which cloud model fits your team?
Control, capability and priorities.
The right fit depends on your hosting requirements and who will run the environment. Both models retain customer responsibilities for data and access.
Indicative guidance, not a compliance assessment or a vendor support guarantee. Confirm release compatibility, service scope and total cost. Answers stay on this page and are not submitted.
MicroStrategy ONE · Cloud deployment options
Customer Managed Cloud or fully hosted SaaS?
MicroStrategy ONE’s enterprise analytics and semantic graph can support different cloud operating models. The key decision is who operates the platform—not simply where it runs. Current vendor documentation uses the Strategy name.
Consideration
Customer Managed Cloud (CMC)
Fully hosted SaaS
Hosting & control
Customer Managed Cloud
Runs within your organisation’s own public cloud or private infrastructure. Your team controls the environment and its infrastructure boundaries.
Fully hosted SaaS
Vendor-hosted SaaS: Strategy oversees the underlying cloud infrastructure, while your organisation retains control of its application and data.
Operations & maintenance
Customer Managed Cloud
Your team manages the application and surrounding infrastructure, including capacity, monitoring, maintenance and deployment of updates. Strategy supplies deployment artifacts and support under the agreed service scope.
Fully hosted SaaS
Infrastructure operations are handled by the vendor under the service agreement. Your team still owns reporting, data integration, user administration and agreed application responsibilities.
Security responsibilities
Customer Managed Cloud
Your organisation manages infrastructure security, network policies, access, encryption and incident response within its environment. Responsibilities are agreed with the vendor.
Fully hosted SaaS
A shared-responsibility model: the vendor manages its hosted infrastructure controls; your team remains responsible for data governance, identities, permissions and secure configuration.
Deployment & flexibility
Customer Managed Cloud
Containerised deployment uses Kubernetes in customer-managed infrastructure. OpenShift compatibility, prerequisites and support must be checked for the selected release.
Fully hosted SaaS
A vendor-managed cloud environment reduces the infrastructure your team needs to operate. Available regions, integrations and customisation depend on the selected offering.
Cost & team considerations
Customer Managed Cloud
Plan for software and support, cloud resources and the people needed to operate the platform. Greater control also brings greater operational responsibility.
Fully hosted SaaS
Plan for the SaaS subscription and any integration or administration work. Confirm what is included rather than assuming every operational task is covered.
Often a good fit when…
Customer Managed Cloud
You need customer-controlled infrastructure and have the operational capability to maintain it, or your policies require a deployment inside your own environment.
Fully hosted SaaS
You want to reduce infrastructure management and focus your team on analytics delivery, subject to your security, integration and service requirements.
We help evaluate infrastructure ownership, data connectivity, security requirements and operational readiness, then define an implementation and handover plan. Neither model automatically guarantees compliance or lower cost.
Final responsibilities, capabilities and support depend on the selected release and service agreement. References: Strategy CMC service guide and Managed Cloud Enterprise documentation.
MicroStrategy on OpenShift · Pre-deployment review
OpenShift readiness checklist
Confirm the evidence behind each item with your platform team and vendor. OpenShift is an emerging deployment option, not a required migration from AWS, other cloud or on-premises environments.
0 of 12 checks reviewed
MicroStrategy version compatibility
Include patch levels and the planned upgrade path.
Verify the support matrix, prerequisites and service scope for this exact combination—not Kubernetes support alone.
Review database drivers, metadata repository, identity integration and existing reports before committing.
Container support
Check image versions, licensing and the vendor-supported packaging; do not assume a VM installation can be containerised unchanged.
Confirm OpenShift compatibility, installation permissions and lifecycle / upgrade procedures.
Check security context constraints, service accounts, image scanning and supported configuration without weakening cluster policies.
Infrastructure prerequisites
Use vendor prerequisites and load testing; agree quotas, availability and capacity headroom.
Validate approved routes to data sources, identity providers and artifact registries, including restricted-network requirements.
Confirm supported storage classes, access modes, metadata database compatibility and backup / restore design.
Operational considerations
Agree responsibility for incidents, access, application maintenance and vendor escalation.
Set recovery objectives, rehearse restore procedures and verify alerts, audit logs and secrets handling.
Complete performance and user acceptance testing; document rollback, change control and operational handover.
This checklist tracks your review, not verified compatibility or production approval. Vendor support remains release-specific; an unsupported combination must be resolved before deployment.
Loading saved progress…
Analytics records progress counts and changes, not which requirements you have reviewed.
Discuss your OpenShift readinessOrganisation experience
Experience across enterprise environments.
- Hilton
- Los Alamos Lab
- CitiBank
- Catamaran
- Giant retail
- Inventiv Health
Selected organisations from our experience. Names are not endorsements; the implementation examples below are illustrative and are not attributed to these organisations.
Project stories · Illustrative, not client work
MicroStrategy in your industry.
Hypothetical project scenarios across five sectors, showing a possible delivery approach and intended outcomes. These are not real client work, verified case studies or measured results.
End-to-end implementation approach
MicroStrategy: from requirements to production.
A complete delivery scope covering platform setup, enterprise reporting and operational handover.
- 01
Discover & scope
Agree stakeholders, use cases, source systems, business metrics and acceptance criteria.
- 02
Architect & install
Plan environments, sizing, network connectivity, identity and platform installation on AWS, Azure, Google Cloud or on-premises infrastructure. Evaluate OpenShift separately when modernisation requirements justify it.
- 03
Model & build
Develop schema, attributes, facts and metrics; implement reports, dossiers and distribution.
- 04
Secure & validate
Review access, reconcile data, tune performance and run user acceptance testing.
- 05
Launch & enable
Plan production cutover and rollback, train users and hand over administration documentation.
- 06
Operate & improve
Establish monitoring, support ownership, upgrade planning and a prioritised improvement backlog.
For a Customer Managed Cloud deployment on OpenShift, confirm release compatibility and vendor support before selecting the installation architecture.
Practical deliverables
A plan your team can act on.
- Architecture and metadata assessment
- Prioritised performance recommendations
- Upgrade or migration roadmap
- SAML SSO configuration, validation and certificate-renewal guidance
- Migration automation workflows and release-validation guidance
- Cube refresh schedules, monitoring and failure-handling runbooks
- User-management automation and auditable administration procedures
- Testing guidance and knowledge transfer
Scope and deliverables are agreed around your environment, priorities and team.
A clear path through the engagement.
Assess
We audit your current platform, data and team to find what's slowing you down.
Design
A clear target architecture and roadmap, sized to your budget and timeline.
Deliver
Hands-on senior engineers build, migrate and tune — onsite, remote or blended.
Enable
Documentation, training and ongoing support so your team owns the result.
Built around your environment
Clear priorities. Practical delivery. Lasting ownership.
Start with the business decision
Define the reporting, performance or platform problem first. Agree the users, data dependencies and acceptance criteria before choosing the implementation approach.
Make governance part of delivery
Consider access, trusted metric definitions, release compatibility and operational responsibility alongside the technical design—not after rollout.
Leave a maintainable foundation
Plan validation, documentation and knowledge transfer around the people who will own the platform. A successful handover matters as much as the initial deployment.
Start a conversation · Worldwide
MicroStrategy automation.
A clear next step.
Discuss code migration, Intelligent Cube refresh or user-management automation. Share your goals, current environment and project timeline so we can review an appropriate scope.
info@solutionprimary.comTell us what needs to change and what success would mean for your team. Share only non-confidential project context; technical access and sensitive information can be discussed separately.