The Snowflake Cloud Data Platform is the eponymous data warehouse with, from the company in San Mateo, a cloud and SQL based DW that aims to allow users to unify, integrate, analyze, and share previously siloed data in secure, governed, and compliant ways. With it, users can securely access the Data Cloud to share live data with customers and business partners, and connect with other organizations doing business as data consumers, data providers, and data service providers.
N/A
SSIS
Score 8.2 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
Fivetran, Stitch, and Etleap are all 1000x more modern than SSIS and 100x less aggravating. While those tools are mainly used to sync data rather than transform it, the ELT model works much better than the ETL model in most situations.
SSIS is similar to Alteryx and Informatica PowerCenter in a way because these are all drag-and-drop ETL tools with similar functionality. Alteryx is a step ahead because it has some advanced ETL functionalities including statistical calculations etc. and a better ability to set …
I am over our HR data, and we use Workday for our HR management system. I have a script in place that runs reports on Workday and saves the results as CSVs. I can then use stages in Snowflake to insert these CSVs into Snowflake, then I can insert or truncate and replace these staged tables into a final schema. Then once these are in a schema I can reference them and build out my data models. In addition to ingesting CSVs, Snowflake has the ability to write a CSV file to our Amazon S3 bucket. Ingesting these CSVs, transforming the data, then delivering it to a destination would've involved so much more coding than my current process if we were on any other platform.
There are always alternative options available to meet the demand for integration. In my opinion, SQL Server Integration Services has a wide variety of capabilities that makes it a very versatile tool for developing dependable integration strategies. When determining which tools to utilize, vendor interfaces may play a significant role, and technologies like PowerShell have been used by colleagues to aid in this decision. For even more user-friendliness, our SSIS solution additionally makes use of a third-party plugin.
Snowflake scales appropriately allowing you to manage expense for peak and off peak times for pulling and data retrieval and data centric processing jobs
Snowflake offers a marketplace solution that allows you to sell and subscribe to different data sources
Snowflake manages concurrency better in our trials than other premium competitors
Snowflake has little to no setup and ramp up time
Snowflake offers online training for various employee types
This tool is very much technical and proper knowledge is required, so mostly you have to hire an IT team.
I wish if various videos could be available for basic quires like its initiation, then I think it would act as a guideline and would help the beginners a lot.
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.
SnowFlake is very cost effective and we also like the fact we can stop, start and spin up additional processing engines as we need to. We also like the fact that it's easy to connect our SQL IDEs to Snowflake and write our queries in the environment that we are used to
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
The interface is similar to other SQL query systems I've used and is fairly easy to use. My only complaint is the syntax issues. Another thing is that the error messages are not always the easiest thing to understand, especially when you incorporate temp tables. Some of that is to be expected with any new database.
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.
We have had terrific experiences with Snowflake support. They have drilled into queries and given us tremendous detail and helpful answers. In one case they even figured out how a particular product was interacting with Snowflake, via its queries, and gave us detail to go back to that product's vendor because the Snowflake support team identified a fault in its operation. We got it solved without lots of back-and-forth or finger-pointing because the Snowflake team gave such detailed information.
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.
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
I have had the experience of using one more database management system at my previous workplace. What Snowflake provides is better user-friendly consoles, suggestions while writing a query, ease of access to connect to various BI platforms to analyze, [and a] more robust system to store a large amount of data. All these functionalities give the better edge to Snowflake.
I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with traditional scripting. Comparably free, but my own familiarity with trad scripts would be my final deciding factor. Perhaps with some further training on SSIS I would have a different answer.
Positive impact: we use Snowflake to track our subscription and payment charges, which we use for internal and investor reporting
Positive impact: 3 times faster query speed compared to Treasure Data means that answers to stakeholders can be delivered quicker by analysts
Positive impact: recommender systems now source their data from Snowflake rather than Spark clusters, improving development speed, and no longer require maintainence of Spark clusters.
