It is not complex. It is straightforward. It is a very simple database anyway. It is just having a script and running them. 

The only thing is that you have to go through the whole nine yards of getting an account or getting your single sign-on enabled. That is a part of every process. For any single sign-on application, you will have to go through this process. 

You also need to involve the right people, such as the security team, infrastructure team, and networking team. When they are there, the setup becomes easier, and there are no problems.

For its maintenance, we have only two or three people. We have one DBA and one account admin. There is another DBA who will take a rotation. You don't really need a big team to manage this because it is all cloud. Management is not that heavy.

The solution is straightforward. 

My Azure ID was created by the DBA. As soon as I had to log in, my user role was set up. To log in to the interface hardly took me more than two or three minutes. Compared to our Data Bricks, it was pretty simple. It's hassle-free. 

The maintenance of the DBs and the production services are normally taken care of by the team itself who's handling the production support. However, just in case, if there is something, if a huge mishap happens, which we cannot recover, or we would need Snowflake customer support help, that is when the help is taken. Otherwise, the team handles everything in-house. 

The majority of the cases that we have seen are some queries stuck somewhere and out of the blue. In the case of some source data, it decides to send you a huge amount of data on a particular day. While we have seen some mishaps, a regular case requires our developers to deal with it.

The initial setup was very straightforward. 

There is no setup issue at all. It's very smooth. You need to do a simple login. If you're doing the initial setup, it's maybe a couple of days of work. That's it. If you are migrating or want to do a proper new database setup, it's just a day's work.

The initial setup was simple and took about a month. The main point is to align the data governance and integration process because you only need to click a button to start. We had a service engineer from Snowflake help with that.

The initial setup was pretty straightforward. The permissioning is a little more complicated than it needs to be. It would be nice if it just assumed permissions when you create new tables or new users, but you do have to go and actually permission to everything for individuals and people rather than when you create something. It's just because there's no default role that applies to new stuff created so it's a little more complicated than it should be.

Our deployment took about one month. I'm the only one involved in the maintenance of the solution now.

We're migrating from Oracle right now. We have two people that handle the maintenance of the solution. A company may need two to four engineers to manage maintenance 24/7.

It's not difficult to deploy. It's pretty straightforward. It took us only a couple of minutes in order to get everything up and running. 

The solution is cloud-based. There is no on-premise solution. It has its own cloud. The installation is quite easy.

I would rate the initial setup process an eight, on a scale from one to 10, with one being the worst and 10 being the best.

The initial setup was straightforward; it was one of the easiest I've done, so I rate the solution five out of five for ease of setup.

I rate the ease of setup a seven or eight out of ten. The tool is deployed on the cloud. The time taken for deployment depends on the workload and how we build it.

The initial setup is not difficult. Google Search will lead us to articles that can guide us on the setup of users, roles, warehouses, and access controls.

The implementation process was pretty straightforward. I didn't set it up, though. I used an already set up version. I just had to connect. I had to push data from Azure to Snowflake, create tables there, and have data loaded into those tables, and that's it. I wasn't doing anything else, so I didn't work on the infrastructure of Snowflake.

You would need a group of two or three people to maintain the product.

 The initial setup was straightforward.

I would rate it a three out of five in terms of complexity just because we didn't have any Snowflake developers that were available. The implementation took about three months.

The deployment model is delivered as a service. So the most deployment you have to do yourself is by deciding which cloud provider and region you want it to be hosted in. But Snowflake will actually host it themselves, so there's no deployment beyond clicking from a dropdown and clicking okay, and it'll magically appear.

Moreover, it's very easy to maintain because it's delivered entirely as a service. Snowflake takes care of all the patches, upgrades, maintenance, security tweaks, etc.

The initial setup process was not that complex and it took around six months.

It was very straightforward.

It is not too complex. Its implementation is easy even for those people who don't know Snowflake and are coming from other environments, such as Oracle or SQL Server.

It can be implemented very quickly. Our customers in Israel implemented it very quickly. It was much faster to implement than other platforms.

The initial setup is straightforward. I give the setup an eight out of ten.

A basic implementation is quick and we only have to set up Snowflake and the cloud service. We need one engineer and one designer for the implementation.

The complexity of the initial setup of Snowflake depends on the use case. However, Snowflake itself, we don't set it up. The difficulty comes from the ingestion patterns, depending on what data I'm putting in, what kind of enrichment, and what additional value we have to add. However, it does tend to get complex because we have a lot of semi-structured data which we need to handle in Snowflake. There have been some challenges.

Snowflake has multiple implementations. For example, it can be implemented on Amazon AWS and on-premise. The data between these two cannot work together because they have different time zones. That's where the integration can be difficult because it is similar to them being on separate islands, they are completely separate. At some point, everything is going to go into the Amazon AWS Snowflake, but right now there are two islands that are completely different. We have to pull the data out and send it out again separately through a different pipeline.

