msmq - Can someone tell me if SQL Server Service Broker is needed for this scenario? -
my first ever question on stack overflow please go easy. have long running windows application continually processes sql server commands. have web front end users use use update same db. i've noticed (depending on windows application processing @ time) if user submits db receive out of memory exceptions on server. realise need dig around bit more , optimise code. cannot afford server go down , expect in future i'll allowing more , more users on frontend. need system queue users requests (they not time critical) , process them when db ready.
i'm using sql 2012 express.
is sql service broker best solution, i've looked msmq.
if can point me in right direction appreciate. in search i'm finding lot of things don't think need.
cheers
it depends on you're doing persistence work, , / or calculations. if you're doing hard work in windows application, using service broker queue won't worthwhile, doing receiving message service broker queue in windows application, doing calculations , / or queries windows application, , persisting results database: database under memory pressure, seems unnecessary load queue , retrieve message msmq (or other queueing technology).
if doing work in database , windows application acts marshalling service - eg taking request , palming off stored procedure actioning - service broker queues may worth using: because operating within context of database, can efficient @ persisting amd querying data.
you want take failure modes, depending on whether or not can afford lose messages. ensure message persistence in msmq have use transactional messaging: service broker more efficient @ transactional queue processing msmq (because has transaction support built in, unlike msmq has use dtc, adds overhead) - if volume of messages low, may not issue.
Comments
Post a Comment