AKHIL AGARWAL

Hi, everyone. This is Akshil Agrawal, and I belong to Bareilly, and I completed my graduation in 2016. After that, from 2017, I moved into the IT environment, and I started my career with COSI Info Systems. That was my first company situated in Hyderabad. There, I worked as a technical support engineer. After that, I moved to Infosys where I worked as a SQL database administrator. There, I worked on replication complications, two types of replications I worked on: snapshot replication and transactional replication. With that, I worked on always-on cluster configurations with those FCIs and listener configurations. I helped the team by building a 12-node OLTP cluster, where eight nodes were present in Bangalore DC, and four nodes were present in Mysore DC. So we combined 12-node clusters for the OLTP configurations. And, moving on, I gained experience with performance tuning and query writing, stored procedures, and configurations. Those are my tasks at Infosys. Then I switched to Dell. There, I worked as a service delivery engineer. My key responsibilities were to focus on the top 3 tickets where customer escalations were there, and managing how to provide better resources for system performance and SQL Server students. And I was rewarded with customer feedbacks and Insta Awards from Dell, from Intel, by providing great support to the clients. Those were my achievements in the build environment. Then I switched to VMware. Until present, I'm working with VMware. There, I worked with many teams, like two to three teams. I worked on VMC on AWS, then I worked on the VM in a multi-cloud environment where I worked on vSphere environment and vSAN. Then I worked on the data analytics side where I performed analytics on the products, like vSphere products and vSAN products. There, I worked on Python, and SQL was my core skill. I built dashboards in the Tableau environment, created reports, and used Apache Superset. With that, I did have migrations for the dashboards as well, and visualizations to the executive environments and VPs. And with the Tableau dashboards, I represented data to the managers and teams. Yeah. Those were my things. Thank you.

For these questions, for this type of scenario, to check the query side or the server side, first, we will check why the query is taking a long time. Then we have some queries, using the sp_who2 command, where we check any long-running queries which were there earlier, before hitting this query, before any query was executed and excluding the entire resource of the SQL Server. With that, once those things are not there, we will ask the application team whether the query was working fine earlier and from when we observe this slowness in the application. So we will check the indexing, whether the indexing is performed on the servers or not, whether their tables are presented in the indexing format. Because when we do the indexing on the servers, that is on every two days. That's the thing. Any backup is running on the servers. If backup is the issue, it might be utilizing a resource. With that, we will see whether the table, recently, if someone has done a bulk upload or any bulk delete into the table and then after that indexing was not performed, data got fragmented. So in that case, we will defragment. So in that case, we will see these are the things we can check. Thank you.

Do implement this tool in PowerShell that periodically check the integrity of a SQL server database. How would you implement a system in PowerShell that periodically check the integrators? In PowerShell, we can configure, the server details, like server instance name, SA user and SA passwords. That will check, like, in batch file, we can like, PowerShell, we can configure and it will trigger the, pulse to a server where it will do a check whether data is present or not. whether survey is up or not. So those are the things we can check. Thank you.

So the strategic team validated the performance again after indexing last. So it's a strategy to validate. This is the strategy to edit the performance gain after indexing a large table in J47. Yeah. Exactly. We can write a select query, and we can see how much time that table is consuming, and we can generate an execution plan to see what the performance is for doing a fetch for that particular table. After that, we can check whether the indexing has performed well and whether the data is correct or not. Like, the time consuming for doing a fetch for that particular table should be minimal. Thank you.

To set up Windows for clustering or SQL server, we need to have more than one server or system. In this case, if we have two servers, we will configure active-passive clusters. There should be one shared drive between them where we will mount a drive that is shared between both servers. We will have two types of IPs - two physical IPs for the machines, and two IPs for the cluster name. Once we open the Failover Cluster Manager, we will have an option to add a cluster. We will add our machines, enter the machine, and choose 'Active Directory' as the authentication method. Then, we will enter the name, IP, and other details provided by the DCM team. Once we add the servers to the Failover Cluster Manager, they will be managed by it.

In SSIS package, there will be logs getting deleted into if it's configured into a SQL server. So in those logs, you can see where it's failing, and then we can check. We can open the package in Visual Studio. I used to debug some links. And once I open the package, then I manually try to execute and see where it's getting blocked. Some components of that SSIS package are missing. So we can check and we can connect to the application team, and we can inform them that this part is missing from the SQL Server or from your query. That's why the package is failing. Those are the workarounds we can do. Thank you.

How do you block a Python? Is it block of the script? Intended to connect to a security. Can you spot and explain any concerning regarding the security first? Yeah. In this query, we can see, like, username and passwords are clearly visible, and, it should be like, anyone can access the data once they have a password. So it should be in encrypted format, and we should not display the passwords or the usernames like that. So just we can pass the value and, hide the passwords from entering like this way.

To this query, I don't think so it will create a performance issue. Just to see if it's its first, it's a parameterized, you know, stored procedure, and we have to pass a user ID whenever we execute this stored procedure. And when ID equals the user ID because, yeah, it's the user ID, we are passing the value, so that's why ID equals the user ID, it will be there only. I don't think so it will create any issues.

SketchUp. High availability strategy for SQL Server database that minimizes downtime during updates. In this case, we can use a high availability strategy in which, according to my experience, we can configure a listener, or use an active-active cluster or an active-passive cluster configuration if it's provided to the environment. And the strategy of minimizing downtime is that whenever we do a patch to a server or SQL patching to SQL servers, in that case, we can do a failover of active-active databases to the passive nodes. Once we do a passive node failover, then it will be minimal downtime. It's similar to a network glitch, and the service will be available to applications every time. And if we configure the listener configurations, when we do a failover, the listener will be connected to our servers, which is an online state. So we can use that way also. Listener configurations are also part of the high availability features. Then we have Windows Failover Clusters, in which an active and passive node should be there, and we can do a failover when we go to the Failover Manager. And we can do a failover from an active node to a passive node, and the service will be active every time. So the drives from the active nodes will move to the passive nodes. The note drive will be available to those nodes as well. Yeah. Thank you.

What methods do you employ to incorporate existing PowerShell scripts with the service package for advanced CDL process? I'm sorry, I have not worked on a PowerShell with SSIS things before. I'm unable to answer this.