Re: Database Server based on SQL database

I'm not sure I understand the question - how can you base a "protocol on
SQL"? SQL is a language, not a protocol - they are two different things.

If you are asking if there is some protocol already defined for exchanging
SQL statements and data, you can look at http://www.freetds.org/, which is
an open source implementation of the Tabular Data Stream (TDS) protocol.

TDS originated with Sybase and is used by SQL Server (earlier versions were
based on Sybase).

It's not 100% of what you are looking for - it sounds like you want to write
both the client and the server side. TDS is an implementation of a client
side of a protocol that communicates with a SQL database, but you would need
to write the server side (since the server side is currently SQL Server or
Sybase). But it is a starting point.

A better way might be to just exchange XML. Have the client embed the SQL
in an XML string and send it to your server, execute it, then send the
results back as XML to the client. There's more overhead than a binary
format, so you may need to compress the data stream.

"Angus" <nospam@xxxxxxxxx> wrote in message
news:O89Ii7nCHHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
Thanks but I am quite clear on my requirements. Confusion I think was
with
person who responded.

I have a contact management package which currently talks to a database on
a
LAN. But I want to enable the program to work over a WAN connection.

So I will write a server program which receives requests from clients via
a
socket connection. The requests (eg a request for some data in a row in a
table) will be passed on down to the database via whatever is best/fastest
access method.

So I need a protocol for communication between socket clients and socket
servers. Should I base this protocol on SQL or design my own protocol.
That is essentially the question.

Angus




"Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
news:OS9eQznCHHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
I expect you need to start from your requirements. Since
you didn't post them, I suspect you are not clear what
they are in the first place. Spend the time figuring out
your requirements and then the design should flow in
place with much less confusion...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"Angus" <nospam@xxxxxxxxx> wrote in message
news:%23XioRInCHHA.4312@xxxxxxxxxxxxxxxxxxxxxxx
Maybe I do not understand. Or maybe my question was not clear. The
server
is a socket server. ie you communicate with server via sockets. There
is
a
product from BMC software called Remedy which works in this way. Data
storage is a SQL server. But clients don't talk directly to database -
communication is via socket server.

ie the client doesn't have OLE DB, ADO, DAO or whatever installed -
they
communicate via sockets - and some sort of protocol. That is what I am
trying to design.

Angus



"Vadym Stetsyak" <vadym_s@xxxxxxx> wrote in message
news:O2R9a6lCHHA.4740@xxxxxxxxxxxxxxxxxxxxxxx
Hello, Angus!

What does it mean "based ib SQL database"?

Have you seen DB servers like mySQL?
Its open source, so you can investigate its design.
Have a look at it ( http://www.mysql.org/ )

Also there are a lot of technical papers on MS SQL Server. From these
papers
you can obtain the picture of DB server parts and architecture...

A> I want to build a socket based database server. How should the
A> client
A> communicate with the server? Should I create SQL syntax at the
A> client and
A> let the server pass this onto the database? Does this work? Would
A> creating
A> a totally new custom protocol for the database communication be
A> better?

A> I intuitively feel that that re-inventing the wheel is probably not
A> very
A> clever. And if the client can create the SQL strings that should
A> work ok.
A> But would be interested to hear from anyone who has also written or
A> is
A> writing a database server.

A> Another issue I suppose is buffering. Should the server store the
A> retrieved
A> SQL searches in memory and just pass to client the record they are
A> viewing?
A> Suppose makes sense.

A> Any comments would be greatly appreciated.

A> Angus



--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com








.

Relevant Pages

  • Re: network booting
    ... So the client would need to tell on which offset into on of the ... The client asks the server to open a specific file (by ... component of DOS 3.3, as well as RWTS. ... code on the C64 can send commands (using a serial protocol called IEC) ...
    (comp.sys.apple2)
  • Re: client -server interaction over XML supporting multiple protocols
    ... > NETBEUI to access the server to access the functionalities exposed. ... > server doesnot know in advance which client is using what protocol. ... size of the XML and Xfunctionality will determine the demands ...
    (comp.lang.cpp)
  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now successfully installed them. ... Access front end to a SQL database, Excel can be a front end, A word mail merge document could access a SQL database via ODBC. ... We are trying to install the client software. ... We understand that a Northwind training database is available for SQL Server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • OpenSSH: SSH2 sshd - Increase key size from 2048 to 8192 bits (Cygwin)
    ... I am only using the SSH2 protocol. ... key, normally 768 bits, generated when the server starts. ... The client compares the RSA host key ... the server and the client enter an authentication ...
    (comp.security.ssh)