Design suggestion

[Mustafa Ismail Mustafa]

There is need to acquire a potentially large images (250 KB - 2.5 MB) from the client computer, now this has to be sent over the wire to the central DB. Question is, would it be advantageous to say, insert it into the local DB (on the client) and then have the local DB then post it to the central DB? This way, I should be able to maintain program response time fairly snappy. On the other hand, I could pipe it straight to the central DB asynchronously or on a separate thread. What do you suggest?

If the post was helpful, please vote, eh! Current activities: Book: Devils by Fyodor Dostoyevsky Project: Hospital Automation, final stage Learning: Image analysis, LINQ Now and forever, defiant to the end. What is Multiple Sclerosis[^]?

[Mycroft Holmes]

I would use the second thread method, having a local database that is communicating with the remote server implies WAY too many fracture points.

[Mustafa Ismail Mustafa]

I was thinking that last night.

Mycroft Holmes wrote:

having a local database that is communicating with the remote server implies WAY too many fracture points.

Why fracture points? I see it as a second, local copy/backup if you will. I'd love to hear your thoughts.

If the post was helpful, please vote, eh! Current activities: Book: Devils by Fyodor Dostoyevsky Project: Hospital Automation, final stage Learning: Image analysis, LINQ Now and forever, defiant to the end. What is Multiple Sclerosis[^]?

[Mycroft Holmes]

I see something like a sql express copy locally where you write the graphic to it. Then you need to have the local DB copy/replicate to the server. How were you going to get the local database to move the record to the server.

Never underestimate the power of human stupidity RAH

[Mustafa Ismail Mustafa]

Mycroft Holmes wrote:

I see something like a sql express copy locally where you write the graphic to it. Then you need to have the local DB copy/replicate to the server.

That's exactly what I was thinking of.

Mycroft Holmes wrote:

How were you going to get the local database to move the record to the server.

Most likely a trigger. Once insertion is complete, then the DBs can take their time sending it over the wire.

If the post was helpful, please vote, eh! Current activities: Book: Devils by Fyodor Dostoyevsky Project: Hospital Automation, final stage Learning: Image analysis, LINQ Now and forever, defiant to the end. What is Multiple Sclerosis[^]?

[Mycroft Holmes]

Trigger is how you initiate it, how are you goung to get local db to talk to server db, this is the crucial question as I think your options break down to the following or some kludge connection. Linked server SSIS Web service I'm not sure express supports this tech I would consider installing and maintaining a local db to be an outrageous cost for this requiremment. What happend when you move from Dev/UAT to production servers etc.

Never underestimate the power of human stupidity RAH

[Mustafa Ismail Mustafa]

I was considering a Linked Server but the more I think about it, the less appealing the idea becomes.

If the post was helpful, please vote, eh! Current activities: Book: Devils by Fyodor Dostoyevsky Project: Hospital Automation, final stage Learning: Image analysis, LINQ Now and forever, defiant to the end. What is Multiple Sclerosis[^]?

[Mycroft Holmes]

Mustafa Ismail Mustafa wrote:

appealing

Appealing AAAaahhhh runs screaming from the room Appart from the fact that I don't think express supports linked servers, maitaining and deploying the solution would be plain nasty. Go for the addition thread doing the write back.