Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2000 Forums  SQL Server Development (2000)  MSMQ + SQL 2k

Author  Topic  MichaelP Jedi Yak 2489 Posts Posted - 2002-02-18 : 14:48:20 I'm working on an app that sends updates to a DB. I have to make 100% sure that the update happens. We have a clustered DB server, so there are times when the server could be unavailable when calling these updates. We've tried handling the error and retrying, but that doesn't seem like a very elegant solution, and is sometimes unsuccessful (failing after 3 tries). I was looking into MSMQ to make sure all updates happen, even if the DB server reboots, catches fire etc. My "client" PC's are NT 4.0 so I can't use COM+ Queued Components like I would like to. MSMQ requires you to send a string of text, or an object that supports the IPersistStream interface. I'm trying to call a stored pocedure. The ADO Command object does not support the IPersistStream interface, so I can't send that across MSMQ. The only solution seems to be send some sort of "command string" that I create and I have to parse on the server end to actually call the stored proc. I'm currently looking at sending an ADO recordset as the "message" and doing an rs.Update once the message reaches the server. I'm not sure if I like that solution, and i'm not sure on the implications of such. There must be a better way. Does anyone know of one?? Any suggestions to make sure that an update happens? TIA guys and gals! Michael