Pushpinder Kaur

Yes. Of course. Uh, first of all, hi. My name is Pushpindarkar, and I have experience of 7 years in software development. And, uh, in my last organization, I was working as a senior software developer, and my role was as senior school developer. Um, in my last organization, I was, uh, I have a role of senior's as for developer in which I have responsibility of developing and maintaining the database server and as well as to do the implementation and to collaborate with the IT team so that we can deploy the scripts into the deployment server. And I have completed my bachelor's degree in computer science from Mumbai University. And as well as I have completed my master's degree in project management. And I'm very passionate about the coding. That is why I pursue a career in software development. And, also, um, in my last organization, um, I have, uh, like, I have additional responsibility as well, like, for x, uh, like, uh, I was a scrum leader. I bought I was a scrum master for development team. And as well as I need to give a training to the stakeholders so that they are aware of our new bill newly built system as well as I need to provide our training to the junior. And, also, my responsibility was to maintain the technical specification documents as well as to maintain the system architecture document. And, um, in the absence of, uh, team leader or manager, I need to review the code for a code to code for the junior level. Thank you so much.

When I have to optimize our database performance, I need to take care of that, uh, that all the database should be running properly without, uh, any block or blockage or any portal next because it is very important for us to see that, uh, our database should be running in proper, uh, you can say proper way, uh, so that it won't impact our productivity as well as performance. And to overcome this, uh, I usually maintain the database by I use I usually check the database by using a different by using many techniques. Like, I need to take care that, uh, there won't be any, um, like, um, any select star statement in our database. There should be a, um, like, a limit in select star operation, uh, so that there won't be any, uh, huge load in our database as well as ash, uh, as well as for doing the searching, we we can use index of we can use the index function so that, uh, we can retrieve that data as soon as possible, like, a fast retrieval of the data as well as another way to optimize the database performance is to use the wear cloth instead of fetching all the records from the database. Uh, we can use the WHERE clause so that we can get a specific data and in the range of, um, particular WHERE format, WHERE clause. And and and, secondly, we can, uh, for the optimization purpose, we can make sure that we, uh, if we have a different database, uh, instead of, uh, all the database into one main database, we can um, differentiate or we can separate the database as per their requirements. For example, in my previous organization, I was working with the 4 countries, but, uh, initially, all the 4 countries database is merged into 1 database. So to optimize the database performance, I divided the main database into the full database as per their countries. And by this, we the load on one database was reduced, and we have, um, um, we have increased our, you can say, performance by 30% because there was no workload or you can say data load in our database because of the country. So whenever we are using a one country, so there won't be impact on the other countries. So by this by using this all techniques, uh, I have optimized the database performance in my last organization. And as a result, we have increased our, uh, database performance by 25%, and, uh, even the load on data will reduce by 35%. Thank you.

To prevent the SQL injection attacks in store procedure, we usually try that all the data which we are getting should be encrypted. For example, in my last organization, I was working as a I was working on a financial client project in which we have to maintain the username and password for the user. So because it is a financial project, it's very important to, uh, secure the data of that particular client or user. So for that, we usually use the SALT techniques in which, uh, we encrypt our user's password, and it will store in our database. And for encryption of that, uh, particular password, we need to use we we used to we need to use the decryption of the password. So by this way, we have implemented the at x cool injection attack, uh, in store procedure by using different techniques.

Uh, what is mhmm. For using the indexes to improve the query performance, I usually use the cluster index, as well as unique index because, uh, cluster index is used if we require if or cluster index is used because, um, the physical orders will be the same as the table so that we can easily, um, we can easily retrieve the data, uh, as faster. And even if we want a unique, uh, data from the database, for that purpose, we are using the unique index. So in my last organization, when I when I was, uh, assigned with the task for the query optimization, As we query perform query optimizations on that time, I have utilized the cluster index so that we can retrieve the data because we need to fetch or record in from a particular column. So for using for doing that, the cluster index is most, uh, you can say useful for us. And even for getting a, uh, for maintaining the uniqueness in our column in particular column also, I have you the unique index so that we can get we won't get any duplicacy across in our database. And so, yes, for using, uh, for optimizing, uh, the query performance by using the indexes, I use the clustered and unique index.

Yes. Uh, for managing the and for managing the school server database transaction, I use the asset approach because that is the most popular approach for the transaction purpose. Uh, I remember that in my, um, previous organization name as Atos, where my, uh, I was working in, um, uh, I was working in a project who whose client was insurance client. And we are using as it was a insurance client as well, uh, insurance client. So I have to maintain the data so that they won't any impact on the users' data. So for that purpose, we have used the asset transaction. In asset transaction, what we have make sure that if the transaction is happened, so it should be complete if, uh, otherwise, it should not it should be not complete. It should be, uh, the same as the previous one. And, um, if, uh, even I have even I make sure that if there's any, we can say, interruption between the tables during the transaction, so I have to make sure that the, uh, data which is, uh, like, which is, um, impacted because of the any issue, so that should be re revert or roll back to the same, uh, chamber so that there won't be any, uh, effect on the new chamber or new entry. And, uh, so to over to so to do that, we have used the asset approach. And even the asset approach is used for the mainly for the transaction, like, I have used for the insurance client and financial client. And because we have a requirement from the client that, uh, in which we have to use the asset transaction. Sorry. Exit concepts and even, uh, we know that there are some, uh, financial, uh, outcomings in so ingoings and outgoings are will be happening in insurance and the finance life insurance and finance application. So we have to make sure that all the transaction which is done before and after should be saved. And if there's any, um, if there's any interruption between that in that transaction, then it should be rolled back for that. It should be committed and rolled back to the original database original table so that there won't be any impact on the other tables. And if all the data if all the data has been transferred to the new tables, so um, we need to check that all the additional or additional of this, uh, previous one and the new one should be same.

