Client to Client communication

Hello,
I have a SQL Server 2005 Database. On some clients (I will call that input
clients) users will enter data and on some other clients these Data will be
used.
Well, I want to avoid, that the other clients have to poll the database all
the time for changes. I thought of somethig like an event which will be rised
at the input client and catched at the other clients.
Is there any possibility to do something like that direct with the SQL
Server (Express) where all the clients are connected to?
Or do I have to write my own server application where the clients have to
connect too and make my own network communication through sockets ect.
Note: The application is ought to work with the SQL Server 2005 Express by
default (for smaller databases), but will be abel to use the SQL Server 2005
also.
thanks, Robert
You could use Global ##Temp tables.
But then again, you will still be using a table on the server, and the
clients will have to poll that table for changes.
But if you were using Notification Services, the clients could be notified
that the changed data is available. (Of course, Notification Services is NOT
included with SQL Express.)
Basically, you are 'butting heads' with the design paradigm of SQL Server.
It is a data STORAGE and RETREIVAL service, NOT a COMMUNICATION service. You
may need to create your own communication service.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"rfw68" <rfw68@.nospam.nospam> wrote in message
news:6AE389B2-A7B3-45E7-974A-4E98AC97A7A8@.microsoft.com...
> Hello,
> I have a SQL Server 2005 Database. On some clients (I will call that input
> clients) users will enter data and on some other clients these Data will
> be
> used.
> Well, I want to avoid, that the other clients have to poll the database
> all
> the time for changes. I thought of somethig like an event which will be
> rised
> at the input client and catched at the other clients.
> Is there any possibility to do something like that direct with the SQL
> Server (Express) where all the clients are connected to?
> Or do I have to write my own server application where the clients have to
> connect too and make my own network communication through sockets ect.
> Note: The application is ought to work with the SQL Server 2005 Express by
> default (for smaller databases), but will be abel to use the SQL Server
> 2005
> also.
> thanks, Robert
>
|||Hello Robert,,
I agree with Arnie that SQL Server is not meant to do this job since it's
mainly for data storage and retrivial.
As Arnie mentioned, Notification service can be used to do this type of
jobs but it is not included in Express edition.
Notification Services
http://www.microsoft.com/sql/technologies/notification/default.mspx
An Introduction to SQL Server Notification Services
http://www.codeproject.com/dotnet/sqlns.asp
Usually you could add subscription to your application so that it could be
notified when data is changed on the server side, and client application
can retrival the newest data at this time.
If you don't want to use Notification Services, you may need to develop
your own service on server side to monitor the data change in SQL Server
and notfiy the clients. Since many users may change data concurrently, I
think it is usually not realistic for it to notifiy other clients by using
client-client communication. A central point might be a better option for
this situation.
If you have any comments or feedback, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
I think that our SocketPro can help you out easily at www.udaparts.com
See the article "
Notify your coworkers any messages anywhere
" at http://www.udaparts.com/document/articles/chatservice.htm
Also, see the tutorial 2 inside the package SocketPro for our chat
service.
Regards,
"rfw68" <rfw68@.nospam.nospam> wrote in message
news:6AE389B2-A7B3-45E7-974A-4E98AC97A7A8@.microsoft.com...
> Hello,
> I have a SQL Server 2005 Database. On some clients (I will call that input
> clients) users will enter data and on some other clients these Data will
> be
> used.
> Well, I want to avoid, that the other clients have to poll the database
> all
> the time for changes. I thought of somethig like an event which will be
> rised
> at the input client and catched at the other clients.
> Is there any possibility to do something like that direct with the SQL
> Server (Express) where all the clients are connected to?
> Or do I have to write my own server application where the clients have to
> connect too and make my own network communication through sockets ect.
> Note: The application is ought to work with the SQL Server 2005 Express by
> default (for smaller databases), but will be abel to use the SQL Server
> 2005
> also.
> thanks, Robert
>