In the future, this type of implementation should be easier. The integration could be better. 

Yes. No hardware or server config is needed. Just create a user account.

The initial setup was straightforward.

It is straightforward. To expose the data in the cloud, we had to go through our info security and legal, so that's the part that took time. After that is done, the process for setting up the platform, getting signed up with the initial free credits, and signing up the licensing for the credits was straightforward.

The initial setup is very straightforward. You simply log in and start using it.

When it comes to deployment, you can choose between the AWS and Azure cloud. We chose AWS.

The solution’s initial setup is comparatively easier.

I give the initial setup a seven out of ten for ease and time required.

Snowflake has an easy setup and it is quick.

It's straightforward. You have to have a rule, database names, and a schema name.

When somebody deploys it and gives me the URL and the required tables to use, I use the URL and configure it from the frontend side, reporting side that could be more like Power BI or Tableau, and I start using it.

The initial setup of Snowflake is straightforward. To set up the ETL pipeline, pull the data, and then generate the reports takes approximately two hours, end to end.

Its initial setup is very simple, which is its plus point. It is not at all a problem. You only need to understand a bit of the cloud ecosystem. When Snowflake is on Azure or AWS, you need to understand

• What exactly is happening?
• How these two are handshaking with each other?
• What part Snowflake is playing?
• How Azure or AWS is complementing it?

If these things are clear, the rest shouldn't be a problem.

Its setup was easy. You can create a connection and be up and running within half an hour.

It is straightforward. It is not that complex.

Setting up Snowflake isn't complex. I've not seen any challenges.

The solution’s setup is easy since it's a SaaS product. The tool’s deployment is fast and wouldn’t take more than two minutes.

It was a cakewalk. The biggest thing that's hard to do with it is that you have to do an analysis of performance over time to determine the scale because they separate compute and storage.

Scaling the query to a proper size compute is the larger aspect of the problem for most people. That's because you're looking at something completely different. The problem is that you're now trying to figure out what is the largest compute you need to keep performance where you want it without going too large. If you were in an on-prem scenario, you would tweak and twaddle all the dials. You might rewrite the query, but at the end of the day, you're still working inside the same physical acquisition or same physical resources, whereas in Snowflake, you're literally saying that you've got a 10 million row table as part of your query, but what is the necessary compute facility that you need to run queries that are running against that table.

The advantage of Snowflake is that it's easy to deploy and they take care of the setup. Basically, it's a cloud warehouse and doesn't need to be registered on any website. It's easy. It just requires dedicating space and registering. It shouldn't take more than a couple of days. 

The initial setup was simple.

The initial setup of Snowflake is easy.

I think the initial setup is straightforward. Anyone who has worked on these types of solutions will pick it up quickly.

The initial setup is not complex.

The initial setup of Snowflake is easy. We only need to create a login, there is no conventional setup.

When it comes to migrating from a previous platform to Snowflake, it largely depends on the size of the data warehouse, the number of integrations, the existing data pipelines, and the type of data sources. The complexity and size of the current deployment will determine how difficult the migration process will be.

There is no installation process, as it is run as software as a service on the cloud.

For deployment, I would say two to five people would be enough. It depends on the size of the project and can have from one person to 20 people supporting it. It really depends on the implementation. The people would likely be admins, engineers, and managers.

The initial setup is quite simple. It's a straightforward process. It's not overly complex. A company shouldn't have any issues with the implementation process.

The initial setup is not complex.

We deploy the solution on-premises because we are developers, the customer is the one who has it on the Cloud. We helped them with the on-premises deployment and then we install the software and we deployed our solutions made on-premises. We complete any changes that need to be done in order to work in the customer's landscape.

The time of the deployment depends on the solution the customer requires. If it's a small solution, typically it will take approximately two weeks. A medium solution, that takes from two weeks to eight weeks.  However, it depends on what you are trying to accomplish with the solution. If you are trying to do a very complex data warehouse, it's not the tool that times the most time, it's the analysis and design that takes the most time for deployment. Once that you have the analysis, design, and you transport them to Snowflake this is not difficult.

In any BI solution, you have a lot of changes because of what you need to do with the end-users, there are a lot of changes to the end-user. This can also take up some time for the deployment for the first time. It can take two to six weeks for a medium-sized project.

It was easy as pie. In a couple of hours, it was up and running, and we were loading the data in. We had a fairly senior developer for that. He knew SQL server and queries very well. If you're used to developing in any type of SQL environment, you can jump in and use Snowflake really quickly.

