As we all know proper use of bind variables in SQL statements is a must to make transaction processing applications scalable. So how do we find the queries that don’t use bind variables and have to be parsed each time they are executed? There is number of ways, but this article is all about the most effective way I know. If you have a better one – let me know please!
The era of datafication is here, businesses today are fully dependant on data. The Question is, Is your business ready?
Wouldn’t it be nice if there was a way to flip block and postfix statements with the ease of a single command? Well, I thought so, so I came up with a dirty little script, have a look.
This post should give you some insights into the risk that your databases are in by switching to the bulk-logged recovery model. So, what do you need to do to avoid this risk? Make sure that you run a backup immediately after the transactions you are running under the bulk-logged recovery model complete.
I describe AlwaysOn Availability Groups as a “database mirroring configuration sitting on top of a Windows Failover Cluster infrastructure.” Why do I say this? It’s because I want SQL Server DBAs to leverage what they already know on features like database mirroring and failover clustering and apply them when dealing with AlwaysOn Availability Groups.
Following my “Building Integrated DWH with Oracle and Hadoop” webinar for IOUG Big Data SIG, I got a bunch of excellent follow up questions. The most frequently asked questions are: What is the minimum I need to do to get started with Hadoop? and How do I load data into Hadoop? Since so many people are interested in the same question, it makes more sense to answer on the blog.
Sky’s the limit for the database bloggers. They are producing awesome rants in Oracle, fabulous ramblings in MySQL, and fantastic views in SQL Server, and this Log Buffer Edition, very proudly covers all that in Log Buffer #303. Enjoy.
I recently helped setup an Exadata X2-8 Database Machine with the latest version of OEM Cloud Countrol (188.8.131.52). A few documents do exist for this process. However I found a few inconsistencies and problems; I think the existing documents I found were written on older versions of OEM and older versions of the tools. I’m publishing my final procedure here with hopes that it helps you, but as always please cross-reference this with the appropriate documentation before doing anything in your own environment.
No its not cloud or engineered system or JBOD, if you are wondering. Surely, it can be any of those thing, and anything else. It really doesn’t matter if your data resides in good, reliable, always-there hands. So what’s the destination of choice in this brand new year? Keep reading to find out.