For the for making sure that there should be a minimized effect of frequency changes. I will make sure that if there's any frequent frequent changes are going on, for example, um, uh, like, uh, insertion or updation if I'm doing any entry or if I'm taking something. Ask, uh, if I'm doing some operations. So I will make sure that, uh, there should be, um, like, a trigger. Uh, we can say a store procedure behind that so that with there won't be any so that we can, uh, maintain our, um, we can maintain our quality of database. For example, uh, I know that during the click, there will be any insertion or there will be any updation or deletion. So I can create a stored procedure in which I can write a query regard related to the insert state, uh, uh, by gathering all the data which is needed, um, in the insert statement, and I will I will trigger that thing. And so that there won't be any changes, uh, on our, uh, tables or database or we I don't need to write a query again and again. So I will just call that short procedure, and the insertion will be done as and also bypassing the arguments, I can do that. And even I can use the view because view want a store or take a lot of, uh, you can say, sizing of a database. And it is very easy to maintain the view because and very easy to maintain the view. And, also, in the view, we it is like a temporary, uh, table for us in which we can gather the data from 1 or more tables, and we can store the data there. So by using this ways, we can minimize the effect of, uh, like, a frequent schema changes, and it won't be, uh, like, it won't be, uh, taking a lot of, uh, space as well as or it it looks like a we are reusing the, um, you can say, a query.

Yes. To optimize this particular, uh, T SQL function, we can do one with that. Instead of using the wear gloves, we we can use the having clothes and buy and, also, uh, we can use a group bike cloth so that all the, uh, you can say, all the details will be aligned into 1, uh, into 1 column, and it will will be very easy to sort the data, uh, to group that data. And, uh, it will be, like, a faster, um, if we can, uh, means if we are using the group by Cloudera, it will group all the details, um, as per the column. And it by this way, we can, uh, easily gather the data.

In this, uh, in this, we we need to use a bracket before the case statement so that all the statements, all the case function will be, um, like, perform, um, perform, with perform CMS we are required because if we if we execute by this functionality, then it will, of course, it will give a wrong answer because of the bracket. And as well Even we need to use the semicolon in last, uh, in ending of after the expensive.

For maintaining the database concurrency complex in high transaction environments, I will use the asset strategy, uh, so that they will be a there will be a concurrency between the transactions. And if there's any, um, you can say bottlenecks or if there's any interruption between the transaction so that it can be rolled back. And, also, um, I will make sure that all the transaction which is, uh, done which is done or which is executed properly without any interruption, that should be reflect into into the new table. Or you can see it into other table, and the all the entries should be, like, missing from our the original table.

Yes. There are many times in which I have to refactor database design for improving the performance. Uh, big in my last organization, when I was working with the, um, client, um, client stakeholders, and the manager, So we have a collaboration between we have a I have collaborated with them and, uh, and then and, also, uh, propose a new solution for that, uh, because in our one database, we are using a different, um, sub databases. We are using sub databases, uh, for our, um, as compared to, um, sorry, as per the countries, we are using, uh, sub tables in our main database. But after that, uh, I can I realized that it will load the main database? So, uh, so after discussion, the same issue, and we have proposed one solution for them and in which we have to in which we have, uh, like, we have to refactor our database design. So that was to, uh, divide our main database into the sub databases as per the countries. And we perform the operation perform the operation as per the country wise. So there won't be any bottleneck and even there won't be any, uh, values which can impact the other countries, uh, other countries or other user because there can be a cases where we have used, uh, 1, uh, user with a different one user can have a different, uh, you can say different, um, relationship with the different con with many countries. So to overcome that, we have used a primary key so that they won't be primary key, foreign key, and composite key so that there won't be any impact with the other, uh, table, which is present in the database. And for this purpose, we have to, uh, refactor our database design, and we have proposed that design to, uh, we have proposed that design with the stakeholders and and, uh, the higher authority. And after give after getting approval from them, uh, we have, uh, um, we, miss, uh, we have took the help from from from the IT operation team, and we have deployed all that necessary thing which is needs to be done so that it can be useful for future reference. Even for that, we have maintained, um, our technical specification document and system architecture documents so that it can be used for the future reference.

For, uh, for documenting my SQL code and database design, I usually use, um, I usually use this document name as technical specification and the system architecture document in which I need to maintain our SQL, um, our database design and SQL code. And as well as, uh, we have, uh, 2 types of approach. Like, first one is a, um, soft copy as well as a hard copy approach. Um, in both, uh, soft copy and hard copy approach, we usually maintain our both the thing, and we usually, uh, deploy our soft puppy to the deployment server so that we know or so that the testing team or other stakeholders know about our scripting that what are the things we have done we have done, uh, we have changed, and what is the future approach for that? So that as a reference as a reference for as for the future reference, we know about that things. And even in absence of absence of us or there can be a case that we have a switch over company. So to deal with that to, uh, to so to do any changes in our database by the other employee. They can get a help from our documentation. So like this way, we have done the documentation for a SQL code and database design. And and we keep our hard copy because there can be case that we can't able to, uh, through we can have to discuss a particular thing with the stakeholders. So it is better to have a hard copy to, um, to, uh, to give us decisions or to give a suggestion to the stakeholders.