A few days ago, I have asked a question on this blog. The question was – What would you like to see in the next episodes of SQL in Sixty Seconds. The poll is still active and posted over here: SQL SERVER – Poll – What would you love to see in SQL in Sixty Seconds? The contest was to suggest the next item of SQL in Sixty Seconds and vote for the your choice of subject. There have been plenty of votes to this contest, however, there were only 4 comments to this blog post. Hence, selecting a winner was very simple.
Result of Poll
It is very clear from result, most of the people would like to watch Performance Tuning subjects. I will continue to build video on this subject in future.
Contest Winner
Now is the time for the winner of the contest, who left comments on the blog. The winner is Raelyard. Here is the comment which he has left on the blog.
raelyard please reach out to me via email and I will send you the gift card.
Current Contest
Here is the contest which is currently running on this blog. You can take part in the contest and can win a Drone.
SQL in Sixty Seconds
Here are few of the episodes of SQL in Sixty Seconds, which you can watch. We will have more episodes of SQL in Sixty Seconds from next week which are focused on performance.
Reference: Pinal Dave (https://blog.sqlauthority.com)
4 Comments. Leave new
Hi Pinal ,
Can you explain CONSTAINSTABLE and FREETEXT table usage with examples with outputs??
Thanks Pinal. Email coming. Looking forward to seeing your video content. (note that I posted for a few times with raelyard showing up as my name before realizing that’s how it was showing and deciding I wanted that to reflect my real name and changed it)
Hi Pinal,
It would be better if the team should give better clarity on clusters Primary and Secondary.If we run maintenance jobs on the primary working fine.but in the secondary it is failing and showing read only.we may not know when the failover happens between the primary and secondary.I would like to see any changes regarding this in next SQL…!!!
Vanitha, I guess you are talking about AlwaysOn Availability Group primary and secondary.
As of now, you need to add a check in the job to run it only if it’s primary replica. I am not from Microsoft so can’t tell you if this would come in next SQL version. I would like you to provide feedback to Microsoft SQL Product team by logging issue to https://docs.microsoft.com/en-us/collaborate/connect-redirect