[
Lists Home |
Date Index |
Thread Index
]
On 4/20/05, Ken North <kennorth@sbcglobal.net> wrote:
> >> and I'm hearing it for XQuery as the interface to XML DBMS or XML types in an
> RDBMS
>
> Some SQL platforms provide a tight integration of the database engine with
> message queues and queuing functions. You can, for example, run SQL stored
> procedures to compose documents and place them in MQ Series message queue or
> shred a document in a SOAP message in a queue.
>
> You can run XQuery over message queues stored in the database.
>
> Now consider the .NET environment, MSMQ and SQL Server 2005. Without message
> queues in SQL Server databases, how do I run XQuery against messages? Use a
> third-party processor?
Are you familiar with the SQL Server 2005 Service Broker that is
"enables faster and easier development of SQL Server applications that
rely upon asynchronous, queued operations."
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sqlsvcbroker.asp
I'm not too clear on its relationship to XQuery myself, but this is
something I'm hoping to learn more about soon. Perhaps one of my more
knowledgeable colleagues could help me out here :-)
I definitely think that there are interesting use cases for building
messaging in the database. I'm not clear on how this relates to
Jonathan's point, however. Do you think having XQuery support in .NET
would make it easier to run XQuery against messages. I would think
that this would be a desirable DB engine feature, and that is where MS
have focused our XQuery efforts.
|
