It's be a couple of days since I got it to do the simplest of tests.
One of the requirements, when I signed up, was to add a billing method.
Now, I owe, Google says.
Dec 1, 2013 - Dec 31, 2013
|
$0.75 | $0.00 | $0.75 | |
| Dec 1 - Dec 31 |
Google SQL Service IP address idling - hour: 30 Hours (Project:559850647429)
|
0.30 | 0.75 | |
| Dec 1 - Dec 31 |
Google SQL Service D0 usage - hour: 16 Hours (Project:559850647429)
|
0.40 | 0.45 | |
| Dec 1 - Dec 31 |
Google Compute Generic Micro instance with burstable CPU, no scratch disk: 124 Minutes (Project:559850647429)
|
0.04 | 0.05 | |
| Dec 1 - Dec 31 |
Google SQL Service Disk Usage: 0.062 GB-month (Project:559850647429)
|
0.01 | 0.01 | |
| Dec 1 |
Starting balance
|
0.00 | ||
Nov 1, 2013 - Nov 30, 2013
|
||||
| No transactions for this date range | ||||
Oct 1, 2013 - Oct 31, 2013
|
||||
| No transactions for this date range | ||||
It was not entirely clear what I'd be paying for with these services.
There was the SQL service.
And there was the Compute service.
And there was a the use of a static IP address.
Each was only supposed to cost a few cents, possibly only when they were being "used" or possibly by the hour. Honestly, it was kind of confusing, and I figured it wouldn't cost much to experiment.
I chose the least expensive options which offered the least amount of resources (GB of memory for storage and computing).
I cancelled the Compute service almost immediately because it just seemed like a difficult-to-connect-to web server. I opted to use my own web server for the SQL connection test; which worked fine.
Other than that, I've done nothing.
So, the pennies are adding up.
75 cents for just a couple of days of inactivity -- I imagine that ends up being hundreds of dollars per year.
Thinking this is not worth the cost, right now, since I'm not selling anything or offering AdSense any space.
I could disconnect the static IP, but then what good is the SQL account if you can't connect to it remotely?
No comments :
Post a Comment