Most folks working with SQL DBs for a while will likely come to see how beginners in this area struggle with “declaritive code” and “tell the DB what you want not how to do it” In my experience, this issue stems partly from the way SQL is tought – examples are often way too simplistic … New year, same issues and some tips.
There is one predominant reason for why databases and database technology get a spot in the conversation of “the business”: performance.Understanding system performance and coming up with ideas for improving it typically requires a form of end-to-end understanding with different levels of detail insight on how a query from a client application is processed by … How to know “all these things”
For many BW performance relevant DB-features, it’s really all about the details of usage and implementation when it’s about the effect of those features. The following are two examples of rather small things that went wrong which had a big impact on the system performance. Two examples for BW on MaxDB The first two examples … Small changes with big effects
People use assumptions to make decisions. They do this all the time and insofar, developers are people as well 🙂 To be a bit more specific, also database developers make assumptions, One of them is for example that when you query data then you ask for data that is actually there. You want to get … MaxDB weekend magic – save 50% total storage space!
Ok, MaxDB is most often used with a NetWeaver on top of it, so this blog is about a niche topic of a niche product. Wow – that should be enough understatement and un-buzzing for now. The question of how and when to collect new optimizer statistics pops up every now and then. Most people … MaxDB Optimizer Statistics handling without NetWeaver
One of the most important analytical tools used to investigate slow running SQL statements is the well-known ST05 – SQL trace. The idea of it is that the ABAP database interface notes down what SQL statement it sends to the database, how long it took to get the result, what selection criteria were used and … MaxDB ST05-trace fallacy – when sometimes the trace is wrong…
Infrastructure software like RDBMS often tends to become feature-rich in many directions. MaxDB is no exception to this, so by reading the documentation there’s a pretty good chance to dig out some features that are rarely seen or used. One example for this is the MaxDB database event dispatcher. It has been around for quite … MaxDB Event Dispatcher Intro
As I promised here’s the second part of my short excurse into the shoals of lock management with MaxDB databases. (The first part can be found MaxDB – On locking mechanisms and how we get to know our MaxDB a bit better each day… Part I) 2) When deadlocks go unnoticed… Ok, big buzz word … MaxDB – On locking mechsanisms and how we learn something new each day… Part II
One of the most boring topics within the area of DBMS surely is locking. It’s also one of the topics that most DB users try to avoid as much as possible. Still, it’s utmost important to correctly understand how locking works in the database of choice to be able to work successfully with it and without bad … MaxDB – On locking mechanisms and how we get to know our MaxDB a bit better each day… Part I
From time to time I start to believe that there are certain problems that would not come up anymore, once the topic is documented well enough. My colleagues from the development know that too well as I’m asking for documentation and notes all the time for everything. However, the written documentation does help nothing if … Questions to SAP-Support (MaxDB): “Data is gone after reboot – where the heck is it?”
