Why Business Intelligence Hybrid Solutions (Cloud vs On-Premise) are the Talk of the Town. Part Two.
In our previous blog, we looked at a Centralised vs Distributed model of Business Intelligence (BI) Hybrid Solutions. We’re still looking at hybrid BI solutions in this blog (Part Two), but now we’ll be focussing on the debate between cloud and on-premise solutions.
Unless you’ve had your head buried in the sand for the last 5 years, you’ll be fully aware of cloud computing and how it has been incorporated into almost every aspect of our personal and business lives. With that in mind, what does this mean for your BI implementations? Should you be using the cloud or keeping it on-premise?
Why Business Intelligence Hybrid Solutions (Centralised v Distributed) are the Talk of the Town. Part One.
What is a Business Intelligence (BI) Hybrid Solution? You might have seen this term thrown around quite a lot in the BI industry lately, and besides knowing a general definition of the word ‘hybrid’ it can be quite hard to know what is meant by it.
Make That Switch From (The) Oracle
Just recently we came across a client who was currently running their data warehouse on an Oracle 10g installation and wanted to come home to the world of SQL Server. As I am personally not a fan of Oracle at all I couldn’t fault their logic one bit, I had not however ever experienced moving and SAP DS transform from one database server to another for the same datastore and so I thought I’d look into it a little more. Let’s begin by stating the problem a little clearer and throwing up some caveats about what this posting is not.
Dogs, Guard Dogs & Toblerones
As is usually the case this blog post started life through a totally off topic conversation about whether stereotypes are always negative. My fiancee is currently taking a language degree and part of the course relates to languages & culture. When at first challenged with this question initially you DO think that stereotypes are negative; then you start to delve just a little deeper and you start to realise they are not always negative. Moreover they are actually an essential part of life as well as being an innate component of the learning process. We are born pretty much a blank slate and slowly over time our brain fills with experiences, observations and nuggets of information, it is these that inform our world view. One of the most amazing things about the human being is our adaptability, it is innate within us and allows us to hit the ground running in any of the different cultural situations we find ourselves in. There are some medical conditions that from a very early age prevent us from assimilating within a social group but in the main we are all able to cope with whatever the crucible of life throws at us. It is my belief that the blank slate approach is critical, if we had some level of pre-programming that allowed us to ‘fit in’ culturally I believe that our adaptability would be severely compromised, culture is also constantly evolving. I also believe that it would hamper our learning model to a huge degree.
SAP Data Integrator: Configuring Data Stores
One of the nice features of SAP Data Integrator that DTS just cannot compete with is how it deals with datastores at run time. For an overview let's think about how the process will normally work…
My SAP Crystal Reports Training Experience
I enrolled onto the two-day SAP Crystal Reports Introduction course run by DSCallards as a complete novice.
Upsert [sic] with SAP Data Services? Don’t cry though ...
So, recently I find myself heavily involved with SAP Data Services and data migrations, I know what you’re thinking … that's not real code! And you’re damn straight …. it isn’t, but I have always leaned heavily towards the data end of the spectrum rather than the UX end which is filled with sorcery, witch craft and more importantly users who are like little pixies with no respect for the sanctity of code; data is data though and it doesn’t press buttons marked ‘Nuclear Button, Do Not Press’ just for kicks. I thus don’t complain too much (ahem) when ETL jobs come my way. One of the biggest challenges with ETL in the SAP world is to keep everything down at the database level, it’s very easy to slip up and watch your execution times rattle up to unusable very quickly all because you used a feature for which there is no direct database equivalent and at times it is frustrating at how the simplest functions are not covered; bygones.
I find myself starting this blog, sad that I must write it. When it comes to development languages and products I am without a shadow of a doubt firmly two feet and all other associated body parts stood plum on the centre of the Microsoft camp; this has been the case since my late 20’s when I started in software. The only real difference now is that there’s a lot more of me to fit inside the camp nowadays but fit I still do. Of late I find myself heavily involved in more ETL work than true ‘development’ and so my playing field when i get distracted thus comprises off SSIS which I’ve always used (being of the Microsoft camp) and SAP Data Services which is what we sometime use in-house (being an SAP reseller). It is about these two products which I write.
Universe 'month name' Object That Orders Chronologically
If you use a month name field (or convert a month number to name), it is a string object, so orders alphabetically in a report. The report users can change this with a custom sort but this is cumbersome.
Waterfall Charts in SAP Crystal Reports for Enterprise 4.2
I've just taken a look at the new Waterfall Chart feature in CR4E 4.2 SP2. I thought the idea of tracking weight loss over a period of time would be a good visual representation of the data.
My data is very simple, consisting of a weekly period starting on the first Sunday of the week from the beginning of 2016 until the current week. I have stored the weight in kilograms and then a variance from comparing the weight loss (or gain!!!) between weeks.
Two New SAP Crystal Reports 2016 Functions
GetLowerBound and GetUpperBound
These functions work well with a Date Range parameter field. Firstly, you will need to define a parameter called 'Date Range' where Type: = Date. Ensure that 'Allow Range Values' is set to True.