Storing Data Locally

I am developing a program that keeps track of manufacturing defects and
deviances. When a product is being developed, if there is a deviance from
the standard, we have to put the part on hold and create a deviation notice
(EPN). I am going to use sharepoint for the EPN notification workflow and
store the EPN data in SQL Server 2005. I am using VB 2008 to do the front
end development. It is critical that the EPN be generated and the part put
on hold regardless if Sharepoint or SQL Server is available (due to a
network outage, or hardware fault in the PC). So I check for network
connection first, and if the network is available, I create the EPN. If the
network is not available, I was thinking of storing the data locally
creating a temp EPN number and allow the operator to put the piece on hold.

The questions I have are:

1. Is there a way for SQL Server 2005 to send a notification when it comes
back online so my program can receive the event and upload the locally saved
data?
2. Can I do an automatic sync with SQL Server 2005 when it comes back
online?
3. What is the best way to store the data locally for processing? Access
Database, text file, etc.


This code has not been written, but I need to architect a solution so any
pointers would be helpful.

Thanks.

John

re: Storing Data Locally

what about using async connection?

Sorry, I don't know about the details

"John Wright" <riley_wright@hotmail.comwrote in message
news:eunZZYUCJHA.4884@TK2MSFTNGP02.phx.gbl...noticethehold.saved

re: Storing Data Locally

John,

As a PC goes down, you cannot store anything anymore.

In other cases isolated storage

http://msdn.microsoft.com/en-us/library/bdts8hk0.aspx

Cor

"John Wright" <riley_wright@hotmail.comschreef in bericht
news:eunZZYUCJHA.4884@TK2MSFTNGP02.phx.gbl...

re: Storing Data Locally

If i understand your requirments correctly then i would go for

Local data storage SQL server Compact edition ( free and exists of only
One Xcopy deployable dll )
For the synchronization part i would go for the synchronization framework
( free downloadable and MS examples availlable )

There are lots of examples for CE devices however you can use it just as
easily for "normal" desktop applications

HTH

Michel Posseth




"John Wright" <riley_wright@hotmail.comschreef in bericht
news:eunZZYUCJHA.4884@TK2MSFTNGP02.phx.gbl...

re: Storing Data Locally

John Wright wrote:
Why? No one else would know that it had been put on hold. It would create an
artifical sense of having completed a task that actually hadn't been completed .

Assuming that "network not available" does not happen very often, I think it
makes much more sense to say no, you can't put it on hold until the network is
back up.

re: Storing Data Locally

On Aug 28, 8:41*pm, "John Wright" <riley_wri...@hotmail.comwrote:Have you considered using SQL Server (either full version or Express)
for the local data and SQL replication for managing the
synchronisation? It sounds like this would be ideal. However, as
pointed out elsewhere in this thread, it would be worth considering
that you could be creating a false sense of security - you may need to
monitor the state of the synchronisation and alert if there is a
network failure and you are relying on temporary local data.