Friday, January 29, 2021

[google-cloud-sql-discuss] Failed to import Data from csv into CloudSQL-postgres

Hi GCP- community, 

I have a csv table in cloud storage that matches the table in CloudSQL. The service account of CloudSQL instance has granted storage.objectAdmin IAM role as mentioned in the GCP-Documentions. I am also the owner of the project. 

1- When I imported the data into the table (Overview--> import) the job shows up that the data has been successfully imported but when I check the table using SELECT it doesn't deliver any data?

2- When I use the gcloud sql command: gcloud sql import csv gs://[BUCKET_NAME]/[FILE_NAME] --database=[DATABASE_NAME] --table=[TABLE_NAME] I get this msg : ERROR: (gcloud.sql.import.csv) [ERROR_RDBMS] ERROR: relation "temp_value" does not exist 

Thanks For your support!

 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/6d268fd5-a6b4-4403-a72c-d651835720b4n%40googlegroups.com.

Thursday, January 28, 2021

Re: [google-cloud-sql-discuss] Query insight doesn't work

Hello,

I understand that Cloud SQL query insights is not working for you. From the data provided, I am not able to identify the root cause but I was able to find a Google Codelab updated yesterday that walks you through setting it up.
I hope that this is a simple issue where a step was missing and in this case, I would encourage you to take a look at this link and let us know if somehow a step was indeed missed. 

This is just a hypothesis at this point and I encourage you to reply if the lab works for you.


On Thursday, January 28, 2021 at 1:37:04 PM UTC-5 pe...@flowms.ai wrote:
It works for me. I assume it's using pg_stat_statements. Do you have that extension enabled?

CREATE EXTENSION pg_stat_statements

On Thu, Jan 28, 2021, 12:38 PM Peter Kowenzowski <pe...@airspace-intelligence.com> wrote:
There is new feature called query insights. However, doesn't work for us:

Screenshot 2021-01-28 at 17.55.38.png

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/778f2229-98d4-48a7-9645-85f5307d3f18n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/46882e56-c302-44dc-88d8-25e70eac37aan%40googlegroups.com.

Re: [google-cloud-sql-discuss] Query insight doesn't work

It works for me. I assume it's using pg_stat_statements. Do you have that extension enabled?

CREATE EXTENSION pg_stat_statements

On Thu, Jan 28, 2021, 12:38 PM Peter Kowenzowski <peter@airspace-intelligence.com> wrote:
There is new feature called query insights. However, doesn't work for us:

Screenshot 2021-01-28 at 17.55.38.png

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/778f2229-98d4-48a7-9645-85f5307d3f18n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CAC%2B%3DFfYp1sWANVzwXDZbv09xCygdMD9QTypbE8YGhiWQbaDGXg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: Query insight doesn't work

If you just enabled it, it may take a few minutes before you start to see the data coming through. Is it working for you now?

On Thursday, January 28, 2021 at 12:38:08 PM UTC-5 pe...@airspace-intelligence.com wrote:
There is new feature called query insights. However, doesn't work for us:

Screenshot 2021-01-28 at 17.55.38.png

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/de1e1bda-e2ab-494d-a83b-efbeeabafdabn%40googlegroups.com.

[google-cloud-sql-discuss] Query insight doesn't work

There is new feature called query insights. However, doesn't work for us:

Screenshot 2021-01-28 at 17.55.38.png

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/778f2229-98d4-48a7-9645-85f5307d3f18n%40googlegroups.com.

Monday, January 25, 2021

[google-cloud-sql-discuss] Re: PostgreSQL Extension request - PLv8

+1 for PLv8, it's a trusted postgres language and is keeping my team from adopting cloud sql.

On Saturday, April 22, 2017 at 3:47:54 PM UTC-5 Reuben Honigwachs wrote:
+1 If this is how it works :-)

So there is conflicting information in the Google Cloud docs whether requests regarding extensions go into this Google Group or have to be risen in the issue tracker. See https://groups.google.com/forum/#!topic/google-cloud-sql-discuss/lHam63RCXD4 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/75ff818e-db07-47af-9faf-ac1ecea7e3ffn%40googlegroups.com.

Friday, January 22, 2021

Re: [google-cloud-sql-discuss] Re: CloudSQL Instance size issue.

Either case. I'd strongly advise you to contact support [1] and if you've purchased a support plan to create a support case [2]. As this will not be the correct place to share your project name or any data about your Cloud SQL instance for further investigation. 

[1] https://cloud.google.com/support-hub
[2] https://cloud.google.com/support/docs/manage-cases#creating_cases

