I am learning MSMQ and successfully using it to send email and text messages from a consumer-oriented ASP.NET MVC website for processing by a separate client application.
If there is no SQL Server database, perhaps when exchanging disks or a broken database deployment, would it be advisable to queue time-independent inserts in the local MSMQ queue to improve execution time?
Theoretically, I can pause / resume queue processing (persistence) when making changes to the database. Has anyone tried this or is there a better way?
I was on the team that implemented this with the goal of guaranteed delivery. We used MSMQ to forward the insertion requests to the database server, which was running its own service, which deleted the requests and launched the inserts, and then confirmed the message (to ensure delivery). It has been working for over a year now, and we have never been asked to conclude why it does not work ... it seems pretty solid to me.
, Service Broker, SQL Express, IIS/ASP . SSB MSMQ , ( /, ), , MSMQ , -commit DTC MSMQ DB ( /), (SELECT .. FROM queue), DB HA/DR ( /mirroring ), DB, , T-SQL. MSMQ #/.NET API.
SELECT .. FROM queue
, , . -, - MSMQ , . , , , , , LOB, - , , - .
, . INSERT ( ); - - , , , , .
, MSMQ , , , . , MSMQ .