#How to share queries in your team
If you're writing or using SQL in your team right now, do you remember how it felt when you first began sharing?
Since each organization usually has a different database structure, no matter how well you understand SQL, it is not easy to find the data you want unless you have knowledge of the structure, such as each table, column, or relationship. So it's difficult to identify structures by looking at queries and ERDs that have been written before.
🔎Possible issues that arise when trying to understand the data in your company
(1) Database Access
Accessing the database is not easy. There are many different types of databases used by organizations, each connection requiring their own host, port, user name, and password. None of which is easy to share.
Sharing might be a bit easier if you're updating the list of all databases within a team wiki or a private document, but most of the time we forget the password after saving it somewhere online. There is also the factor where planning and marketing positions can have difficulty accessing this information from the get-go, because not many are given access if they do not belong to the development team. The method of sharing such sensitive information through messengers and emails is also risky as it can lead to security leaks.
(2) Sharing a Query
Let's say some database information has been shared with you. What's the next step?
We need to understand the structure of the table, the relationships, etc. before we start to think about where to find the data we want, and what kind of queries we want to make. Only then can we find the results we need. But unless you work alone or build a database from scratch, there will be a number of people within your organization who have already extracted data. So it is essential to refer to these queries for faster visibility.
At times like this, we usually share queries by instant messenger or through email. But when copied to the clipboard and shared or forwarded by means of a file, it's difficult to figure out where which query is supposed to go.
(3) Query Update
Whether it's a file or a copy+pasted query, there are often times when you don't get the results you want when trying to run that query within the SQL Editor. If a value in a particular column is changed or deleted, it will result in incorrect results. And sometimes you want to modify the period or variable, but you have to change it as you go through the values one-by-one. So there are cases where it's not very useful to use the shared queries, even though it's given by a colleague.
These situations are common within an organization, and in order to solve them there is no choice but to get help from the tools we use.
Many developers and planners who use a SQL IDE reached out to us to express their desire for an easy way to share queries within their teams. Even our company, which makes data management products, has suffered the same difficulty in sharing queries. So to meet the needs of our users (and ourselves), QueryPie has implemented a new Workspace where users can invite their teams and easily share queries.
💡 How to analyze data using QueryPie!
(1) Invite your team members!
The first step is creating a Workspace, then adding and managing the list of desired databases. After that, you can simply send an invitation to your team member using their email address. After they accept, they can work with you in the same Workspace.
(2) Share your Database List
When invited users accept and enter the Workspace, they can easily access the database with a click, even if they do not know the connection information of each database (i.e. host, user, password, etc). So although there may be many databases within the organization, it is easy to navigate them because only the administrator is handling the registration part. The invited team members do not have to enter any access information individually to view the same data.
(3) Share your Queries
Having a Query Directory is also helpful to users who share a Workspace, where numerous queries can be stored and managed easily.
For example, let's say you are selecting a list of users who have purchased a particular item in the last 10 days. You can save this query in a directory so that other team members can recall it in a single click within the app and modify, execute and save only the items they need.
📌Give us your feedback for future updates!
QueryPie is always seeking ways to make working with data easier and faster to view within an organization. The sharing feature came into existence due to this concern.
We plan to add more features that allow effective collaboration, such as managing access controls and checking revision history, so please try out the Workspace feature and let us know what you think! We decide what features to build based on your feedback, so don't hesitate to reach out to us with any suggestions or concerns!