On Thursday, January 21, 2021 at 5:59:47 PM UTC+1 rajat....@telusinternational.com wrote:
Enabling the PITR shoots the db storage exponentially based on the traffic on the database. 
Also, might scale up the storage allocation of the instance which cannot be reduced at a later stage.


On Thursday, 21 January, 2021 at 9:15:39 pm UTC+5:30 Rajendra More wrote:
We have set the ""log_output = FILE" flag and binary logging is on for this instance because it is in  "Auto Backup" and "Point in time recovery" mode.
This issue might be because of binary logging, but I read that old binary logs are removed after every daily auto backup, Is it true ? If it is true then binary log size must be low.

--
Rajendra More
IT Infrastructure Manager
+91-(976) 433-5755



On Thu, Jan 21, 2021 at 2:23 PM 'ocando' via Google Cloud SQL discuss <google-cloud...@googlegroups.com> wrote:
The issue might have to do with the way you configured the "log_output" flag. As described here [1] it is recommended to use FILE (as if you have set the flag to "TABLE" the table created might become very large and affect your database). Another usual suspect for increased Storage that is not related to your data might have to do with the binary logging. 
Either case. I'd strongly advise you to contact support [2] and if you've purchased a support plan to create a support case [3]. As this will not be the correct place to share your project name or any data about your Cloud SQL instance,

On Wednesday, January 20, 2021 at 9:11:16 AM UTC+1 Rajendra More wrote:
Hello All,

We have a 2nd generation  MySQL 5.7  database instance with HA, In last few day's SQL instance storage size is increasing. Total database size is 28GB, but currently storage size more than 70 GB. Have anyone faced this type of issue.
We have enabled "slow_query_log" and "log_output" flags. 

Thank you,

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/195dc379-aeb1-4886-a972-9ec5704dbb16n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/9cd38200-ca7d-435b-8646-1bf90e7c4dbdn%40googlegroups.com.

Thursday, January 21, 2021

Re: [google-cloud-sql-discuss] Re: CloudSQL Instance size issue.

Enabling the PITR shoots the db storage exponentially based on the traffic on the database. 
Also, might scale up the storage allocation of the instance which cannot be reduced at a later stage.


On Thursday, 21 January, 2021 at 9:15:39 pm UTC+5:30 Rajendra More wrote:
We have set the ""log_output = FILE" flag and binary logging is on for this instance because it is in  "Auto Backup" and "Point in time recovery" mode.
This issue might be because of binary logging, but I read that old binary logs are removed after every daily auto backup, Is it true ? If it is true then binary log size must be low.

--
Rajendra More
IT Infrastructure Manager
+91-(976) 433-5755



On Thu, Jan 21, 2021 at 2:23 PM 'ocando' via Google Cloud SQL discuss <google-cloud...@googlegroups.com> wrote:
The issue might have to do with the way you configured the "log_output" flag. As described here [1] it is recommended to use FILE (as if you have set the flag to "TABLE" the table created might become very large and affect your database). Another usual suspect for increased Storage that is not related to your data might have to do with the binary logging. 
Either case. I'd strongly advise you to contact support [2] and if you've purchased a support plan to create a support case [3]. As this will not be the correct place to share your project name or any data about your Cloud SQL instance,

On Wednesday, January 20, 2021 at 9:11:16 AM UTC+1 Rajendra More wrote:
Hello All,

We have a 2nd generation  MySQL 5.7  database instance with HA, In last few day's SQL instance storage size is increasing. Total database size is 28GB, but currently storage size more than 70 GB. Have anyone faced this type of issue.
We have enabled "slow_query_log" and "log_output" flags. 

Thank you,

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/195dc379-aeb1-4886-a972-9ec5704dbb16n%40googlegroups.com.

Confidentiality Notice: 
This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED.  If you have received this transmission in error, please immediately notify the sender. Please destroy the original transmission and its attachments without reading or saving in any manner.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/2aaf20ae-02cc-4b21-b538-b6360683aa0en%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: CloudSQL Instance size issue.

We have set the ""log_output = FILE" flag and binary logging is on for this instance because it is in  "Auto Backup" and "Point in time recovery" mode.
This issue might be because of binary logging, but I read that old binary logs are removed after every daily auto backup, Is it true ? If it is true then binary log size must be low.

--
Rajendra More
IT Infrastructure Manager
+91-(976) 433-5755



