Salesforce CRM Analytics (formerly Tableau CRM) is a cloud-based business intelligence solutions and analytics software. It provides users with automated data discovery, CRM-connected analytics, top-down views of data, augmented analytics, predictive insights, and customizable data visualization tools.
$125
per month
SSIS
Score 7.6 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Salesforce CRM Analytics
SQL Server Integration Services (SSIS)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Salesforce CRM Analytics
SSIS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Salesforce CRM Analytics
SQL Server Integration Services (SSIS)
Considered Both Products
Salesforce CRM Analytics
No answer on this topic
SSIS
Verified User
Director
Chose SQL Server Integration Services (SSIS)
Alteryx Designer is easier to use for machine learning models. The functionality of drag and drop is the most valuable. It is a very user-friendly tool that can be understood easily. My teams also work with other solutions, such as Integration Services, and these solutions are …
For us it really comes down to that book management and next best contact for our advisors. When we're thinking about a book of business that may range, depending on the advisor, from 400 clients to a thousand clients, how do they really optimize their time? Who do they call next? Who do they work with to make sure not only they're keeping those clients engaged, they're not leaving the firm going to other advisors who they haven't talked to in a while who might need their attention. That's really where that CRM analytics is really proven pretty powerful for us.
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
Implementation takes time and resources. It is a heavy lift to implement and at first, it can take a little bit of time to understand what you are looking at. But once it's implemented it's easy to get started.
Without any BI expertise or resources available to your organization, the implementation of this is difficult. If you aren't used to BI tools and don't have an expert in house, the terminology can be difficult to understand at first.
Their support is not on hand to help you if you encounter any issues, at least not on all the plans or the basic plans. Real-time support service is an add-on, so you'll need to be patient if you require help or pay extra money.
More functionality for the tool is needed to compete with other heavyweights in the arena like Tableau, Qlik, and Microstrategy. Still lacks the robustness, functionality, and flexibility other competing products possess.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
For someone who don't have coding background, this could be a useful tool and fairly easy to learn and use given the good support. However, if you know other open source tools, it would be much easier to use the other tools and the knowledge is more transferable in the future.
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
I was not able to be in interaction much with Salesforce support team since every feature works the way it should be working. So far I have not experienced any bug or major glitches that would delay the result of my work and performance. There is also a hotline in our company for Salesforce issue but so far I have not used it.
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
An implementation partner would certainly result in greater output in a more efficient amount of time. However, I have found implementation partners to be extremely expensive for the output received (at least working for a non-profit company they are frequently unaffordable). Internal implementation does help with usable output though since internal knowledge would better know the data architecture and business processes
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
Tableau is the absolute top of the class when it comes to business intelligence, but it doesn't make sense for every business case. In our case, we needed a simple data visualization platform for our CRM platform and sales pipeline. Salesforce Analytics, while nowhere near as robust, did the job we needed it to do perfectly in a significantly more cost-effective manner.
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
I would say it's been positive just because as a company, anyone that has access to it can go in there and pull any company information and we're very up to date then on all of our client base. So I would say it's been a very positive impact.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.
