Відео

Glad it was helpful!

Happy that you like it🙂

Hello, thank you for watching. Added script. Please let me know if you need anything else. Furthermore, you can share your interested topics you want me to cover in the future. Thanks :)

You can see the link in the video description

I am glad you liked it!

Thank u🙂

Oh i see. I never tried multi statement batch

Hello. I am glad you liked it Unfortunately, when you apply the plan, the current plan for the same query is deleted. Therefore, before applying the plan, you should save old plan for the same query. When you want to revert back, you should apply the old one by removing the applied one. Step 1 Save the old plan before applying the plan Step 2 If you want to revert back, run the below and remove the applied plan: EXEC sp_control_plan_guide N'DROP', N'TestPlanGuide'; Step 3 Apply the old plan in the same way. With high possibility, you can just rerun the query and it will generated the same inefficient plan. But in case, it does not, you can just apply the same saved one

Thanks. Will do it soon!!

@@arslanov1886 thank you so much

Hello Venkata Thank you for your comment. I am glad you liked my videos Related to high memory issues, I hope the video helped you. I will try to add more. I have a few performance tuning videos. Did you check below? ua-cam.com/video/-l3HzkBd5EM/v-deo.html&ab_channel=ARSLANOV (recommend starting from this :) ) ua-cam.com/video/1oCYUA2bjUs/v-deo.html&ab_channel=ARSLANOV ua-cam.com/video/S4qj0D74JIg/v-deo.html&ab_channel=ARSLANOV ua-cam.com/video/GcKRWrMeLNc/v-deo.html&ab_channel=ARSLANOV ua-cam.com/video/AievhIhGBdY/v-deo.html&ab_channel=ARSLANOV ua-cam.com/video/UrZtKoqVpxo/v-deo.html&ab_channel=ARSLANOV I will try to do more!

Your comments and likes give me motivation to continue. Thanks! :)

Cool, thanks!

Thanks, will do!

I updated and added github link to video description

Sure. :) Thank you!

Glad it helped

Hello. Thank you for your comment. Changing compatibility mode does not cause any data loss or corruption. It is metadata level change in SQL Server. SQL Server just changes the way it compiles plans etc. Compatibility level change does not cause changes in user database. Furthermore, you can roll back to previous compatibility level at any time

Hello mate. Thank you for your comment. I am sorry. Did not have time for that video. We have very detailed documentation on this: learn.microsoft.com/en-us/sql/relational-databases/indexes/reorganize-and-rebuild-indexes?view=sql-server-ver16 Please kindly go through the above. It is very detailed and helpful and answers your doubts :)

Thanks🙂

Glad it helped!

Thank you for your comment 🙂. Please let me know which part of video you think should be improved. I will do my best to take into consideration next time👍

Thanks

Thank you. Your comments give me encouragement to continue :)

Happy you liked it

Thank you for your comment Unfortunately, there is not good resources I can suggest. I can tell one thing: the more you work with SQL Server, you will understand more. Btw, I highly suggest below internals documentation by MS: learn.microsoft.com/en-us/sql/relational-databases/sql-server-guides?view=sql-server-ver16

Most welcome 😊

You are most welcome

Let your Windows team provide the CN signed certificate for you which is a recommended approach. or you can run New-SelfSignedCertificate in powershell to generate self-signed certificate: learn.microsoft.com/en-us/powershell/module/pki/new-selfsignedcertificate?view=windowsserver2022-ps About the issue you face while using self-signed certificate: learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/error-message-when-you-connect

Glad it helped!

🙌

Interesting take on identity columns, never thought of that though it makes sense

Yeah. This is the design issue where many DBAs make mistake

Hi, you should generate it manually as self-signed certificate or your windows team should generate CN signed certificate for you if you do not want self-signed certificate :)

Really, really helpful thanks.@@arslanov1886

Thanks 🙏