On Thu, Jan 21, 2021 at 2:23 PM 'ocando' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:
The issue might have to do with the way you configured the "log_output" flag. As described here [1] it is recommended to use FILE (as if you have set the flag to "TABLE" the table created might become very large and affect your database). Another usual suspect for increased Storage that is not related to your data might have to do with the binary logging. 
Either case. I'd strongly advise you to contact support [2] and if you've purchased a support plan to create a support case [3]. As this will not be the correct place to share your project name or any data about your Cloud SQL instance,

On Wednesday, January 20, 2021 at 9:11:16 AM UTC+1 Rajendra More wrote:
Hello All,

We have a 2nd generation  MySQL 5.7  database instance with HA, In last few day's SQL instance storage size is increasing. Total database size is 28GB, but currently storage size more than 70 GB. Have anyone faced this type of issue.
We have enabled "slow_query_log" and "log_output" flags. 

Thank you,

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/195dc379-aeb1-4886-a972-9ec5704dbb16n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CAEMpOSLOwsAFigaowsNLLu0PQmx7CCru6BdKu9tAHbmQFjZc%3Dg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: CloudSQL Instance size issue.

The issue might have to do with the way you configured the "log_output" flag. As described here [1] it is recommended to use FILE (as if you have set the flag to "TABLE" the table created might become very large and affect your database). Another usual suspect for increased Storage that is not related to your data might have to do with the binary logging. 
Either case. I'd strongly advise you to contact support [2] and if you've purchased a support plan to create a support case [3]. As this will not be the correct place to share your project name or any data about your Cloud SQL instance,

[1] https://cloud.google.com/sql/docs/mysql/flags#tips
[2] https://cloud.google.com/support-hub
[3] https://cloud.google.com/support/docs/manage-cases#creating_cases

On Wednesday, January 20, 2021 at 9:11:16 AM UTC+1 Rajendra More wrote:
Hello All,

We have a 2nd generation  MySQL 5.7  database instance with HA, In last few day's SQL instance storage size is increasing. Total database size is 28GB, but currently storage size more than 70 GB. Have anyone faced this type of issue.
We have enabled "slow_query_log" and "log_output" flags. 

Thank you,

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/195dc379-aeb1-4886-a972-9ec5704dbb16n%40googlegroups.com.

Wednesday, January 20, 2021

[google-cloud-sql-discuss] Re: Cloud SQL export failed

Bug was acknowledged - https://issuetracker.google.com/issues/177989504

On Wednesday, January 20, 2021 at 9:31:26 PM UTC+3 Кирилл Дубровин wrote:
Hello,

I am experiencing the same issue with my account. And just like the author, everything was working several days ago.

On Wednesday, January 20, 2021 at 8:53:48 PM UTC+3 Elliott (Google Cloud Platform Support) wrote:
Hello,

To better understand your issue, I did a reproduction on my system. I created a Cloud SQL Server instance and created a database from a BAK file I found on the Microsoft website by first downloading it to my system, then uploading it to a Cloud Storage Bucket. The database was then created.

Using your instructions: > gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export,  I exported the database without error.

This makes me believe that since I cannot find any common issues at this time, there is something in your project or configuration that is causing this error.

In this case, I would suggest the regular support channel for one to one support since Google Groups is meant for general discussions.

I was able to find a document here that describes how a gz file can be used for compressed imports.

"When you export a BAK file, use a .gz file extension to compress the data. When you import a file with an extension of .gz, it is decompressed automatically."

I hope this helps.

On Wednesday, January 20, 2021 at 9:49:41 AM UTC-5 j...@dimosoftware.com wrote:
Hello,

thank you for taking the time to analyze my problem.
I tried to change the name of the backup to "prod.bak" and the same error occurs.

Knowing that I was doing the same procedure a few days earlier and that it was working correctly, I wonder what this has to do with.

Do you know if it's possible to disable compression on the web interface? I haven't seen this kind of options.

Thank you

On Tuesday, 19 January 2021 at 16:25:25 UTC+1 Elliott (Google Cloud Platform Support) wrote:
Hello,

I understand that you have an error, when you are exporting a backup of an SQL database to a Google Storage Bucket. 

The error code that you mention indicates that backup terminated abnormally.
The main concern is the message "BACKUP DATABASE WITH COMPRESSION is not supported on Web."

I am unable to find a common issue now that would explain the error message. So I am thinking this message is related to your project.

In this case, I have found a possible explanation indicating that if you rename your BAK file, the error would no longer be present.

I would like for you to try this advice to see if it helps and reply back if it helped.


On Tuesday, January 19, 2021 at 8:40:52 AM UTC-5 j...@dimosoftware.com wrote:

Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/b6e99935-0ac4-41a1-ae13-677f7855ec06n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL export failed