There is no need to install this software, which is the best part. It doesn't require any maintenance, and although DBA support is required, it is much less compared to an on-premises solution. This type of cloud-based solution has no requirement for software, hardware, or maintenance because everything is managed by Snowflake's system.

The setup for the product was straightforward. For us, it was a little bit of a challenge because when we implemented the data warehouse, we also changed the architectural concept and we implemented a better framework. Because this framework was new to us it complicated our installation. But Snowflake itself, if you want to use and you have a data warehouse already in place with the right framework, then it is straightforward. You just store your data in and that's it. What you use on top is material for orchestrating all the load jobs. But this is other integrations and other choices that are really outside Snowflake itself.

The initial deployment from purchase until it was up and running in production took two months.

We did some testing and some comparisons, but it's all set up now and running fine. The deployment took about three months. Since we didn't want to disrupt the on-premises, or overload the system, we did most of the migrations on the weekend.

For maintenance, in the beginning, until you are through with training and performance tuning, you will need more people. You might need to start with seven or so, and then, for ongoing work, probably one or two people can manage it. 

The initial setup is pretty straightforward. We didn't have any issues with implementation. It's not too complex.

The initial setup is straightforward. It doesn't require any hardware. It's just about getting the account access and having a browser. Everything is done by Snowflake. There is a set process that you need to follow. It is a really fast process, and it helps that the entire migration can be done within minutes. The solution is used on a daily basis by hundreds of people. 

The installation is very easy. What is needed is a good extract, transform, and load (ELT) tool and we used Matillion.

Everything with the installation went smoothly. I believe when I joined the company Snowflake was already here. They bought the Business Edition that is encrypted everywhere because they are a financial insurance company and most of them choose the Business Edition because of the security.

We need about 50-60 people to maintain the solution.

The initial setup is very easy, especially if you have cloud knowledge. We have around 150 users. 

The solution's initial setup was very straightforward.

Its setup was quite straightforward. I did not find any complexity with that.

Its setup is not very straightforward. Its customization and configuration are not very straightforward. For two large data factories, the configuration is too complicated. They should work on it.

There is no installation as such. After you register with Snowflake, you get a demo database, which you can configure and use. It only takes around 30 minutes. 

The initial setup is straightforward. Since Snowflake is software, the only requirements to start using it are to select a subscription and activate our account.

It is very easy to install. After the installation, you just have to input some information into the Snowflake database. It is very easy.

The initial setup is very simple.

The initial setup was very straightforward. It was very quick. The complexity came from our specific use case scenario.

The solution is a SaaS, it can be installed and managed by your provider. The installation setup is not difficult in this case. However, the configuration took us a couple of days.

The initial setup is easy. Full deployment takes a few weeks. The initial deployment for the first initiatives might take weeks. It's not complex, really. You may have it loaded after a full day and already providing results or interacting, but there are some other companies that have to be implemented to extract and consume the information from the database. But it's very easy.

The initial setup was not complex. We needed a dedicated person for the setup. Once we know the requirements, it's not that complex. It has straightforward parameters. 

The initial setup is very simple, just go to the internet and start using it. Of course, if it has to implement to part of the customer's own cloud infrastructure, then there are more steps to configure. We provide that service for our customers. 

The initial setup of Snowflake is very simple and straightforward. We do not need to read or understand any of the technical documentation. It is a plug-and-play service or platform.

It was not complex. Our implementation strategy was to put Snowflake on top of Google Cloud solutions instead of BigQuery, but BigQuery was better in price. So, BigQuery won in this case instead of Snowflake.

The initial setup is very straightforward. I wouldn't describe it as complex.

How long it takes to deploy depends on your knowledge and your background. It's difficult to judge. I've been working for 20 years now with data warehouses. For me, it was very easy because of my extensive background. However, it depends on what someone knows, and their technical background. It can be difficult for others who maybe don't have as much knowledge or first-hand experience with warehouses.

The initial setup is straightforward. There's no deployment; it's just your code solution that needs to get up and running. You have a deal with Snowflake in terms of what environment you want, and when you want to use it, and they'll set it up within a day for you.

The initial setup is very straightforward.

It is easy. It is a SaaS solution, so there is no installation. Therefore, you don't need the infrastructure team, but you need a few data analysts.

It was quite straightforward. There is no problem with that. However, managing the database and roles and access is complicated. Its deployment didn't take a long time.

The initial setup is straightforward. You just need to follow the documentation.

The initial setup is not too complex. It is pretty straightforward. A company shouldn't have too much trouble implementing the solution.

The initial setup can be complex at the beginning but once you get into it, it can be straightforward.

When you come from an on-premises solution and you have to change or shift to the cloud, it works very differently. Once you know the differences then it is straightforward.