|
Home > Archive > SQL Anywhere database > May 2005 > iAnyWhere 8.0 server version
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
iAnyWhere 8.0 server version
|
|
|
| I new to this group, but I have used different versions of SQL anywhere in
my past. Those were a single-user copies, never had attention to use this
product as a server based with multiple connections.
This time a have group of clients who have local copies installed on their
desktops and now they are asking me to convert their local installations
into a centralize database with multi-user connections through their local
network. I am thinking to install a server version of iAnyWhere, and fonder
what would be the effort of doing it. Is there a white papers for
installation and maintenance of network version of it?
Please share your experience with that being a server version, whether they
good or bad,
Any comments would be greatly appreciated!
Thanks!
| |
| Breck Carter [TeamSybase] 2005-05-19, 8:23 pm |
| The network server dbsrv8.exe is *exactly* the same as the standalone
engine dbeng8.exe, except for the fact that it accepts connections
across a network (the standalone engine only accepts connections from
the same computer). The network server works wonderfully well with
hundreds or thousands of users connected.
Here is an example of a typical server start line; it allocates 256M
to the cache, saves the console log to a text file, enables tcp/ip
network communications, and starts the database xxx. When you connect
to this database, the "database name" and the "server name" both
default to xxx, the file name portion of the database file.
" %ASANY9%\win32\dbsrv
9.exe" -c 256M -o console.txt -x tcpip xxx.db
You can also run the server as a Windows service or a *nix daemon.
You will have to take care in your programming to perform frequent
COMMIT operations after updates, otherwise one user's actions will
block other users because row locks will be held a long time.
Multi-user application design is somewhat more difficult than
single-user design.
BTW, the current version is 9.0.2.
Breck
On 19 May 2005 11:02:13 -0700, "Serge"
< serguei_antonov@stan
dardandpoors.com> wrote:
>I new to this group, but I have used different versions of SQL anywhere in
>my past. Those were a single-user copies, never had attention to use this
>product as a server based with multiple connections.
>
>This time a have group of clients who have local copies installed on their
>desktops and now they are asking me to convert their local installations
>into a centralize database with multi-user connections through their local
>network. I am thinking to install a server version of iAnyWhere, and fonder
>what would be the effort of doing it. Is there a white papers for
>installation and maintenance of network version of it?
>
>Please share your experience with that being a server version, whether they
>good or bad,
>
>Any comments would be greatly appreciated!
>
>
>
>Thanks!
>
>
>
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
|
|
Thanks Breck, your help is very much appreciated!
"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:62sp81163kncf1l
bc3ibgp83ju988bdl1n@
4ax.com...
> The network server dbsrv8.exe is *exactly* the same as the standalone
> engine dbeng8.exe, except for the fact that it accepts connections
> across a network (the standalone engine only accepts connections from
> the same computer). The network server works wonderfully well with
> hundreds or thousands of users connected.
>
> Here is an example of a typical server start line; it allocates 256M
> to the cache, saves the console log to a text file, enables tcp/ip
> network communications, and starts the database xxx. When you connect
> to this database, the "database name" and the "server name" both
> default to xxx, the file name portion of the database file.
>
> " %ASANY9%\win32\dbsrv
9.exe" -c 256M -o console.txt -x tcpip xxx.db
>
> You can also run the server as a Windows service or a *nix daemon.
>
> You will have to take care in your programming to perform frequent
> COMMIT operations after updates, otherwise one user's actions will
> block other users because row locks will be held a long time.
> Multi-user application design is somewhat more difficult than
> single-user design.
>
> BTW, the current version is 9.0.2.
>
> Breck
>
> On 19 May 2005 11:02:13 -0700, "Serge"
> < serguei_antonov@stan
dardandpoors.com> wrote:
>
in[color=darkred]
their[color=darkred]
local[color=darkred]
fonder[color=darkred
]
they[color=darkred]
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
http://www.amazon.com/exec/obidos/A...7/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com
|
|
|
|
|