Skip to main content

Always Free Autonomous Oracle Database: Let's get going!

On September 16, Larry Ellison announced a new Always Free tier for Oracle Cloud, which (for me) most importantly includes an Always Free Autonomous Oracle Database.

For nothing but the "cost" of providing your credit card information (which is only used for identification purposes and is henceforth ignored until you decide to upgrade to a paid service), everyone in the world now can use the most powerful, most advanced database in the world FOR FREE.

Of course, there are limits. But oh my what generous limits they are!

 Get lots more details here.

And it's not just the amazing Autonomous Database (in both transaction processing and data warehouse flavors).

You get Oracle Application Express (APEX) so you can build websites writing very little code, and taking full advantage of your SQL and PL/SQL skills.

You get SQL Developer to write what code you need and manage your database.

You get Oracle Rest Data Services to build REST endpoints against your database.

And if you happen to write in Python or Javascript (Node.js) or Java or....the drivers are also there for you. Wow!

Now, I must confess, I've never had trouble getting access too a free Oracle Database. I've been working for Oracle or Oracle partners since 1987. But running my own little database on my laptop for my own experiments is so different from having access to a self-managed database on the Internet that I can use to build my own websites.

Oh my - the ideas I have bubbling around in my head!

As some of you may know, I have gotten very concerned about climate change and human-caused extinctions. That's why I founded fabe - for all a beautiful earth - with Vincent Morneau last year. That's why we are building the fabe app to make it easy to reduce consumption and rescue species.

But I am also - more locally - somewhat obsessed with rescuing native trees and other living things from the human-driven scourge of invasive species. So I am starting up a Carrboro Tree Rescuers group here in town.
And now I can also easily build a website for this initiative.

And then even more personal, family-oriented websites to help us all stay connected.

And...and...

Well, what are you waiting for? Visit https://www.oracle.com/cloud/free/ and sign up now.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...
4 comments
Read more