SPSS Statistics is a software package used for statistical analysis. It is now officially named "IBM SPSS Statistics". Companion products in the same family are used for survey authoring and deployment (IBM SPSS Data Collection), data mining (IBM SPSS Modeler), text analytics, and collaboration and deployment (batch and automated scoring services).
$99
per month
Microsoft BI (MSBI)
Score 8.4 out of 10
N/A
Microsoft BI is a business intelligence product used for data analysis and generating reports on server-based data. It features unlimited data analysis capacity with its reporting engine, SQL Server Reporting Services alongside ETL, master data management, and data cleansing.
Microsoft BI is very well suited to implement reporting and visualization within departments. Choosing Microsoft BI over tools like Tableau is the variety of third party apps it extracts data from. This functionality is limited in Tableau as it digests data from large data …
SPSS is well-suited for the following: 1) User Behavior Analysis: SPSS handles large datasets to analyze user behavior data. 2) Customer Satisfaction / Foundational Surveys: SPSS facilitates analysis of quant data from satisfaction surveys, keeping us informed about customer needs and preferences. 3) A/B test analysis: SPSS statistical tools for A/B test analysis, which helps optimize user experience of our products. Scenarios where SPSS are less appropriate: 1) Qualitative Data Analysis: I do not use SPSS for open-ended survey responses/qual data. 2) Live/in-vivo data analysis: SPSS is not ideal for real-time data processing. 3) Complex Data Integration: SPSS isn’t the best fit for complex data integration tasks
Microsoft BI is well suited for Stream analytics, easy data integration, report creation and UI/UX designs (limited but what all available are great ones) Microsoft BI may be less appropriate for handling huge number of datasets and difficult queries. It may also be difficult for a company with heavy data.
SPSS has been around for quite a while and has amassed a large suite of functionality. One of its longest-running features is the ability to automate SPSS via scripting, AKA "syntax." There is a very large community of practice on the internet who can help newbies to quickly scale up their automation abilities with SPSS. And SPSS allows users to save syntax scripting directly from GUI wizards and configuration windows, which can be a real life-saver if one is not an experienced coder.
Many statistics package users are doing scientific research with an eye to publish reproducible results. SPSS allows you to save datasets and syntax scripting in a common format, facilitating attempts by peer reviewers and other researchers to quickly and easily attempt to reproduce your results. It's very portable!
SPSS has both legacy and modern visualization suites baked into the base software, giving users an easily mountable learning curve when it comes to outputting charts and graphs. It's very easy to start with a canned look and feel of an exported chart, and then you can tweak a saved copy to change just about everything, from colors, legends, and axis scaling, to orientation, labels, and grid lines. And when you've got a chart or graph set up the way you like, you can export it as an image file, or create a template syntax to apply to new visualizations going forward.
SPSS makes it easy for even beginner-level users to create statistical coding fields to support multidimensional analysis, ensuring that you never need to destructively modify your dataset.
In closing, SPSS's long and successful tenure ensures that just about any question a new user may have about it can be answered with a modicum of Google-fu. There are even several fully-fledged tutorial websites out there for newbie perusal.
It would be beneficial to have AMOS as part of the SPSS package instead of purchasing it separately.
It would be beneficial to have other statistical tests, such as PROCESS, be part of the standard SPSS tests instead of having the need to run a syntax to have it installed.
My dataset tends to be smaller, and I have never had any issues with using SPSS. I heard that SPSS may not be optimal when handling large datasets.
The race to perfect gathering of Non-Traditional datasets is on-going; with Microsoft arguably not the leader of the pack in this category.
Licensing options for PowerBI visualizations may be a factor. I.e. if you need to implement B2C PowerBI visualizations, the cost is considerably high especially for startups.
Some clients are still resistant putting their data on the cloud, which restricts lots of functionality to Power BI.
Both money and time are essential for success in terms of return on investment for any kind of research based project work. Using a Likert-scale questionnaire is very easy for data entry and analysis using IBM SPSS. With the help of IBM SPSS, I found very fast and reliable data entry and data analysis for my research. Output from SPSS is very easy to interpret for data analysis and findings
Microsoft BI is fundamental to our suite of BI applications. That being said, Northcraft Analytics is focused on delighting our customers, so if the underlying factors of our decision change, we would choose to re-write our BI applications on a different stack. Luckily, mathematics are the fundamental IP of our technology... and is portable across all BI platforms for the foreseeable future.
Probably because I have been using it for so long that I have used all of the modules, or at least almost all of the modules, and the way SPSS works is second nature to me, like fish to swimming.
The Microsoft BI tools have great usability for both developers and end users alike. For developers familiar with Visual Studio, there is little learning curve. For those not, the single Visual Studio IDE means not having to learn separate tools for each component. For end-users, the web interface for SSRS is simple to navigate with intuitive controls. For ad-hoc analysis, Excel can connect directly to SSAS and provide a pivot table like experience which is familiar to many users. For database development, there is beginning to be some confusion, as there are now three tool choices (VS, SSMS, Azure Data Studio) for developers. I would like to see Azure Data Studio become the superset of SSMS and eventually supplant it.
SQL Server Reporting Services (SSRS) can drag at times. We created two report servers and placed them under an F5 load balancer. This configuration has worked well. We have seen sluggish performance at times due to the Windows Firewall.
I have not contacted IBM SPSS for support myself. However, our IT staff has for trying to get SPSS Text Analytics Module to work. The issue was never resolved, but I'm not sure if it was on the IT's end or on SPSS's end
While support from Microsoft isn't necessarily always best of breed, you're also not paying the price for premium support that you would on other platforms. The strength of the stack is in the ecosystem that surrounds it. In contrast to other products, there are hundreds, even thousands of bloggers that post daily as well as vibrant user communities that surround the tool. I've had much better luck finding help with SQL Server related issues than I have with any other product, but that help doesn't always come directly from Microsoft.
I have used on-line training from Microsoft and from Pragmatic Works. I would recommend Pragmatic Works as the best way to get up to speed quickly, and then use the Microsoft on-line training to deep dive into specific features that you need to get depth with.
Have a plan for managing the yearly upgrade cycle. Most users work in the desktop version, so there needs to be a mechanism for either pushing out new versions of the software or a key manager to deal with updated licensing keys. If you have a lot of users this needs to be planned for in advance.
We are a consulting firm and as such our best resources are always billing on client projects. Our internal implementation has weaknesses, but that's true for any company like ours. My rating is based on the product's ease of implementation.
I have used R when I didn't have access to SPSS. It takes me longer because I'm terrible at syntax but it is powerful and it can be enjoyable to only have to wrestle with syntax and not a difficult UI.
We have used the built in ConnectWise Manager reports and custom reports. The reports provide static data. PowerBI shows us live data we can drill down into and easily adjust parameters. It's much more useful than a static PDF report.
As a SaaS provider we see being able to provide self-service BI to our client users as a competitive advantage. In fact the MSSQL enabled BI is a contributing factor to many winning RFPs we have done for prospective client organisations.
However MSSQL BI requires extensive knowledge and skills to design and develop data warehouses & data models as a foundation to support business analysts and users to interrogate data effectively and efficiently. Often times we find having strong in-house MSSQL expertise is a bless.
