I stopped all the instance Running in my app but still Cloud SQL have a one Active connection, I have no idea why.. is that keeping the Cloud Sql Instance running.. and I'm getting charged for the hours it used.. please help
There are a few places that a flag could be set to keep the Cloud SQL instance alive.
Go to the Dev Console Your Project -> Cloud SQL -> SQL Instance -> Edit -> "Show advanced options..." -> ACTIVATION POLICY make sure its set to "On Demand".
if you are still seeing it up then:
Go here and fill out the information. Under fields select only 'settings' click execute and scroll down. Look for 'activationPolicy' and see whats set to. You can use the API browser to change the setting or gcloud
Related
I have a strange one for you. I'm maintaining several databases prior to a migration. One of them is a 2008R2 instance. This instance has multiple errors in the logs (the infrastructure has been poorly maintained), so I set up a bunch of alerts (16-25) and tried using Database Mail to send them. But the mail registry settings keep resetting and preventing it from working. I can't tell if someone is maliciously going in behind me and reverting the settings in the registry (this is possible in the poisonous environment I'm working in) or whether it's some kind of obscure problem.
Just to confirm... I've created the same alerts with the same mail settings on the 2017 instances that I'm also monitoring with no problem. Equally, on the 2008R2 instance, I can successfully set the Database Mail parameters, send myself a test email AND execute a job, sending a 'completed' email using the same Database Mail profile and user via an Operator.
Setting the parameters using xp_instance_regwrite or sp_set_sqlagent_properties didn't work either, although I realised early on that the parameters weren't sticking because of a lack of admin rights on the server, so I got the infrastructure guys to give me access. I then:
logged in to the server
shut down the Agent (it isn't doing anything at all)
configured the registry settings (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.<instance>\SQLServerAgent\UseDatabaseMail = 1, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.<instance>\SQLServerAgent\DatabaseMailProfile = <my-mail-profile>)
restarted the Agent.
I then confirmed from SSMS that the 'Mail session' parameters (Enable mail profile, Mail system and Mail profile) were correctly set. A day later, the log is full of errors, I have no emails and all of the Agent properties are empty and greyed out!
Anyone seen this before?
I have created a db instance (sql server ex) in my AWS account and now trying to access it via MS SQL Server Management Studio or via Visual Studio Server Explorer, but i can't, i get the errors like below:
I have added my ip address in inbound under security group as well:
I Tried all the above steps but didn't work. Even though, i have selected 'Publicly Accessible' while using visual studio, it didnt reflect in the aws console. So, the below steps worked for me. Please try this.
Note:- this is only for my testing/learning purposes. So, i made it publicly accessible. You might not enable publicly accessible if there is a security issue. If you are testing/using for learning purposes, you can follow the below approach.
Make sure your port is publicly accessible .Else you will not be able to connect.
To enable the public accesss, please follow the below steps.
Select the db instance --> click Modify
Scroll to connectivity Section, expand 'Additional configuration' section --> select 'Publicly Accessible'--> Scroll to bottom --> select update. (as shown below).
Your db instance will be in modifying state and after 2-3 minutes it will be available. Now, give it a try to connect again and you will be able to connect now.
My eventlog is cluttered with Package "<name>" finished successfully messages; is there any way to stop these from being added to the log?
The packages in question run very frequently and are making the eventlog harder to use
This is running from SQL Server 2008 R2 (Standard)
The job properties are set with Write to the Windows Application event log - When the job fails (and sends an email to an operator and in the corresponding maintenance plan, the settings for "Reporting and Logging" are all set with nothing checked.
And the SQL Server Agent properties are set only with the fail-safe operator; by email
For the life of me, I cannot see anywhere in SQL where I can suppress the "success" messages and would appreciate help.
I have just encountered a very similar scenario.
I have a couple of packages that are scheduled frequently. Monitoring of these non-critical packages can be managed within SQL Server Management Studio itself, I have no need to log events to the Windows Application logs.
In fact the logs are now "bloating" insofar as they are filling at a far greater pace than I am happy with.
It is possible to switch package logging on or off within the SSIS package itself.
From within BIDS (Business Intelligence Design Studio), right click anywhere within the control flow and select "Logging..." from the menu that appears.
From what I have read of this, to set your own custom logging options you have to tick the option on in the "Providers and Logs" screen and then add the "SSIS log provider for Windows Event Log" provider.
Once you have done that, you can tick options on and off within the "Details" tab. The options are all unchecked by default.
In the alternative, you could set up logging to the "SSIS log provider for SQL Server" and select the items that you do want to monitor. This then logs activity to a table called dbo.sysssislog in whichever database you configure within the provider.
You can get details on SSIS package logging here: http://msdn.microsoft.com/en-gb/library/ms181205(v=sql.100).aspx
I'm completely new to Parallel as i'm helping out someone and I want to change DNS settings to switch MX records. I don't see DNS settings anywhere, so i searched around and it says to enable DNS zone settings?? Here are screenshots.. there are no DNS settings or DNS zone settings?
How do i solve this? As you can see there are no DNS settings(zone). The account also has administrator privilege(all privileges), what is the problem?
In addition to that, the first thing you need to confirm is, whether you have installed DNS server /bind installed in Plesk,
You can check it in Tools & Settings >> Server Components
If you did not find any components for bind, then go ahead and install it from autoinstaller.
To do so either you can proceed with Tools & Settings >>Updates & Upgrades
or; Login to server as root and run /usr/local/psa/admin/sbin/autoinstaller
you need to set dns settings on your domain level where it is registered.
for example, if your domain.com is registered within godaddy then login into the account and set DNS settings there, it could be the IP of your server to the dns.
I think in godaddy acocunt, it is Domains > manage DNS of the domain
thanks
In Plesk Panel , You need to access to your domain and click Customize .
After clicking Customize - you need to access to permissions tab and select :
DNS zone management
(If granted, makes DNS service parameters act as a preset.)
First solution
Check if dns zone managment is enabled.
For a certain subscription
Subscriptions > Desired Subscription Domain > General Tab:Customize > Permissions Tab:DNS zone management
(if changed, subscription lock out of plan updates)
For entire service plan (recommended)
Service Plans > Desired Plan > Permissions Tab:DNS zone management
(subscription(s) in plan might be unlocked for syncing settings)
Image is common for these two ways in solution (PSA 12.0.18)
Second Solution
Caused by bind9 loading failure in combination with a recent upgrade.
The above DNS zone managment checkbox is missing!
A Plesk package (plesk-dns-bind-driver) depends on bind9. So you should NOT force a remove/purge of bind9 and then install again.
You also might noticed a bind9 loading failure at startup.
(not always affects PSA, but after a recent upgrade, fixing bind9 failure is necessary)
So if suddenly "DNS Settings" replaced with "Whois Information" this is your solution.
So service bind9 restart fails as expected.
Then check for an apparmor denial
# tail /var/log/syslog
...
apparmor="DENIED" operation="open" profile="/usr/sbin/named"
name="/var/named/run-root/etc/named.conf" pid=4869 comm="named"
requested_mask="r" denied_mask="r" fsuid=109 ouid=0
...
if there is something like above, then edit etc/apparmor.d/usr.sbin.named and add in
/usr/sbin/named only section
/usr/sbin/named{
..
/var/named/run-root/** rwm, #add this line
..
}
Then please do update && upgrade (you might noticed an 1 not fully installed or removed again).
After a server restart all works fine for me again!
giannisepp
I'm using the AWS Toolkit in Visual Studio 2013 to attempt to launch a new instance on Amazon RDS. I get through the wizard for creating the new instance and after clicking finish, there is a delay, and then a message appears saying:
Error launching DB instance: DB Security Groups can only be associated with VPC DB Instances using API version 2012-01-15 through 2012-09-17.
Launching different types of instances (SQL Server SE vs MySQL) doesn't seem to help, nor does selecting different versions of the platforms (SQL Server 2008 vs 2012). The only thing that gets it to go through is unchecking the box for "default" in the DB Security Groups area. However, I feel like something is going on here that shouldn't be happening.
Can anyone explain why this is happening and how I can resolve it other than by not setting a default security group? Thank you.
If you created your AWS account recently, you will be using a VPC by default.
It sounds like the API the plugin is trying to use hasn't been updated. The latest version is 1.5.6, and looking at the history it seems like some of these features were added in 1.5.0.
I finally solved it! Since I couldn't use the API that the VS 2013 plugin uses, I had to manually add my IP to the Security Group created for my Elastic Beanstalk.
Go to the console, ec2's security groups configuration
Find the one which description matches your Beanstalk (e.g.: Security Group created for Beanstalk Environment to give access to RDS instances)
Hit Inbound, Edit and add a new rule for All Traffic (I guess HTTP should be enough, but just in case).
In Source, select My IP and Save.