Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Author |
Message |
Duane Foot #1 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Hey People, I am trying to create a middle tier exe that can act as a communicator between my databsae adn my front end. My software is going to be written in VB.net with SQL Server 2000 as my backend. This communicator will be a Gateway bew{*filter*} my front end and back end. I am doing this because if I have my gui talk to my Sql 2000, I have a large load on the server (no matter how powerful it is). I want to be able to take some of the stress off the server cpu usage.This app has constant streaming of data back and forth between the server and the client.it is somewhat of a thin client setup where some of the work is done at the client and some of it is dont at the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 04:41:47 GMT |
|
 |
Richard T. Edward #2 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Your architecture is going to cost you more with respect to resources, CPU usage and legacy code maintainence than what it is going to be worth. Don't you realize that you can talk to SQL server on its own port?
Quote: > Hey People, > I am trying to create a middle tier exe that can act as a communicator > between my databsae adn my front end. My software is going to be written in > VB.net with SQL Server 2000 as my backend. This communicator will be a > Gateway bew{*filter*} my front end and back end. I am doing this because if I > have my gui talk to my Sql 2000, I have a large load on the server (no > matter how powerful it is). I want to be able to take some of the stress > off the server cpu usage.This app has constant streaming of data back and > forth between the server and the client.it is somewhat of a thin client > setup where some of the work is done at the client and some of it is dont at > the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 05:12:23 GMT |
|
 |
Duane Foot #3 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
I understand that, liek I said, the way the software was written, previously(and I am not going to change that not enough time) I need a middle communicator because the constant hitting of the SQL server form 50-100 clients tends to bring a major load on the server. This app communicates to soem hardware. THis hardware returns information to the communicator and too the gui on teh Server, then this informaiton has to be broadcasted out to from 5-100 clients. And most of the time it is a constant thing.
Quote: > Your architecture is going to cost you more with respect to resources, CPU > usage and legacy code maintainence than what it is going to be worth. > Don't you realize that you can talk to SQL server on its own port?
> > Hey People, > > I am trying to create a middle tier exe that can act as a communicator > > between my databsae adn my front end. My software is going to be written > in > > VB.net with SQL Server 2000 as my backend. This communicator will be a > > Gateway bew{*filter*} my front end and back end. I am doing this because if I > > have my gui talk to my Sql 2000, I have a large load on the server (no > > matter how powerful it is). I want to be able to take some of the stress > > off the server cpu usage.This app has constant streaming of data back and > > forth between the server and the client.it is somewhat of a thin client > > setup where some of the work is done at the client and some of it is dont > at > > the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 06:18:13 GMT |
|
 |
Richard T. Edward #4 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Well, what do you have so far? Are you wanting code? Or just ideas?
Quote: > I understand that, liek I said, the way the software was written, > previously(and I am not going to change that not enough time) I need a > middle communicator because the constant hitting of the SQL server form > 50-100 clients tends to bring a major load on the server. This app > communicates to soem hardware. THis hardware returns information to the > communicator and too the gui on teh Server, then this informaiton has to be > broadcasted out to from 5-100 clients. And most of the time it is a > constant thing.
> > Your architecture is going to cost you more with respect to resources, CPU > > usage and legacy code maintainence than what it is going to be worth. > > Don't you realize that you can talk to SQL server on its own port?
> > > Hey People, > > > I am trying to create a middle tier exe that can act as a > communicator > > > between my databsae adn my front end. My software is going to be > written > > in > > > VB.net with SQL Server 2000 as my backend. This communicator will be a > > > Gateway bew{*filter*} my front end and back end. I am doing this because if I > > > have my gui talk to my Sql 2000, I have a large load on the server (no > > > matter how powerful it is). I want to be able to take some of the > stress > > > off the server cpu usage.This app has constant streaming of data back > and > > > forth between the server and the client.it is somewhat of a thin client > > > setup where some of the work is done at the client and some of it is > dont > > at > > > the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 06:44:27 GMT |
|
 |
Duane Foot #5 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Ideas? I dont code.
Quote: > Well, what do you have so far? > Are you wanting code? Or just ideas?
> > I understand that, liek I said, the way the software was written, > > previously(and I am not going to change that not enough time) I need a > > middle communicator because the constant hitting of the SQL server form > > 50-100 clients tends to bring a major load on the server. This app > > communicates to soem hardware. THis hardware returns information to the > > communicator and too the gui on teh Server, then this informaiton has to > be > > broadcasted out to from 5-100 clients. And most of the time it is a > > constant thing.
> > > Your architecture is going to cost you more with respect to resources, > CPU > > > usage and legacy code maintainence than what it is going to be worth. > > > Don't you realize that you can talk to SQL server on its own port?
> > > > Hey People, > > > > I am trying to create a middle tier exe that can act as a > > communicator > > > > between my databsae adn my front end. My software is going to be > > written > > > in > > > > VB.net with SQL Server 2000 as my backend. This communicator will be > a > > > > Gateway bew{*filter*} my front end and back end. I am doing this because if > I > > > > have my gui talk to my Sql 2000, I have a large load on the server (no > > > > matter how powerful it is). I want to be able to take some of the > > stress > > > > off the server cpu usage.This app has constant streaming of data back > > and > > > > forth between the server and the client.it is somewhat of a thin > client > > > > setup where some of the work is done at the client and some of it is > > dont > > > at > > > > the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 12:22:50 GMT |
|
 |
