Re: Sending large notifications.
Joe's idea is the best method, but just thought I would share new features
for SQL 2005. There is a new datatype XML that has a max of 2 GB.
Again this is new to SQL 2005, but may be appropriate for your needs.
"Joe Webb" <[email protected]> wrote in message
> Since you're going to create a custom delivery protocol anyway, why
> not have SLQNS only process the primary key for the row you're
> interested in, and then have the custom delivery protocol grab the
> rest of the information for the row?
> Joe Webb
> SQL Server MVP
> Get up to speed quickly with SQLNS
> I support PASS, the Professional Association for SQL Server.
> On 28 Dec 2005 01:33:43 -0800, "SQL Guy" <[email protected]> wrote:
>>I have some clarifications on Notification services.
>>Following is the scenario
>>when a record is updated by a user, the same record needs to be sent to
>>all the other online users. And here we are using notification services
>>for pushing data from the server to the client machines.
>>I have to send the entire dataset row(that got modified/added). So one
>>way of doing that is to get the XML of the Dataset and send this as a
>>part of the notification message by inserting the XML as one of the
>>notification fields. Here the problem that I am facing is, notification
>>fields have a restriction of 8000 characters. For the notification
>>fields, the long data types (like text, ntext etc) are not supported.
>>The questions that I have is
>>Is there some way we can manipulate the notification message that is
>>sent? Only way I could find is setting a notification field with the
>>value. But the problem here is the 8000 characters' limit. Is there
>>any other way?