Hello,

I am experiencing the same issue with my account. And just like the author, everything was working several days ago.

On Wednesday, January 20, 2021 at 8:53:48 PM UTC+3 Elliott (Google Cloud Platform Support) wrote:
Hello,

To better understand your issue, I did a reproduction on my system. I created a Cloud SQL Server instance and created a database from a BAK file I found on the Microsoft website by first downloading it to my system, then uploading it to a Cloud Storage Bucket. The database was then created.

Using your instructions: > gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export,  I exported the database without error.

This makes me believe that since I cannot find any common issues at this time, there is something in your project or configuration that is causing this error.

In this case, I would suggest the regular support channel for one to one support since Google Groups is meant for general discussions.

I was able to find a document here that describes how a gz file can be used for compressed imports.

"When you export a BAK file, use a .gz file extension to compress the data. When you import a file with an extension of .gz, it is decompressed automatically."

I hope this helps.

On Wednesday, January 20, 2021 at 9:49:41 AM UTC-5 j...@dimosoftware.com wrote:
Hello,

thank you for taking the time to analyze my problem.
I tried to change the name of the backup to "prod.bak" and the same error occurs.

Knowing that I was doing the same procedure a few days earlier and that it was working correctly, I wonder what this has to do with.

Do you know if it's possible to disable compression on the web interface? I haven't seen this kind of options.

Thank you

On Tuesday, 19 January 2021 at 16:25:25 UTC+1 Elliott (Google Cloud Platform Support) wrote:
Hello,

I understand that you have an error, when you are exporting a backup of an SQL database to a Google Storage Bucket. 

The error code that you mention indicates that backup terminated abnormally.
The main concern is the message "BACKUP DATABASE WITH COMPRESSION is not supported on Web."

I am unable to find a common issue now that would explain the error message. So I am thinking this message is related to your project.

In this case, I have found a possible explanation indicating that if you rename your BAK file, the error would no longer be present.

I would like for you to try this advice to see if it helps and reply back if it helped.


On Tuesday, January 19, 2021 at 8:40:52 AM UTC-5 j...@dimosoftware.com wrote:

Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/35622908-a3f1-40f6-8513-f3330e5bd60an%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL export failed

Hello,

To better understand your issue, I did a reproduction on my system. I created a Cloud SQL Server instance and created a database from a BAK file I found on the Microsoft website by first downloading it to my system, then uploading it to a Cloud Storage Bucket. The database was then created.

Using your instructions: > gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export,  I exported the database without error.

This makes me believe that since I cannot find any common issues at this time, there is something in your project or configuration that is causing this error.

In this case, I would suggest the regular support channel for one to one support since Google Groups is meant for general discussions.

I was able to find a document here that describes how a gz file can be used for compressed imports.

"When you export a BAK file, use a .gz file extension to compress the data. When you import a file with an extension of .gz, it is decompressed automatically."

I hope this helps.

On Wednesday, January 20, 2021 at 9:49:41 AM UTC-5 j...@dimosoftware.com wrote:
Hello,

thank you for taking the time to analyze my problem.
I tried to change the name of the backup to "prod.bak" and the same error occurs.

Knowing that I was doing the same procedure a few days earlier and that it was working correctly, I wonder what this has to do with.

Do you know if it's possible to disable compression on the web interface? I haven't seen this kind of options.

Thank you

On Tuesday, 19 January 2021 at 16:25:25 UTC+1 Elliott (Google Cloud Platform Support) wrote:
Hello,

I understand that you have an error, when you are exporting a backup of an SQL database to a Google Storage Bucket. 

The error code that you mention indicates that backup terminated abnormally.
The main concern is the message "BACKUP DATABASE WITH COMPRESSION is not supported on Web."

I am unable to find a common issue now that would explain the error message. So I am thinking this message is related to your project.

In this case, I have found a possible explanation indicating that if you rename your BAK file, the error would no longer be present.

I would like for you to try this advice to see if it helps and reply back if it helped.


On Tuesday, January 19, 2021 at 8:40:52 AM UTC-5 j...@dimosoftware.com wrote:

Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/2708b1b9-879c-47fb-94a5-7087c4aa254cn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL export failed

Hello,

To better understand your issue, I did a reproduction on my system. I created a Cloud SQL Server instance and created a database from a BAK file I found on the Microsoft website by first downloading it to my system, then uploading it to a Cloud Storage Bucket. The database was then created.

Using your instructions: > gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export,  I exported the database without error.

This makes me believe that since I cannot find any common issues at this time, there is something in your project or configuration that is causing this error.

