Cloud SQL supportsSQL Server Reporting Services (SSRS) which helps you create, deploy, and manage paginated reports.

This page provides the prerequisites, setup procedure, and limitations for usingSSRS in Cloud SQL.

Before you begin

Before using SSRS on Cloud SQL, you must have the following:

• A Cloud SQL instance to host the report server database
• A host where you install and run SSRS.It can be either a Compute Engine VM or a host that doesn't use Compute Engine.For installation instructions, seeInstall SQL Server Reporting Services.

• A Cloud DNS record to assign a hostname for your Cloud SQL instance.You can create a hostname by using one of the following options:

  • Cloud DNS: UseCloud DNS to create a hostname that points to your instance.
  • Custom DNS zone: If you manage your own DNS zone, thencreate an A record that maps your preferred hostname to the IP address of your instance.
  • Local hostname mapping: Modify your system'shosts file to create a custom alias for your instance.

• Two existing Cloud SQL logins, a setup login and a service login.To create a login, seegcloud sql users create.

  Note: Cloud SQL doesn't support using Windows logins for SSRS.

  If you want to use Windows authentication, then you must use Managed Active Directory to join the SQL Server instance and the host running SSRS. For more information, seeUse Managed Microsoft AD with Cloud SQL.

Procedure

To set up SSRS in Cloud SQL, perform the following steps:

1. Acquire an SSRS lease.
2. Set up SSRS.
3. Release an SSRS lease.

Acquire an SSRS lease

SSRS requires elevated permissions during setup. To acquire an SSRS lease for your instance, use the following command:

gcloudsqlinstancesacquire-ssrs-leaseINSTANCE_NAME\--project=PROJECT_NAME\--setup-login=SETUP_LOGIN\--service-login=SERVICE_LOGIN\--report-database=REPORT_DATABASE\--duration=DURATION\

POSThttps://sqladmin.googleapis.com/sql/v1/projects/PROJECT_ID/instances/INSTANCE_NAME/acquireSsrsLease

{"acquireSsrsLeaseContext":{"setupLogin":SETUP_LOGIN,"serviceLogin":SERVICE_LOGIN,"reportDatabase":REPORT_DATABASE,"duration":DURATION,}}

POSThttps://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME/acquireSsrsLease

{"acquireSsrsLeaseContext":{"setupLogin":SETUP_LOGIN,"serviceLogin":SERVICE_LOGIN,"reportDatabase":REPORT_DATABASE,"duration":DURATION,}}

Set up SSRS

gcloudsqlinstancesrelease-ssrs-leaseINSTANCE_NAME\--project=PROJECT_NAME

POSThttps://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME/releaseSsrsLease

POSThttps://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME/releaseSsrsLease

You acquire a lease usinggcloud sql instances acquire-ssrs-leasebefore configuration and release it afterwards withgcloud sql instances release-ssrs-lease.The lease has a configurable duration.

Authentication

The following section helps address authentication questions.

Can I use Windows Authentication (Microsoft Active Directory) for setup?

No, you must use SQL Server logins for the--setup-login and--service-login parameters when acquiring the lease and configuringthe report server database. Windows logins are not supported for this initialsetup process.

While setup requires SQL logins, you can potentially use Windows Authenticationfor accessing reports if your Cloud SQL instance and the SSRS host areboth joined to one of the following domain types:

• Customer-managed Active Directory (CMAD) (recommended)
• Managed Service for Microsoft Active Directory

Restrictions

The following section helps address questions related to restrictions or limitations.

What are the limitations of using SSRS with Cloud SQL?

• There aren't any Microsoft Active Directory logins for the database setup phase.
• The report database name can only contain alphanumeric characters and hyphens.
• You must acquire a new lease if you want to change the service accountcredentials later.
• Scale-out deployments require the lease process for each new SSRS host.
• Importing existing report server databases requires manual steps to remap theservice login user.

Pricing considerations

The following section helps address pricing considerations.

What are the costs associated with licensing?

• A SQL Server license is required for your Cloud SQL instance.
• Since SSRS runs a separate Windows machine, make sure the Windows OS and anySQL Server components on that machine are properly licensed. According toMicrosoft's policies, running SSRS on a separate server might require anadditional SQL Server license.

Automation

The following section helps address questions related to automation.

Can you automate the SSRS host installation and configuration process?

You can run operations to acquire and release the SSRS lease within Cloud SQLusinggcloud CLI or REST APIs.

The SSRS installation and configuration within the Windows environment itselftypically involves manual steps through the Reporting Services ConfigurationManager interface, making full end-to-end automation more challenging.

For more information, seeInstall and configure SSRS.

Maintenance

The following section helps address questions related to maintenance.

What are the potential management and maintenance activities associated with using SSRS?

Before you begin, consider the ongoing management overhead associated with theseparate SSRS server. You are responsible for managing, patching, and securingthe Windows VM running the SSRS service. Cloud SQL only manages thedatabase instance.