Starting at 09:00 in Grand Oaks E/F... #ThickDB >>> #SmartDB

BrynLite's tweet image. Starting at 09:00 in Grand Oaks E/F... #ThickDB  >>>  #SmartDB
BrynLite's tweet image. Starting at 09:00 in Grand Oaks E/F... #ThickDB  >>>  #SmartDB

NoPlsql versus #ThickDB by @ToonKoppelaars (with slight support from me) just starting #DOAG2016 in St Petersburg.

BrynLite's tweet image. NoPlsql versus #ThickDB by @ToonKoppelaars (with slight support from me) just starting #DOAG2016 in St Petersburg.

Keynote about #thickdb paradigm by @BrynLite at #APEXCONN17 - does he accept views as part of the interface?

phsalvisberg's tweet image. Keynote about #thickdb paradigm by @BrynLite at #APEXCONN17 - does he accept views as part of the interface?

One of my slides in the webcast, with a quote (by @oraclebase) that delivers the message nicely and clearly. #PLSQL #ThickDB @oracleace

DBoriented's tweet image. One of my slides in the webcast, with a quote (by @oraclebase) that delivers the message nicely and clearly.
#PLSQL #ThickDB @oracleace

#orclapex vs JET by @DickDral at #APEXCONN17 - JET looks very promising and ready for #thickdb

phsalvisberg's tweet image. #orclapex vs JET by @DickDral at #APEXCONN17 -  JET looks very promising and ready for #thickdb

In #BigData world everybody agrees it's cheaper to bring the computation where the data locates than moving data for processing. #ThickDB


So what do you think? #thickdb or #noplsql takes most resources? @ToonKoppelaars gives answer now at #otw16 (near #oow16)

kibeha's tweet image. So what do you think? #thickdb or #noplsql takes most resources? @ToonKoppelaars gives answer now at #otw16 (near #oow16)

How does using a tool like ODI impact #thickdb? Where do we put the sql and pl/sql?


A marketing idea for @BrynLite & @ToonKoppelaars: Start calling stored procedures "database microservices" and begin a #ThickDB renaissance!


Watching @ToonKoppelaars #otw16 presentation. One of the most important Oracle presentations I've ever seen. #thickDB


What's your preferred "umbrella" term to cover all types of "do all business logic close to the data inside the database"-architectures? The term should be recognized to cover SmartDB, PinkDB or any variants thereof, no matter which RDBMS. #ThickDB #FatDB #SmartDB


Since #MLE is about code in the database, I will most probably mention #ThickDB, #SmartDB or #PinkDB.


Challenging (or really not used as much as it should be): Edition Based Redefinition. Build it into SDDM. I build an EMPLOYEE entity in a logical model and you build a relational model with EBR$EMPLOYEE base table with an editionable view named EMPLOYEE. #ThickDB @BrynLite


These slides by Peter Koletzke are really worth looking at for the implementation of your #ThickDB solution for @OracleDatabase . nocoug.org/download/2018-… nocoug.org/download/2018-… nocoug.org/download/2018-… #SmartDB #PinkDB


Jeff, *must* you? I've obeyed the Party Whip and changed #ThickDB to #SmartDB. And now you're rebelling...


What's in a name? #SmartDB #ThickDB, whatever you call it, #ORCLAPEX should be in the mix. Looking forward to talking about it on Thursday, 17 May at #GLOC18 #GLOCCLE @neooug Usually early reg's get extra swag. I'll have swag (until I run out) for anyone who reg's today-11 May!


Chris @chrisrsaxon, 'cool stuff' is subjective. Being able to use #PLSQL packages to enable a #SmartDB / #ThickDB that can simply and efficiently process huge amounts of data on @Oracle or #TimesTen is #Awesome

Who says you can't do cool stuff with PL/SQL? @mortenbraten shows you how to consume Slack APIs using it buff.ly/2CcAWBr

ChrisRSaxon's tweet image. Who says you can't do cool stuff with PL/SQL?

@mortenbraten shows you how to consume Slack APIs using it buff.ly/2CcAWBr
ChrisRSaxon's tweet image. Who says you can't do cool stuff with PL/SQL?

@mortenbraten shows you how to consume Slack APIs using it buff.ly/2CcAWBr


Ha! And make plenty of references to hashtag #ThickDB!


for SUCH things I prefer SQL translate framework. A special case of #thickDB


Would make sense to expand it, abstract it, from one specific implementation of #ThickDB technology. Always happy to support… @postgresql @EDBPostgres


If anyone is still in doubt, here's your chance to see highly convincing and thoroughly tested arguments. #smartDB #thickDB

The DB should be used as processing engine or persistence layer? At #tvdpdays @ToonKoppelaars shares his experience. buff.ly/2x010ch



Sure but nobody wants to pay Oracle Database licenses and options for non Database processing. This is why customers abandoned #ThickDB


Starting at 09:00 in Grand Oaks E/F... #ThickDB >>> #SmartDB

BrynLite's tweet image. Starting at 09:00 in Grand Oaks E/F... #ThickDB  >>>  #SmartDB
BrynLite's tweet image. Starting at 09:00 in Grand Oaks E/F... #ThickDB  >>>  #SmartDB

It's a matter of definition. I like #ThickDB. However, I’m going to be a bit lax with @BrynLite’s definition (incl. views, r/o, r/w).


1/3 I’ve been using #ThickDB because this has been in use for more than a decade. Some say that its age is enough to damn it.


ไม่พบผลลัพธ์สำหรับ "#thickdb"

Starting at 09:00 in Grand Oaks E/F... #ThickDB >>> #SmartDB

BrynLite's tweet image. Starting at 09:00 in Grand Oaks E/F... #ThickDB  >>>  #SmartDB
BrynLite's tweet image. Starting at 09:00 in Grand Oaks E/F... #ThickDB  >>>  #SmartDB

NoPlsql versus #ThickDB by @ToonKoppelaars (with slight support from me) just starting #DOAG2016 in St Petersburg.

BrynLite's tweet image. NoPlsql versus #ThickDB by @ToonKoppelaars (with slight support from me) just starting #DOAG2016 in St Petersburg.

Just starting. #ThickDB by @ToonKoppelaars in the Children's Creativity Museum.

BrynLite's tweet image. Just starting. #ThickDB by @ToonKoppelaars in the Children's Creativity Museum.

One of my slides in the webcast, with a quote (by @oraclebase) that delivers the message nicely and clearly. #PLSQL #ThickDB @oracleace

DBoriented's tweet image. One of my slides in the webcast, with a quote (by @oraclebase) that delivers the message nicely and clearly.
#PLSQL #ThickDB @oracleace

Keynote about #thickdb paradigm by @BrynLite at #APEXCONN17 - does he accept views as part of the interface?

phsalvisberg's tweet image. Keynote about #thickdb paradigm by @BrynLite at #APEXCONN17 - does he accept views as part of the interface?

#orclapex vs JET by @DickDral at #APEXCONN17 - JET looks very promising and ready for #thickdb

phsalvisberg's tweet image. #orclapex vs JET by @DickDral at #APEXCONN17 -  JET looks very promising and ready for #thickdb

So what do you think? #thickdb or #noplsql takes most resources? @ToonKoppelaars gives answer now at #otw16 (near #oow16)

kibeha's tweet image. So what do you think? #thickdb or #noplsql takes most resources? @ToonKoppelaars gives answer now at #otw16 (near #oow16)

Loading...

Something went wrong.


Something went wrong.


United States Trends