In this case, I would suggest the regular support channel for one to one support since Google Groups is meant for general discussions.

I was able to find a document here that describes how a gz file can be used for compressed imports.

"When you export a BAK file, use a .gz file extension to compress the data. When you import a file with an extension of .gz, it is decompressed automatically."

For your question on disabling compression on the web interface, I think before exploring that option,

I hope this helps.


On Wednesday, January 20, 2021 at 9:49:41 AM UTC-5 j...@dimosoftware.com wrote:
Hello,

thank you for taking the time to analyze my problem.
I tried to change the name of the backup to "prod.bak" and the same error occurs.

Knowing that I was doing the same procedure a few days earlier and that it was working correctly, I wonder what this has to do with.

Do you know if it's possible to disable compression on the web interface? I haven't seen this kind of options.

Thank you

On Tuesday, 19 January 2021 at 16:25:25 UTC+1 Elliott (Google Cloud Platform Support) wrote:
Hello,

I understand that you have an error, when you are exporting a backup of an SQL database to a Google Storage Bucket. 

The error code that you mention indicates that backup terminated abnormally.
The main concern is the message "BACKUP DATABASE WITH COMPRESSION is not supported on Web."

I am unable to find a common issue now that would explain the error message. So I am thinking this message is related to your project.

In this case, I have found a possible explanation indicating that if you rename your BAK file, the error would no longer be present.

I would like for you to try this advice to see if it helps and reply back if it helped.


On Tuesday, January 19, 2021 at 8:40:52 AM UTC-5 j...@dimosoftware.com wrote:

Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/429adc11-2b03-4ee0-82c0-266317f75db4n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL export failed

Hello,

thank you for taking the time to analyze my problem.
I tried to change the name of the backup to "prod.bak" and the same error occurs.

Knowing that I was doing the same procedure a few days earlier and that it was working correctly, I wonder what this has to do with.

Do you know if it's possible to disable compression on the web interface? I haven't seen this kind of options.

Thank you

On Tuesday, 19 January 2021 at 16:25:25 UTC+1 Elliott (Google Cloud Platform Support) wrote:
Hello,

I understand that you have an error, when you are exporting a backup of an SQL database to a Google Storage Bucket. 

The error code that you mention indicates that backup terminated abnormally.
The main concern is the message "BACKUP DATABASE WITH COMPRESSION is not supported on Web."

I am unable to find a common issue now that would explain the error message. So I am thinking this message is related to your project.

In this case, I have found a possible explanation indicating that if you rename your BAK file, the error would no longer be present.

I would like for you to try this advice to see if it helps and reply back if it helped.


On Tuesday, January 19, 2021 at 8:40:52 AM UTC-5 j...@dimosoftware.com wrote:

Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/bb420e4b-6556-44d9-af89-92172d090fccn%40googlegroups.com.

Tuesday, January 19, 2021

[google-cloud-sql-discuss] CloudSQL Instance size issue.

Hello All,

We have a 2nd generation  MySQL 5.7  database instance with HA, In last few day's SQL instance storage size is increasing. Total database size is 28GB, but currently storage size more than 70 GB. Have anyone faced this type of issue.
We have enabled "slow_query_log" and "log_output" flags. 

Thank you,

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/6458e614-5b95-440d-9c57-0bd379e8c537n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL export failed

Hello,

I understand that you have an error, when you are exporting a backup of an SQL database to a Google Storage Bucket. 

The error code that you mention indicates that backup terminated abnormally.
The main concern is the message "BACKUP DATABASE WITH COMPRESSION is not supported on Web."

I am unable to find a common issue now that would explain the error message. So I am thinking this message is related to your project.

In this case, I have found a possible explanation indicating that if you rename your BAK file, the error would no longer be present.

I would like for you to try this advice to see if it helps and reply back if it helped.


On Tuesday, January 19, 2021 at 8:40:52 AM UTC-5 j...@dimosoftware.com wrote:

Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/781284ac-4c28-4c86-bd36-04a35cbf223cn%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL export failed


Hello,

I am trying to export a backup of an SQL database in a bucket. An error occured and the export has failed.

My process is simple :
> gcloud sql databases > export > .bak format > select database  > select bucket > leave the default name > Click Export

Logs:
-An unknown error occurred
-BACKUP DATABASE WITH COMPRESSION is not supported on Web Edition (64-bit).
-errors 1844 & 3041

I did the same procedure 5 days ago and i worked well.

Does anything changed in Cloud SQL ? or anyone facing the same problem ?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/dd3cf4f0-54d9-4ff0-beb3-17e9b8054e43n%40googlegroups.com.

