PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #33
Your organization is running a low-latency reporting application on Microsoft SQL Server. In addition to the database engine, you are using SQL Server Analysis Services (SSAS), SQL Server Reporting…
The correct answer is C. Migrate to Compute Engine. Cloud SQL for SQL Server (option A) is a managed service that supports only the core SQL Server database engine - it does not support SQL Server Analysis Services (SSAS), SQL Server Reporting Services (SSRS), or SQL Server Integration Services (SSIS). Migrating to Compute…
Question
Your organization is running a low-latency reporting application on Microsoft SQL Server. In addition to the database engine, you are using SQL Server Analysis Services (SSAS), SQL Server Reporting Services (SSRS), and SQL Server Integration Services (SSIS) in your on- premises environment. You want to migrate your Microsoft SQL Server database instances to Google Cloud. You need to ensure minimal disruption to the existing architecture during migration. What should you do?
Options
- AMigrate to Cloud SQL for SQL Server.
- BMigrate to Cloud SQL for PostgreSQL.
- CMigrate to Compute Engine.
- DMigrate to Google Kubernetes Engine (GKE).
How the community answered
(34 responses)- A3% (1)
- B6% (2)
- C82% (28)
- D9% (3)
Explanation
Cloud SQL for SQL Server (option A) is a managed service that supports only the core SQL Server database engine - it does not support SQL Server Analysis Services (SSAS), SQL Server Reporting Services (SSRS), or SQL Server Integration Services (SSIS). Migrating to Compute Engine (option C) lets you install a full SQL Server instance with all these companion services intact, preserving the existing architecture with minimal disruption. Cloud SQL for PostgreSQL (option B) is a different engine entirely, and GKE (option D) would require significant rearchitecting.
Topics
Community Discussion
No community discussion yet for this question.