AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Jetbrains datagrip hello1/23/2024 Pycharm Community is actually how I learned about other Jetbrains products and led me to using Datagrip. A different case is Pycharm, because it has the free version, I've seen a couple of colleagues using it - outdated version installed from company approved site. I've been using the product on my work computers only because I pay for the license without any contribution from the company, install it myself in a hacky way and my managers tolerate me using it. We work in companies that only accept software they purchased or freeware as long as it passes security checks, since we are working with sensitive data. While analysts close to technology can get effiecient in the product quickly, others would struggle.Į) DataOps - Those are the people that have full access to production and from time to time can make slight adjustments to the data, usually by running a script prepared by Developers and/or maintain CI/CD pipelines for quick propagation of DMLs and DDLs to higher environments.į) Data Scientists - I will not cover as those are either using SQL similarly to analysts or Python/R or else using other products.Īs Datagrip is commercial-only product, it is unlikely it will get into hands of DWH experts. DWH Analysts in general have the need to perform complex ad-hoc queries on multiple databases using different accounts in order to find root causes of issues, elaborate new features as well as check whether each data consumer group has proper access. The product doesn't help this target group in any way.Ĭ) DWH analysts - The analysts are usually split into technical and business based on whether they have a good understanding of the technology involved or rather the business terms used, also wheter they work closely with the development team or sit in business deparments. Datagrip is only capable of a very basic visualization of the tables that provides no added value. DDLs are then generated from the physical model and applied to database. As the approach to building DWH tends to be model-driven architecture (MDA), modelers would use tools such as PowerDesigner to construct and iterate from general ideas of business concepts down to physical tables and columns (conceptual/logical/physical model). However, some of the needs in this area are not respected.ī) Data modelers - Those are the designers of database objects. I think the product does well for this target group, as developers are used to work with rather complex and technical tools. Based on my experience, working in different roles, I understand the product can have following groups of users:Ī) DWH Developers - In DWH world those are the people most concerned about creating data pumps (ETL/ELT), translating mapping documents from analysts into data pumps, heavily SQL focused. I'm a Data Warehousing (DWH) expert, over the last decade involved in building analytical solutions for a number of clients across industries. Let me explain a bit of background for you to understand where I'm coming from with this feedback. Don't get me wrong, I still believe Datagrip is the best product currently available, but it's such a shame the potential is not leveraged. As a customer and heavy user of Datagrip for a few years, I've been recently rather mispleased with the roadmap of the product, so I wanted to share my feedback which I hope represents a part of industry (and user base) thas is being overlooked.
0 Comments
Read More
Leave a Reply. |