Posts Categorized: Technical Blog
It’s that time of the year again! Collaborate time: the world’s only user-driven, user-run Oracle conference. From April 22nd to 26th, thousands of Oracle professionals are heading to Las Vegas for a week’s worth of presentations, education sessions, networking opportunities, and who knows what else (it’s Vegas, after all!). Here is what we have planned for Collaborate 12!
If you’re planning on running Oracle VM with Amazon EC2, there are some important limitations you should know about. As part of my work getting the Oracle Linux Unbreakable Enterprise Kernel 2 working, I tried using the Oracle-supplied Oracle Linux 6 AMI images that are listed as community AMIs by Amazon. Here are my findings.
I’m going to test Oracle’s Unbreakable Enterprise Kernel out, and an obvious way to do this would be using Amazon EC2, providing high-capacity instances on demand. After some blind allies getting the Oracle Linux UEK2 kernel working with Amazon EC2 and Oracle VM, I found that I could make it work without Oracle VM, with Amazon’s default Xen hypervisor. Here are the steps I used.
Hello Friends, This is a short blog post to let you know that I am going to give my RMAN and SCAN talks to WA OUG (AUSOUG) folks in Perth next week. Here are the details:
TEMPDB, is one of SQL server hot-debated topics; there’s always something to say about its sizing, file placement or datafiles count in Multi-core instances. This is simply because TEMPDB is a global resource that’s heavily used and very critical asset in a busy instance; this makes any advice against TEMPDB fall in the “It depends” category.
Those of you who have seen me present about GoldenGate will know that I recommend using a heartbeat table to monitor GoldenGate lag. The heartbeat table is a great way to monitor GoldenGate replication because it can follow a single SQL insert through each major GoldenGate replication process, and report the replication lag attributable to each.
As we all are aware SQL Server 2012 virtual launch has arrived. Earlier I discussed what’s new in SQL Server 2012 setup, MS has released the SQL Server 2012 training kit and made it available for us to download.
I’ve been playing with SQL Server 2012, codenamed “Denali,” since the CTP days and am very happy with some of the features that they have introduced to address high availability and disaster recovery requirements. For me, these are more than enough reasons to consider upgrading to SQL Server 2012.
In recent past we had a situation where in, we were required to move MSDB, Model and Master databases to a new location, the reason being a faulty drive. While moving the system databases to the new location we needed to be extra cautious. Let’s see the process step-by-step.
The process of upgrading SQL Server is usually time consuming, costs money and requires availability of human resources. If you don’t see the immediate need…Why bother?! Before deciding on upgrading, you should be aware of the new features and make sure you will really benefit by the upgrade. From our experience at Pythian with dozens of clients and hundreds of environments, what could be worth upgrading to SQL Server 2012?
Here are some of the top features related to the database engine (Part I):