Truncate is useful in some serial batch processing but it breaks the read-write consistency, generates stranges errors and results for running selects, and it needs DROP ANY TABLE when run over a table that you do not own.
But also, DELETE is faster in the following test case.
In 12c, you could have over one million partition in a table, but for the sake of the universe, I’ll try with 10000.
This is mainly a note to myself to save me from looking up the details very time I need it. I can just go to my own post. To use Autotrace in SQL you need to grant the schema the PLUSTRACE role. But in SQL Developer you need the PLUSTRACE role that has a few additional privileges. Connect to SYS as sysdba and run the following.
Oracle MySQL – News, Monitoring, Diagnostic and Backup
Event Oracle MySQL (Session in French) – Lausanne / 29.09.2015
You work on MySQL and your needs evolve? ORACLE and dbi services invite you to a workshop dedicated to the monitoring, the diagnostic and the backup of your MySQL databases. We look forward to meeting you there!
Until very recently I had really believed the marketing hype and sales pitch about how in 12c database upgrades are so much faster and easier than earlier releases – just unplug the PDB from one container and plug it in to another container and bingo you have an upgraded database!
Partly true …. maybe about 20%!
As Mike Dietrich from Oracle Corp. has rightly pointed out on his great blog (http://blogs.oracle.com/upgrade),it is not as straight forward as pointed out in slides seen I am sure by many of us at various Oracle conferences showcasing Oracle database 12c.
Yet another compiler anomaly; two solutions for exercises posted these days
Reverse engineering exercise #6 (for x86, ARM, ARM64, MIPS)
Encrypted database case #1
Did you ever have one of those déjà vu moments when you are working in SQL Server and you swore you already addressed an issue? This has happened to all of us, and working in SQL Server every day, I’ve certainly had my fair share of SQL déjà vu.