I am a Support Engineer at Microsoft in SQL Server sharing some useful sessions here.
This channel is about internal features of SQL Server as well as installation guides of different components. In this channel. you will be able to deeply understand how SQL server works internally which can be helpful for maintaining SQL Server as DBA. Furthermore, I will share useful troubleshooting sessions which might be helpful when you face issues in SQL Server.
Please kindly note that the contents of this channel belongs to me only; they do not necessarily reflect the views and recommendations of Microsoft.
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 :)
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
hello I am Thank full for you videos. your architecture video was awesome and hekped me. can you start performance turning videos please. i want to learn . if not please guide me any best vidoes to learn performance tuning from basic to advanced. high CPU issuee, high memory issues, slowly running sp, slow batch jobs, inserts happening slowly etc
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? ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE--l3HzkBd5EM.html&ab_channel=ARSLANOV (recommend starting from this :) ) ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-1oCYUA2bjUs.html&ab_channel=ARSLANOV ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-S4qj0D74JIg.html&ab_channel=ARSLANOV ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-GcKRWrMeLNc.html&ab_channel=ARSLANOV ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-AievhIhGBdY.html&ab_channel=ARSLANOV ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UrZtKoqVpxo.html&ab_channel=ARSLANOV I will try to do more!
Very interesting, thank you! Trying to find information on risk of data loss or data corruption when upgrading compatibility mode in production. Do you have any information on this?
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
thanks mate for the beautiful session❤ ...I looked into the next video to learn about maintaining and resolving index fragmentation, but the relevant information was not available.
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 :)
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👍
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
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
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 :)
