User profile for jchoksi

Just closing the loop on this thread for anyone else looking to setup a GCP Cloud SQL instance as their data repository for SQL Monitor. It won't work. SQL Monitor's installer + Base monitor service fail to query details about the schema for the RedgateMonitor database due to the SQL queries used for this, accessing the "model" database on SQL Server. In the end we didn't bother trying to use a managed instance of SQL Server at all and simply used a SQL Server machine image (https://cloud.google.com/compute/docs/images/os-details#sql_server) to bring up a Windows server with SQL Server pre-installed. This comes with on demand licensing which was the major factor in pursuing a managed instance for us. Thanks for your input Russell. All the best. / comments

Just closing the loop on this thread for anyone else looking to setup a GCP Cloud SQL instance as their data repository for SQL Monitor.It won't work.SQL Monitor's installer + Base monitor service ...

0 votes

>However, this just sounds like the exact same problem that using Azure SQL DBs has (ie can't access the model database). >So you might be able to workaround this in the same way we recommend for Azure, by creating a blank empty database in GCP, and when you install Monitor, use an existing database. The installer can then connect to it, and perform a schema upgrade and away you go. I tried following that advice but the base service monitor installer complains that it can't access the model database. What I've also tried so far is: - I installed base monitor service on a throwaway VM which had SQL Server Express on it. - I wen through the base monitor service installation and used it to create a RedGateMonitor database in the SQL Server Express instance. - I used SSMS to "Generate Scripts" for the RedGateMonitor database and save the sql into a single script. - I stripped the script for any database creation sql and all that was left was the sql to create the objects under the RedGateMonitor monitor database. I had to also remove any mention of ", OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF" which seems to be a SQL Server 2019 feature and GCP Cloud SQL only supports SQL Server 2017. - This script was successfully applied to an empty database in the GCP Cloud SQL instance. - I tried launching base monitor service with its config amended to point to this database and I still experienced the can't access model database issue. Am I missing some change that was done to make this work for Azure SQL databases? I looked at the base monitor service's config file and I was wondering whether I need to amend the databaseEngine value to something other than Mssql? I tried amending autoUpgrade to "false" but that did not resolve the issue but did reduce the number of exceptions reported. <repositorySettings readOnlyMode="false"> <maintenance dayOfWeek="Sunday" localTimeOfDay="1:00" mode="Sample"/> <dataStore databaseEngine="Mssql" autoUpgrade="false"> <mssql version="Auto" connectionStringName="DataConnectionString"/> </dataStore> </repositorySettings> This will be my last attempt to try to get it to work on GCP Cloud SQL and I will try to setup an Azure SQL db next. Is there any documentation on what I would need to do to use Azure SQL as the host for the data respository? / comments

>However, this just sounds like the exact same problem that using Azure SQL DBs has (ie can't access the model database). >So you might be able to workaround this in the same way we recommend for A...

0 votes

SQL Monitor Data Repository on GCP Cloud SQL Server

HiWe know that on the supported platform page ((https://documentation.red-gate.com/sm/installation-and-setup/planning-the-sql-monitor-infrastructure-and-installation/supported-platforms#Supportedpl...

2 followers 4 comments 0 votes

How can we help you today?

jchoksi

Activity overview