Showing posts with label Microsoft. Show all posts
Showing posts with label Microsoft. Show all posts

Tuesday, July 5, 2016

Don't be so closed minded.

Industry changes.  Tools change and they become better.  Competitors add enhancements and this forces the rest of the industry to adapt.    One of the platforms that have worked to continuously improve is Microsoft SQL Server.   If you look over the years at the roadmap for this tool, you will see a robust platform that prior to 2008, you would have probably not appreciated.   Microsoft is now steering the industry.   Check out Microsoft BI, integration with SharePoint, etc.   But this is not a blog about Microsoft, it’s a blog about mindsets.  

My boss here at my current engagement is a strong advocate for the AS400.   The industry has walked around the AS400 and IBM.  We have moved to other platforms.  Right? I mean the AS400 is old school, right.   That's state of the art 1988 tech, right?  But it turns out that the AS400 is a stable platform that still exist in many businesses today.  They continue to refine and get better and now they have the I Series.  Great failover, great stack of redundancy, security.  I know what you're thinking.   It's not cool, it’s not new.   What is your goal?  Is it new tech or stable tech?  But this is not a blog about the AS400 either. 

Don't pass over the tools.   Tableau is for data mining, correct?   Qlik is for dashboards, correct?   Cognos is for reporting, correct?   I think if you look at Tableau, you will see that they have enhanced that tool to collaborate.  To share online.  Publish a report online with the click of a button.  

Back in 2005, MS SharePoint was a collaboration tool primarily used as a document repository.   But behind the scenes, you can create portals and web pages that envy others.   Think about this.   Stop looking at how you used the tool at your previous employer and start to think about how this tool can be used today by my current employer.   Look at price.  Use your analysis experience to look at tools in different ways.  Find out if your bias are warranted or not?  Be open to new ways of doing things.  Tunnel vision is limiting to you and your company.   

Thursday, March 12, 2015

Upgrading from SQL 2008 to SQL 2012

One of my clients was upgrading from SQL server 2008 to SQL server 2012.  I want to describe some of the items to look out for when migrating.  In this case, the client had already installed a new virtual environment so the infrastructure was in place.   Now what


  1. Freeze all changes on production - At some point you are killing yourself if you are trying to migrate one set of reports, packages, and jobs that are consistently changing.   
  2. Analyze what packages are currently being used and what packages can be sunset.  Analyze what jobs can be used and what jobs can be sunset.  If any of the jobs send data to another system, attain the contact name for that data for testing after migration.  Analyze what procedures you currently use and what can be sunset.
  3. Determine who the business users of the reports are.  Analyze what reports are being used and what can be sunset.
  4. Create your timeline.  (Remember that not all jobs are created equal.  Some jobs have 1 step and others have 101 steps.  Don't overload one developer with a one step job to the same timeline as the developer with the 101 step job.)
  5. Allow time for testing by peers of the jobs,packages and procedures.
  6. Also note that SQL 2012 is not as forgiving on package performance as SQL 2008.   In 2008, you can have a package that performs 50 tasks and it works just fine.  However in 2012, the packages need to be broken up into fewer tasks.  Suffice it to say, that you need to allow time to peformance tune the data warehouse cycle.   Some of this testing has to happen in production.   
  7. Allow time for Pre-UAT by your IT team
  8. Allow time for UAT by the business teams

Best of luck in your migration/upgrade.   As a follow-up, the upgrade to 2012 is great for the business.  My clients business users love Power Pivot and this also opens up some Power BI capabilities as well for Sharepoint solutions.