Monday, January 18, 2021

[google-cloud-sql-discuss] Re: New project issue

Hello,

Please be advised that Google Groups is not a place for troubleshooting. To get a wider range of support, please post your issue on StackOverFlow and ServerFault.

A possible reason could be that you do not have permission to access. You will have to check your billing account and organization to see if your username/email have access/permission. 

I would advise you to ask the administrator of the organization to add you as a member, so you may able to access the IAM policies. 

You will have to give your user the required permissions to be able to access IAM Policies and make sure the users are added to the organization.

Hope this helps.

On Monday, January 18, 2021 at 9:30:23 AM UTC-5 simbat...@gmail.com wrote:
Hi All,

I have created new project, but I AM policy showing '?'.

I added sql admin service account from another project. but i am not able to connect, bec of above issue.

Please find the attached attachment.

Thanks,
Anil 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/feeb2c7c-e2c5-490d-9343-f7c09ee7416fn%40googlegroups.com.

Sunday, January 17, 2021

[google-cloud-sql-discuss] New project issue

Hi All,

I have created new project, but I AM policy showing '?'.

I added sql admin service account from another project. but i am not able to connect, bec of above issue.

Please find the attached attachment.

Thanks,
Anil 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/220b52d9-2577-42b7-806e-ab12442fe9c6n%40googlegroups.com.

Wednesday, January 13, 2021

[google-cloud-sql-discuss] Re: Cloud SQL PostgreSQL Committed Use

I believe your understanding is correct, for an instance with 4 HA vCPUs committed resource shall be 8 vCPUs. Standby instance is always running in HA configuration and billed the same as master instance. Also the documentation doesn't mention any exclusions for HA setups. 

On Wednesday, January 13, 2021 at 8:30:37 AM UTC+1 rajat....@telusinternational.com wrote:
Hi, Thanks for the explanation. 
A few questions:
How is High Availability resource calculated. If there is a instance with 4 HA vCPUs, for it committed resource shall be 8 vCPUs? Or committed resource shall be 4 HA vCPUs only?
Is the commitment dependent on number of instances using the resources ?


On Saturday, 9 January, 2021 at 4:49:11 am UTC+5:30 sohailalvi wrote:
Hello,

For your particular use case scenario, you can scale up the resources but you will be charged at standard billing for the differences in the resource above the committed use discount resources . You cannot scale down or in other you cannot  change or modify your CUD after you purchase a commitment , even your resource utilization is under CUD but you will be charged based on standard Committed Use Discounts (CUDs).

In  order to understand the concept of CUD , please read the following documents:

1-  Committed use discounts [1].
2-  Analyze the effectiveness of your resource-based committed use discounts [2].
3-  VM instances pricing[3].

Committed Use Discounts (CUDs) allow any customer to receive a substantial discount by committing to use a minimum quantity of concurrent GCE resources and reservations for 1 year or 3 years. Reservations allow you to reserve certain GCE resources (vCPUs, memory, GPUs, PD and/or Local SSD) in a specific Zone for later consumption without the hassle of running and monitoring VMs to hold the desired capacity.

Committed use discounts are ideal for workloads with predictable resource needs. When you purchase a committed use contract, you purchase compute resources (vCPUs, memory, GPUs, and local SSDs) at a discounted price in return for committing to paying for those resources for 1 year or 3 years. The discount is up to 57% for most resources like machine types or GPUs. The discount is up to 70% for memory-optimized machine types.[1].

By default, committed use discounts apply at the project level, but you can enable discount sharing from your billing account to share discounts across multiple projects.

Note:

1- After you create a commitment, you can't cancel it. You must pay the agreed upon monthly amount for the duration of the commitment

2- After you purchase a commitment, you can't change it. If you need to modify a commitment, purchase a new commitment with a new expiration date for the incremental amount.

After purchasing, you are billed monthly for the resources you purchased for the duration of the term you selected, whether or not you use the services. If you have a predictable workload, you can use discounts to help you cut costs on resources that you need.

Committed use discounts work on most Compute Engine machine types, including predefined and custom machine types, however, f1-micro and g1-small shared-core machines are excluded. Committed use discounts are simple and flexible, and require no upfront costs. Discounts apply to the aggregate number of vCPUs, memory, GPUs and local SSDs within a region, so they are not affected by changes to your instance's machine setup.

For your particular use cases please read  the section " How committed use discounts work" [1] and you will know in detail.

