How to use Service Broker to scale out SQL Server database applications

Подписаться 14 тыс.

Просмотров 49 тыс.

50% 1

Database applications can be scaled up or out by using SQL Server Service Broker, which provides asynchronous messaging and queuing infrastructure. In this video, watch Microsoft Certified IT Professional Jon Seigel explain the basics of how Service Broker works and the database objects behind creating your own Service Broker applications.
Blog post for this video:
voluntarydba.com/post/2014/02/...
SqlDependency class:
msdn.microsoft.com/en-us/libra...
Service Broker samples on CodePlex:
msftsbprodsamples.codeplex.com
ssbdiagnose utility documentation:
technet.microsoft.com/en-us/li...
Visit my channel for more database administration videos:
/ voluntarydba
Subscribe to get notified about my latest videos:
ru-vid.com?...
Read additional content on my blog:
voluntarydba.com
Follow on Twitter:
/ voluntarydba
Like on Facebook:
/ voluntarydba

Наука

Опубликовано:

15 фев 2014

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 24

@harihariprasad3734 5 лет назад

Jon, I love your videos for their content. They are very informative. I also like your delivery style. Thanks for sharing your expertise! Keep up the good work.

@calvint3419 4 года назад

Thank you! This can still be an awesome feature in 2020.

@superrebotar 3 года назад

Great video. Very explanatory and clear. Thank you!

@clesben8716 7 лет назад

Video suggestion: High availability setup and config start to end

@ILoveProjects 5 лет назад

Thanks for the informative video, I like the way you deliver the information - straight to the point. Back in 2005 I was excited by Service Broker (SB) intro, but actual implementation found cumbersome and we stopped supporting SB. Question: in these days (2018) how would you build asynchronous SQL queries processing? Would you still consider SB for messaging?

@VoluntaryDBA 5 лет назад

It depends on the business requirements and what needs to go where. Certainly there are advantages and disadvantages of Service Broker, so... it depends. But I would definitely consider it as an option, especially since it's functionality built into a product that will already be in use in the organization.

@ahmedjawad7350 3 года назад

thanks:)

@lotsa2000 5 лет назад

Thank you for posting this video. I'm wanting to do distributed computing. Right now, our system is dumping into a SB Queue and it activates several threads to process the queue inside of SQL Server. However, the CLR that it is calling downloads HTML from a website and sends it to an SMTP server. For whatever reason, this is much slower than taking the processing outside of SQL Server. I would like to write a distributed .NET Core app that works on the existing queue and make sure that it does not duplicate the work. Our customers do not want to receive multiple emails and they definitely want their email. Before, I relied a lot on SB to handle all of that and now I'm not sure what would happen if one external app received an item and started processing, but didn't complete. I've been searching for applications that have used SB and it is very hard to find them. They almost always use RabbitMQ. What are your thoughts?

@sahwaahmed8054 9 лет назад

broker services receiving requsest and sending and used sql and database

@autecuso 9 лет назад

It sounds like Service Broker could be customized to create a custom company-wide trouble-ticket/change control system when used in coordination with an sql server database. Kewl.

@terasoft-official 8 лет назад

I am happy to know service broker. But SCALEOUT is a totally different concept. This means attaching more outsided resources to handle the load. You have not spoken on that point. How service broker can help on-demand in that regard?

@VoluntaryDBA 8 лет назад

It's possible to send messages to a different database on a different server.

@edgarallanbayron3924 7 лет назад

Hi, why did you stop uploading videos? they are all so useful.

@VoluntaryDBA 7 лет назад

(I'm assuming that was directed at me.) The short answer is that my previous job burned me out doing database stuff, and my new job (since Feb 2015) is in a different field. A lot of the small technical details are gone now. I may come back to this from a different angle in the future, making the occasional reference-style content video, like the last few were.

@edgarallanbayron3924 7 лет назад

Thanks ! Looking forward on this.

@borkasiamese4617 10 лет назад

Hi there! We have not heard from you quite for a long. Is all alright? -Borka

@VoluntaryDBA 10 лет назад

Hi Borka, Everything is fine; thanks for asking. I've just been taking a break from this and working on other projects (not DBA-related). Don't worry, I do intend to make more videos on this channel. :) I also post on dba.stackexchange.com regularly if you haven't seen that site before.

@borkasiamese4617 10 лет назад

Voluntary DBA Thank you for answering and providing additional info - much appreciated! It's nice to hear that you are fine! Looking forward to seeing new videos :) Take care! -- Borka

@jatinverma6759 3 года назад

why aren't you uploading now?

@TheShadowSilencer 10 лет назад

Hi there. This is nice video but very low informative. After 13:38 min I still don't know what Service Broker is and what is the purpose of using it. You are talking like a robot or bored teacher on the same 1001 presentation. Please explain what Service Broker is, what is his purpose in general in simple words, put some simple non-technical diagram of it - like "if there is a 100 application, service broker is able to parallel the request from application or balanced the resources between application requests". In way that almost every technical person will understand. Not only some "few geek developers from your room in school". Come on, it's a video for people. BR,

@TheShadowSilencer 10 лет назад

Oh, and put some energy and positive attitude in your videos. Talking like a robot without any intonation is very hard to listening and understand above 1-2 minutes.