Salesforce Data 360 vs. SQL Server Integration Services (SSIS)

Great tool for client management, sales tracking, cases studies. Using is as the source of truth for all client communication. Allowing more integration options for cc and ACH payments. Right now the options are limited and only integrate with strict processing capabilities that are not always in the businesses best interest.

Incentivized

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.

Incentivized

• Allows use to bring external data into Salesforce as zero-copy
• Is able to present data using standard Salesforce reports familiar to our users
• Allows us to establish multiple relationships between our CRM data and the external data to contextualize the imported data.

Incentivized

• Standard ETL use cases for daily loads
• Loading incoming data from Vendors which is placed on FTP and adding them to the SQL Warehouse
• Creating outgoing data files and writing them to Vendor FTPs
• Easy Active Directory integration for seamless connections to SQL Server
• CI/CD by hosting the code on visualstudio.com

Incentivized

• pricing or costing visibilty, we can't estimate what would be consumption this month and suddenly we get surprised
• CI/CD can be improved, that looks a difficult and hard
• Also sandbox comes with many limitation so very hard to replicate production like environment to test

Incentivized

• 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.

Incentivized

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

Incentivized

Most of the daily use features, are very usr friendly, intuitive, every end user can learn how to manage and operate basic activities such as enter information, send an email, send a campaign, create an email marketing template, run a report on the renewals for the month, open and close a support case, create new account or a new contact, etc

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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

Incentivized

we have evaluated Snowflake, adobe rt-cdp as well. They also offer a very strong capabilities but the Data 360 is more suitable for us because of the same Salesforce ecosystem. The main key factor is without any custom code we were able to include it into our automations. And ofcourse with agentforce already in plans, we had to pick Data 360

Incentivized

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

Incentivized

• Salesforce Data Cloud has a positive impact on me as a realtor because it is easy to generate reports on customer data and see what is needed to be bumped to the next level. We have to earn a certain commission by the end of the year and it makes it easy to see how close you are
• It has a positive impact on keeping track of customers because it is nice to have it all in one place which is a nice time saver
• I like that you can even see customer info from other agents making it nice to compare and try and pass others
• Makes the customers journey smooth sailing because everything is in one place

Incentivized

• 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.

Incentivized