• Deleted.

  • You lose what you don't use. This is what is true for most. But, that depends on the person.

    When it comes to the BI stack. Yes, you can either clean and conform all the data to what the business needs so you don't have to worry to much on the IT side of things, or you can move a lot of those problems to the front-end so the end users have to try to work magic in these apps to make it work. They are the same problems, just either in the front or in the back. Most would prefer it being in the back because most of the end users using these apps are not as tech savvy.

    Personally, I like a mixture of both. I like a pretty flexible wide and large model that is enough to do anything. It's not exactly what you need, but it's not exactly what you don't need. But this greatly depends on the business. If there is an enterprise application being built and a standard needs to be established, then it needs to be set in stone, everyone agrees and you push forward.

    Outside of that, everything else you are mentioning is not really a thing. The business is going to do what the business is going to do regardless of your personal feelings and flavors. You're either a good problem solver or you're not. You either enjoy BI regardless of the stack or you don't. You can't go out there saying the jack of all trades when all you are looking at is the Microsoft stack. Focus on what BI really means, not what brands you like to use.

    Hope that helps.

  • Deleted.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply