วีดีโอ

You're welcome!

Each series consists of a set of videos designed to help the community. They begin with basic concepts and gradually progress to more advanced topics. I don't have plans to start training sessions at the moment, Rahul. Thank you for your interest, and I hope you’re finding the content useful!

Glad you found it helpful!

Glad it was helpful!

Happy to hear that it worked!

I'm afraid that's not possible. The input for this report is a SQLNexus database, so you won't be able to directly analyze PerfMon files.

Glad you liked it. When you take a copy-only backup on the Always On secondary replica, the point-in-time recovery process involves several steps to ensure that the restoration is consistent across all nodes. 1) The copy-only backup is taken on the secondary replica. This type of backup does not affect the sequence of regular log backups, making it ideal for scenarios where you need to take an ad-hoc backup without disrupting the backup chain. 2) To perform a point-in-time restoration, you need to restore the backup on all nodes. This involves restoring the full backup followed by any subsequent log backups up to the desired point in time. The steps are as follows: -> Restore the full copy-only backup on the primary replica first. Ensure that the database is in a restoring state. -> Apply the log backups sequentially up to the point in time you want to recover. This includes all log backups taken after the full backup. -> Once the primary replica is restored, you need to restore the same backups on the secondary replicas. This ensures that all replicas are synchronized to the same point in time. -> After restoring the backups, the secondary replicas will synchronize with the primary replica. This process involves applying any remaining log records to bring the secondary replicas up to date with the primary. I hope this helps! If you have any further questions, feel free to ask.

Glad it was helpful!

Thanks for your interest!

Happy to hear that it solved your problem. Good luck.

Each series consists of a set of videos designed to help the community. They begin with basic concepts and gradually progress to more advanced topics. I don't have plans to start training sessions at the moment. Thank you for your interest, and I hope you’re finding the content useful!

Thanks for your interest. I dont take any classes.

Thanks for your interest. Glad you liked it.

Glad you liked it. Thanks bro!!!

Glad you liked it. below are my response, 1) Yes, you need to install the Failover Clustering feature on your server before you can use the Get-ClusterLog command. The Get-ClusterLog cmdlet is part of the Failover Clustering PowerShell module, which is only available after the Failover Clustering feature has been installed. Once the feature is installed, the command will work out of the box without any additional configuration. 2) Setting VerboseLogging to a higher level will indeed increase the amount of logging generated by the Failover Cluster service. This setting applies to the overall cluster logging, not just the Get-ClusterLog command. As a result, more detailed logs will be recorded, which could potentially lead to larger log files that might fill up the C: drive if not managed properly. However, it’s important to note that the Get-ClusterLog cmdlet itself does not directly cause logs to be written to disk continuously; it merely collects existing logs into a single file for easier analysis. The VerboseLogging setting will influence the amount of detail in the logs that are already being generated by the cluster service, which Get-ClusterLog then aggregates. To avoid filling up your C: drive, you should monitor the available disk space and manage the log files periodically, especially when VerboseLogging is enabled at a higher level.

Thank you for the question. Yes you can create read routing from GUI.

Thanks for sharing your experience. It’s interesting to hear that you encountered a similar issue with the cluster being in a pending state and fluctuating. Could you share more details on how you resolved it? It might help others facing the same problem.

Thanks !!!Glad you liked it.

Thanks. Glad you find it useful.

Yes, it’s generally a good practice to place the condition with the highest selectivity first in the WHERE clause. This helps the database engine filter out rows more efficiently, potentially improving query performance. Selectivity refers to the ability of a condition to narrow down the number of rows returned by a query. The more selective a condition, the fewer rows it returns.

@@jbswiki Thanks for this. could u please make a video on inequality predicate estimation.

@@abhinavtiwariDBA Thanks for your interest. Will do a video soon.

Glad you enjoyed

Hope you are well. Only secondary should fine for the given scenario.

Wow, thanks for your interest.

Sure will do. Thanks for your interest.

More videos every Tuesday. Thanks for your support.

Thank you for your support.

Sure, Thanks for your support!!!

Thank you for your support.

Glad you liked it. I am doing TH-cam videos only.

@@jbswiki Have any plan to start ?you can think of that on weekend

Thank you for your support. Glad you liked it. I am doing TH-cam videos only.