Sushma Kumari

Hi. My name is Sushma Kumari. I have been working as a database developer from past 12 years. My primary skills were writing SQL queries, creating reports, Uh, using the data modeling, data warehousing using MS SQL 2019. Uh, Cognos, IBM Cognos, Jasper. And I have used a PostgreSQL, AWS, and Python. And, uh, as a senior member of the team, I have also, uh, helped my, team members to, uh, to guide with their difficult queries and, uh, supported Collaborated teams like the BAs and QAs. And I have also worked, uh, I I mean, domain wise, I have worked in health care domain and hospitality. So my last, uh, my last previous job was in hospitality to uh, doing where I have worked continuously for 6 years. And, Apart from, uh, these, I I have, uh, also worked on, uh, Pentaho ETL. I have also worked on Oracle and, uh, ELT and, uh

How do I utilize the SQL in developing? Like, I mean, I do write the SQL queries. It depends on the requirements, like, uh, what I have to write. I'm not sure, like, what this question. I have used SQL, so I write I do write complex queries. How do I utilize? I think I'm not getting that question, but I uh

How would you handle data extraction from the business report that requires data from multiple tables? How do I handle? I can use, uh, joined queries to get the data from multiple tables. And through the metadata, I can and I can get all the data in a single table. Maybe Not sure if someone wants to talk about SSIS here.

Okay. So for performance in SQL queries, we can check multiple things. Uh, first, we'll, uh, check the whether the indexing is correct or not, whether, uh, index Uh, are there too many of index as been given in that table? We can avoid the case condition. We can see if the Join is based on, uh, the same data type of the field. We can We can use, uh, top instead of selecting all the field names. So these type of things, you can, uh, see to enhance the performance. Indexing is the main thing, uh, and, uh, joins also, like, to see, like, if we can use the inner join. We should use inner join instead of a rare condition. So things like that, uh, we can check.

So while designing, uh, we have to be, like, um, about we have to be careful about the relationship and the data type. So I think these are the most important thing that we should, uh, we should keep in our mind. And, uh, like the how the tables so the later also, the performance of the table will be good. Uh, it will not slow down. Uh

Huddl flow to design useful database for an application that means to Huddl. Define is QM database. So we can design the table and Uh, the final data is not sure.

Given the following, you can point out how it can be optimized for better Uh, maybe we can write, uh, select count star, uh, comma, country and then comma city from customers where country is equal to USA and city is equal to New York group by country and setting.

We have to write And at the end of the procedure, uh, after country at country, we have to write

Oh, I know the sign has for the database. I will check the tables tables data type and the land and the relationship between the different tables. Indexes is given correctly or not or so many Indexes has been given. Uh, Yeah. These are the things I will do before designing