Keith Ro #6 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
You could create a TCP/IP client much like a chat client (example available at http://www.*-*-*.com/ N-US/101VBNETSamples.exe under "VB.NET - Advanced .NET Framework (Networking) - Use Sockets"). You could send the data from the device to the server piece and then broadcast it out to all of the clients. During processing of your data, you could also save it to the database if that is needed.
Quote: > Ideas? I dont code.
> > Well, what do you have so far? > > Are you wanting code? Or just ideas?
> > > I understand that, liek I said, the way the software was written, > > > previously(and I am not going to change that not enough time) I need a > > > middle communicator because the constant hitting of the SQL server form > > > 50-100 clients tends to bring a major load on the server. This app > > > communicates to soem hardware. THis hardware returns information to the > > > communicator and too the gui on teh Server, then this informaiton has to > > be > > > broadcasted out to from 5-100 clients. And most of the time it is a > > > constant thing.
> > > > Your architecture is going to cost you more with respect to resources, > > CPU > > > > usage and legacy code maintainence than what it is going to be worth. > > > > Don't you realize that you can talk to SQL server on its own port?
> > > > > Hey People, > > > > > I am trying to create a middle tier exe that can act as a > > > communicator > > > > > between my databsae adn my front end. My software is going to be > > > written > > > > in > > > > > VB.net with SQL Server 2000 as my backend. This communicator will > be > > a > > > > > Gateway bew{*filter*} my front end and back end. I am doing this because > if > > I > > > > > have my gui talk to my Sql 2000, I have a large load on the server > (no > > > > > matter how powerful it is). I want to be able to take some of the > > > stress > > > > > off the server cpu usage.This app has constant streaming of data > back > > > and > > > > > forth between the server and the client.it is somewhat of a thin > > client > > > > > setup where some of the work is done at the client and some of it is > > > dont > > > > at > > > > > the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 14:10:53 GMT |
|
 |
Duane Foot #7 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
THanks KEith but the Link does not work. I would like to read up on it. Could you post it agian
Quote: > You could create a TCP/IP client much like a chat client (example available > at
http://www.*-*-*.com/ Quote: > N-US/101VBNETSamples.exe under "VB.NET - Advanced .NET Framework > (Networking) - Use Sockets"). You could send the data from the device to > the server piece and then broadcast it out to all of the clients. During > processing of your data, you could also save it to the database if that is > needed.
> > Ideas? I dont code.
> > > Well, what do you have so far? > > > Are you wanting code? Or just ideas?
> > > > I understand that, liek I said, the way the software was written, > > > > previously(and I am not going to change that not enough time) I need a > > > > middle communicator because the constant hitting of the SQL server > form > > > > 50-100 clients tends to bring a major load on the server. This app > > > > communicates to soem hardware. THis hardware returns information to > the > > > > communicator and too the gui on teh Server, then this informaiton has > to > > > be > > > > broadcasted out to from 5-100 clients. And most of the time it is a > > > > constant thing.
> > > > > Your architecture is going to cost you more with respect to > resources, > > > CPU > > > > > usage and legacy code maintainence than what it is going to be > worth. > > > > > Don't you realize that you can talk to SQL server on its own port?
> > > > > > Hey People, > > > > > > I am trying to create a middle tier exe that can act as a > > > > communicator > > > > > > between my databsae adn my front end. My software is going to be > > > > written > > > > > in > > > > > > VB.net with SQL Server 2000 as my backend. This communicator will > > be > > > a > > > > > > Gateway bew{*filter*} my front end and back end. I am doing this > because > > if > > > I > > > > > > have my gui talk to my Sql 2000, I have a large load on the server > > (no > > > > > > matter how powerful it is). I want to be able to take some of the > > > > stress > > > > > > off the server cpu usage.This app has constant streaming of data > > back > > > > and > > > > > > forth between the server and the client.it is somewhat of a thin > > > client > > > > > > setup where some of the work is done at the client and some of it > is > > > > dont > > > > > at > > > > > > the server. Any ideas on how to start with this communicator
|
Tue, 10 May 2005 21:46:31 GMT |
|
 |
Andre #8 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Maybe you could implement an architecture built that way: Server Side - Sql server 2000 + .NET components .dll (with business server- logic) Client Side - .NET .exe assemblies as GUI - .NET Components .dll (with client logic and data access using Dataset in a disconnected way, can communicate with the server components) The .exe assemblies could be loaded and cached to the clients (until you don't modify them) and can be run under .NET security runtime (sand-box secure mode). They can give you a rich client GUI. Another approach should use ASP.NET and a web server (with a stateless soluton).
Quote: > Hey People, > I am trying to create a middle tier exe that can act as a communicator > between my databsae adn my front end. My software is going to be written in > VB.net with SQL Server 2000 as my backend. This communicator will be a > Gateway bew{*filter*} my front end and back end. I am doing this because if I > have my gui talk to my Sql 2000, I have a large load on the server (no > matter how powerful it is). I want to be able to take some of the stress > off the server cpu usage.This app has constant streaming of data back and > forth between the server and the client.it is somewhat of a thin client > setup where some of the work is done at the client and some of it is dont at > the server. Any ideas on how to start with this communicator
|
Sat, 14 May 2005 23:02:29 GMT |
|
 |
Andre #9 / 9
|
 Trying to Create a communicator for VB.net Front End and SQL 2000 back end
Sorry, I forgot the URL :-) http://msdn.microsoft.com/netframework/techinfo/articles/smartclient/... .asp
|
Sat, 14 May 2005 23:11:46 GMT |
|
|
|