MultiUser Environment Winforms

22 Feb 2007 2:12 PM

AnikSol

Development Environment: VB 2005 Prof, SQL Server 2005

In a typical Multi User environment, what is the best way to handle updates
of disconnected datasets of other users.

Eg: User A opens application Winform 1, dataset1 is loaded on his machine
User B opens application Winform 1, dataset1 is loaded on his machine as
well.

Say User A makes changes to Dataset1 and the database has been updated with
the changes. But since User B is either doing something else or may be
editing some records, how to make sure that UserB dataset also gets updated
with the new values from the db.

Any practical / implemented ideas?

Thanks

There have been replies to this post on the windows.databinding forum.

Since SQLDependency cannot be used in SQLServer Express, are there any other
alternatives other than forcing the end client to use SQL Server 2005
Standard Edition?

thanks

22 Feb 2007 3:01 PM

Kerry Moorman

AnikSol,

The standard approach in a disconnected architecture such as ADO.Net
datasets is to use optimistic concurrency and deal with any problems at
update time.

If that won't work for you (although it seems to work for the vast majority
of applications) then you need to use a connected architecture.

In my opinion, chasing this idea of change notification to all users in a
disconnected environment is never going to work to anyone's satisfaction.

Kerry Moorman

Show quote

"AnikSol" wrote:

>
> Development Environment: VB 2005 Prof, SQL Server 2005
>
> In a typical Multi User environment, what is the best way to handle updates
> of disconnected datasets of other users.
>
> Eg: User A opens application Winform 1, dataset1 is loaded on his machine
> User B opens application Winform 1, dataset1 is loaded on his machine as
> well.
>
> Say User A makes changes to Dataset1 and the database has been updated with
> the changes. But since User B is either doing something else or may be
> editing some records, how to make sure that UserB dataset also gets updated
> with the new values from the db.
>
> Any practical / implemented ideas?
>
> Thanks
>
> There have been replies to this post on the windows.databinding forum.
>
> Since SQLDependency cannot be used in SQLServer Express, are there any other
> alternatives other than forcing the end client to use SQL Server 2005
> Standard Edition?
>
> thanks
>
>
>
>
>
>

23 Feb 2007 8:34 AM

WenYuan Wang

Hi AnikSol,

SQLDependency should be a good approach for you. Additionally, SQL Server
Express also support SQLDependency. Many people misunderstand that because
SQL Server 2005 Express does not support the notification service, we will
not be able to perform Query Notification in SQL Server 2005 Express. In
fact, Query Notifications has nothing common with SQL Server Notification
Services. It should also work on SQL Server Express even though you haven't
installed Notification Services on SQL. What's the different is we should
have to create a broker endpoint for the Service Broker.

Below is a sample for ASP.net, but it still will work for WinForm.
http://blogs.ipona.com/davids/archive/2006/06/05/4757.aspx
[SQL Server Dependencies]

Hope this helps. Please don't hesitate to let me know if you have anything
unclear.
Sincerely,
Wen Yuan

23 Feb 2007 9:24 AM

AnikSol

Wen,

Thanks. I had googled enough on this topic and could see a lot of confusion.

Your message clarifies all.

regards

""WenYuan Wang"" <v-wyw***@online.microsoft.com> wrote in message
Show quote

news:Q9SSuVyVHHA.4088@TK2MSFTNGHUB02.phx.gbl...
> Hi AnikSol,
>
> SQLDependency should be a good approach for you. Additionally, SQL Server
> Express also support SQLDependency. Many people misunderstand that because
> SQL Server 2005 Express does not support the notification service, we will
> not be able to perform Query Notification in SQL Server 2005 Express. In
> fact, Query Notifications has nothing common with SQL Server Notification
> Services. It should also work on SQL Server Express even though you
> haven't
> installed Notification Services on SQL. What's the different is we should
> have to create a broker endpoint for the Service Broker.
>
> Below is a sample for ASP.net, but it still will work for WinForm.
> http://blogs.ipona.com/davids/archive/2006/06/05/4757.aspx
> [SQL Server Dependencies]
>
> Hope this helps. Please don't hesitate to let me know if you have anything
> unclear.
> Sincerely,
> Wen Yuan
>