Lubomir
Sat Mar 17 12:43:05 CDT 2007
Thanks for help. I think SQLDpendecy could be fine after all.
Lubomir
"Remus Rusanu [MSFT]" wrote:
> If the updates of the data are rare, you can subscribe to query notification
> w/o using SQL Dependency. Clients can check each time they connect if a
> notification was sent, and if so they need to update the dataset.
> That being said, a SQL Express instance wiht 'much more' than hudrends of
> clients is not gonna work for many other reasons (CPU scheduler limitations,
> database sizes etc etc), as even if clients connect seldom, there will be
> spikes when many clients want to connect and the SQL Express will not be
> able to handle them.
>
>
> "Lubomir" <Lubomir@discussions.microsoft.com> wrote in message
> news:40E32875-186E-46FE-9D23-9E0C969185FB@microsoft.com...
> > There will be much more clients probably. We can not leave connecitons
> > open.
> > However, the there will not be many transmitted data.
> >
> >
> > "Remus Rusanu [MSFT]" wrote:
> >
> >> Query Notification can detect changes in the dataset a client is
> >> interested:
> >>
http://msdn2.microsoft.com/en-us/library/t9x04ed2.aspx
> >> The clients can use the ADO.Net wrappers: SqlNotifications or
> >> SqlDependency.
> >>
> >> How many clients are we talking about? SqlDependency keeps a connection
> >> open
> >> blocked in a WAITFOR(RECEIVE), therefore cosnsumming a thread on the
> >> server,
> >> for each appdomain that called SqlDendency.Start(), so this cannot scale
> >> high (hundreds of clients), but since you say is SQL Express, probably
> >> you're scale is small to start with.
> >>
> >> HTH,
> >> ~ Remus
> >>
> >>
> >> "Lubomir" <Lubomir@discussions.microsoft.com> wrote in message
> >> news:4F0075C6-37CA-4F2C-B4B4-C1BF04732BDC@microsoft.com...
> >> > Hi,
> >> >
> >> > We would like to use MS SQL Server Express database for out data. The
> >> > data
> >> > can be updated by many clients.
> >> >
> >> > There will be an application that will show these data. This
> >> > application
> >> > can
> >> > work with the disconnected recordest.
> >> >
> >> > My question is, how to notify this application, about the data in
> >> > recordset
> >> > are not valid anymore, because the table in the database had been
> >> > changed
> >> > by
> >> > a client?
> >> >
> >> > As I understand, I can not use Notification Services with SQL Express.
> >> >
> >> > 1/ Is the trigger that would send message to the Service broker
> >> > suitable
> >> > for
> >> > this scenario?
> >> >
> >> > 2/ Can I use Event notification? I think they don't work with DML
> >> >
> >> > 3/ What would be the best way to inform *.exe app that the disconnected
> >> > recodset is not valid?
> >> >
> >> > Thanks for any ideas.
> >> >
> >> > Lubomir
> >> >
> >> >
> >>
> >>
> >>
>
>
>