Re: Client to Client communication

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@xxxxxxxxxxxxx> wrote in message
news:6AE389B2-A7B3-45E7-974A-4E98AC97A7A8@xxxxxxxxxxxxxxxx
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




.

Loading