For example, if you purchase a commitment for 8 cores, and you run 24 cores during the month, you will receive committed use discounts for 8 cores. The other 16 cores will be billed at standard, non-committed use rates. Keep in mind that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 8 cores, you're billed the committed use rates for those 8 cores for the whole month, even if you might have only run these cores for a part of the month. It is to your advantage to purchase commitments only in increments you know you will use.

You can scale up but will be charged at standard billing for the differences in the resource .

Thanks You,
On Friday, January 8, 2021 at 6:54:39 AM UTC-5 rajat....@telusinternational.com wrote:
Hi, 
can the configuration and number of instance be scaled up/down during committed use?

is there some billing difference in the cases below?:

If Committed Use is configured at 2 vCPUs and 10GB Memory
Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory
Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory
Also, Instance1 configuration is 1 vCPUs and 5GB Memory
Instance2 configuration is 1 vCPUs and 5GB Memory

or

If Committed Use is configured at 4 vCPUs and 10GB Memory
Also, Instance1 configuration is 3 vCPUs and 6GB Memory,
Instance2 configuration is 1 vCPUs and 4GB Memory



--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3b477c63-a212-48b4-b945-3610529af611n%40googlegroups.com.

Tuesday, January 12, 2021

[google-cloud-sql-discuss] Re: Cloud SQL PostgreSQL Committed Use

Hi, Thanks for the explanation. 
A few questions:
How is High Availability resource calculated. If there is a instance with 4 HA vCPUs, for it committed resource shall be 8 vCPUs? Or committed resource shall be 4 HA vCPUs only?
Is the commitment dependent on number of instances using the resources ?


On Saturday, 9 January, 2021 at 4:49:11 am UTC+5:30 sohailalvi wrote:
Hello,

For your particular use case scenario, you can scale up the resources but you will be charged at standard billing for the differences in the resource above the committed use discount resources . You cannot scale down or in other you cannot  change or modify your CUD after you purchase a commitment , even your resource utilization is under CUD but you will be charged based on standard Committed Use Discounts (CUDs).

In  order to understand the concept of CUD , please read the following documents:

1-  Committed use discounts [1].
2-  Analyze the effectiveness of your resource-based committed use discounts [2].
3-  VM instances pricing[3].

Committed Use Discounts (CUDs) allow any customer to receive a substantial discount by committing to use a minimum quantity of concurrent GCE resources and reservations for 1 year or 3 years. Reservations allow you to reserve certain GCE resources (vCPUs, memory, GPUs, PD and/or Local SSD) in a specific Zone for later consumption without the hassle of running and monitoring VMs to hold the desired capacity.

Committed use discounts are ideal for workloads with predictable resource needs. When you purchase a committed use contract, you purchase compute resources (vCPUs, memory, GPUs, and local SSDs) at a discounted price in return for committing to paying for those resources for 1 year or 3 years. The discount is up to 57% for most resources like machine types or GPUs. The discount is up to 70% for memory-optimized machine types.[1].

By default, committed use discounts apply at the project level, but you can enable discount sharing from your billing account to share discounts across multiple projects.

Note:

1- After you create a commitment, you can't cancel it. You must pay the agreed upon monthly amount for the duration of the commitment

2- After you purchase a commitment, you can't change it. If you need to modify a commitment, purchase a new commitment with a new expiration date for the incremental amount.

After purchasing, you are billed monthly for the resources you purchased for the duration of the term you selected, whether or not you use the services. If you have a predictable workload, you can use discounts to help you cut costs on resources that you need.

Committed use discounts work on most Compute Engine machine types, including predefined and custom machine types, however, f1-micro and g1-small shared-core machines are excluded. Committed use discounts are simple and flexible, and require no upfront costs. Discounts apply to the aggregate number of vCPUs, memory, GPUs and local SSDs within a region, so they are not affected by changes to your instance's machine setup.

For your particular use cases please read  the section " How committed use discounts work" [1] and you will know in detail.

For example, if you purchase a commitment for 8 cores, and you run 24 cores during the month, you will receive committed use discounts for 8 cores. The other 16 cores will be billed at standard, non-committed use rates. Keep in mind that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 8 cores, you're billed the committed use rates for those 8 cores for the whole month, even if you might have only run these cores for a part of the month. It is to your advantage to purchase commitments only in increments you know you will use.

You can scale up but will be charged at standard billing for the differences in the resource .

Thanks You,
On Friday, January 8, 2021 at 6:54:39 AM UTC-5 rajat....@telusinternational.com wrote:
Hi, 
can the configuration and number of instance be scaled up/down during committed use?

is there some billing difference in the cases below?:

If Committed Use is configured at 2 vCPUs and 10GB Memory
Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory
Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory
Also, Instance1 configuration is 1 vCPUs and 5GB Memory
Instance2 configuration is 1 vCPUs and 5GB Memory

or

If Committed Use is configured at 4 vCPUs and 10GB Memory
Also, Instance1 configuration is 3 vCPUs and 6GB Memory,
Instance2 configuration is 1 vCPUs and 4GB Memory




Confidentiality Notice: 
This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED.  If you have received this transmission in error, please immediately notify the sender. Please destroy the original transmission and its attachments without reading or saving in any manner.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/39568033-414e-4c09-b498-620846d092e5n%40googlegroups.com.

Friday, January 8, 2021

[google-cloud-sql-discuss] Re: Cloud SQL PostgreSQL Committed Use

Hello,

For your particular use case scenario, you can scale up the resources but you will be charged at standard billing for the differences in the resource above the committed use discount resources . You cannot scale down or in other you cannot  change or modify your CUD after you purchase a commitment , even your resource utilization is under CUD but you will be charged based on standard Committed Use Discounts (CUDs).

In  order to understand the concept of CUD , please read the following documents:

1-  Committed use discounts [1].
2-  Analyze the effectiveness of your resource-based committed use discounts [2].
3-  VM instances pricing[3].

Committed Use Discounts (CUDs) allow any customer to receive a substantial discount by committing to use a minimum quantity of concurrent GCE resources and reservations for 1 year or 3 years. Reservations allow you to reserve certain GCE resources (vCPUs, memory, GPUs, PD and/or Local SSD) in a specific Zone for later consumption without the hassle of running and monitoring VMs to hold the desired capacity.

Committed use discounts are ideal for workloads with predictable resource needs. When you purchase a committed use contract, you purchase compute resources (vCPUs, memory, GPUs, and local SSDs) at a discounted price in return for committing to paying for those resources for 1 year or 3 years. The discount is up to 57% for most resources like machine types or GPUs. The discount is up to 70% for memory-optimized machine types.[1].

By default, committed use discounts apply at the project level, but you can enable discount sharing from your billing account to share discounts across multiple projects.

Note:

1- After you create a commitment, you can't cancel it. You must pay the agreed upon monthly amount for the duration of the commitment

2- After you purchase a commitment, you can't change it. If you need to modify a commitment, purchase a new commitment with a new expiration date for the incremental amount.

After purchasing, you are billed monthly for the resources you purchased for the duration of the term you selected, whether or not you use the services. If you have a predictable workload, you can use discounts to help you cut costs on resources that you need.

Committed use discounts work on most Compute Engine machine types, including predefined and custom machine types, however, f1-micro and g1-small shared-core machines are excluded. Committed use discounts are simple and flexible, and require no upfront costs. Discounts apply to the aggregate number of vCPUs, memory, GPUs and local SSDs within a region, so they are not affected by changes to your instance's machine setup.

For your particular use cases please read  the section " How committed use discounts work" [1] and you will know in detail.

For example, if you purchase a commitment for 8 cores, and you run 24 cores during the month, you will receive committed use discounts for 8 cores. The other 16 cores will be billed at standard, non-committed use rates. Keep in mind that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 8 cores, you're billed the committed use rates for those 8 cores for the whole month, even if you might have only run these cores for a part of the month. It is to your advantage to purchase commitments only in increments you know you will use.

You can scale up but will be charged at standard billing for the differences in the resource .

Thanks You,

Links:
[1] https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts.
[2] https://cloud.google.com/billing/docs/how-to/cud-analysis-resource-based#understanding_commitment_recommendations.
[3] https://cloud.google.com/compute/vm-instance-pricing


On Friday, January 8, 2021 at 6:54:39 AM UTC-5 rajat....@telusinternational.com wrote:
Hi, 
can the configuration and number of instance be scaled up/down during committed use?

is there some billing difference in the cases below?:

If Committed Use is configured at 2 vCPUs and 10GB Memory
Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory
Also, Instance configuration is 1 HA vCPUs and 5GB HA Memory

or

If Committed Use is configured at 1 HA vCPUs and 5GB HA Memory
Also, Instance1 configuration is 1 vCPUs and 5GB Memory
Instance2 configuration is 1 vCPUs and 5GB Memory

or

If Committed Use is configured at 4 vCPUs and 10GB Memory
Also, Instance1 configuration is 3 vCPUs and 6GB Memory,
Instance2 configuration is 1 vCPUs and 4GB Memory



--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/60a83128-1811-4c4f-8f48-bd9f05a084c4n%40googlegroups.com.