 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Obadiah
Guest
|
 Posted: Thu Aug 21, 2003 4:20 am Post subject: What database management system should I use? Would InterBa |
 |
|
I'm going to be developing a system that will eventually go commercial in a
medical setting...it will have approximately 5-20 users per office (possibly
more).
There may be multiple offices connected via VPN tunnels over the internet (I
think using replication if I understand it correctly...so that data from all
offices is available anywhere, but that local clients access a local server
for speed and reliability).
There will not be an on-site DBA or techie...just people using the system.
I remember hearing at some point that InterBase didn't require the amount of
administration as other client/server databases. Also I like the
possibility of haveing tight integration with Delphi with the InterBase
express components.
What about deploying? Would there be any great difficulties in creating
installs to fully set up and configure a database for use in a commercial
product like this?
I'd be gratefull for any advice / suggestions on this...
|
|
| Back to top |
|
 |
Obadiah
Guest
|
| Posted: Thu Aug 21, 2003 12:22 pm Post subject: Re: What database management system should I use? Would Int |
|
|
Thanks for your response.
Now MSDE is a "desktop" solution, is it not? So with more then a few users
I would need to get a full version of MS SQL Server? Which is another
issue...I beleive SQL Server is much more expensive then Interbase?
"Helmut Wöss" <h.woess (AT) iis-edv (DOT) at> wrote
| Quote: | Hi,
made a big application last year with delphi 5 pro and IBX. Everything
works
fine in my litte office network (3 pc's) but in the network of my customer
where a lot of pc's with different operation systems, different hardware
and
many switches and routers. So i had the problem that more ore less often
the
connection between client and database died. And this is something what
Interbase doesn't like. Without administration the database became more
ond
more bad (consistency errors) and without a full backup/restore all 2 or 3
days it was always the danger that the database wouldn't start up after a
crash (and we had in the middle 5 crashes a day). No i have changed
everything to MSDE and ADO and no more problems since that.
Make a little application wich does some random reads, deletes, updates,
....
by itself and let it run for a day or two. Try to find out what happens
when
you stop and restart the database during the clients are active. This was
my
second problem - catching the errors when the connection was broken!
And MSDE is royalty-free when you buy a sql server developer edition (i
heard it costs only 49$ since this month).
So at least i want to say that Interbase isn't a bad database and had some
features you will miss in sql server, but i had more troubles with it than
with msde. If you will really work with Interbase then try IBObjects, i
never did it but i had a lot more of database programming to do because
IBX
doesn't have the features like IBObjects but you will need them! And maybe
my problems are a result of this overhead programmings, so my tip:
Interbase
(7.1, better buy it than using the free versions!) and IBObjects (not IBX)
or sql server / msde with ADO.
only my 2 cents,
Helmut
"Obadiah" <fr_libertarian (AT) hotmail (DOT) com> schrieb im Newsbeitrag
news:WLX0b.4529$r15.352969 (AT) twister (DOT) southeast.rr.com...
I'm going to be developing a system that will eventually go commercial
in
a
medical setting...it will have approximately 5-20 users per office
(possibly
more).
There may be multiple offices connected via VPN tunnels over the
internet
(I
think using replication if I understand it correctly...so that data from
all
offices is available anywhere, but that local clients access a local
server
for speed and reliability).
There will not be an on-site DBA or techie...just people using the
system.
I remember hearing at some point that InterBase didn't require the
amount
of
administration as other client/server databases. Also I like the
possibility of haveing tight integration with Delphi with the InterBase
express components.
What about deploying? Would there be any great difficulties in creating
installs to fully set up and configure a database for use in a
commercial
product like this?
I'd be gratefull for any advice / suggestions on this...
|
|
|
| Back to top |
|
|
Obadiah
Guest
|
| Posted: Fri Aug 22, 2003 12:09 am Post subject: Re: What database management system should I use? Would Int |
|
|
Ok, thank you. I hadn't considered MSDE before, but will now include it in
my deliberations. :)
"Helmut Wöss" <h.woess (AT) iis-edv (DOT) at> wrote
| Quote: | yes, msde is a desktop solution, but very powerfull. It doesn't stop with
5
connections like many others say, i have more than 20 connections running
at
the same time running 24 hours 7 days a week without any problem. Only the
parallel running batches are limited to 5, the rest ist queued by a
workload
governer and you can check how often this governor stops you with "DBCC
CONCURRENCYVIOLATION" (only under msde, sql server doesn't have this!).
Important is the right programming (no serverside cursors!). If you make
this job bad every database will get problems.
And the other limits (2 Gb per data file, 2 processors) are not really
often
a problem. If you see that msde is not enough you can change from msde to
the sql server model you need without any changes and then your customer
is
surely so big, that costs are not the problem. And please always see the
total costs, not only the costs for the database server - if you have a
problem like i had and you can't solve it, then it becames very fast very
expensive!
Tools for managing msde are available for free or for a very low price,
the
same for Interbase - there is no big difference. Installation of Interbase
is much easier, that's true. But give both a try, make some tests, check
the differences (especially with triggers), think about the server agent
(which you do not have in Interbase) and then decide what you prefer.
And very important: the locking and transaction handling, which works
totally different because msde / sql server has not multiversioning like
Interbase. It's hard to explain for me and both has good and bad sides, so
once again - try it out. My personal favorit is msde!
bye,
Helmut
"Obadiah" <fr_libertarian (AT) hotmail (DOT) com> schrieb im Newsbeitrag
news:yQ21b.6760$r15.377764 (AT) twister (DOT) southeast.rr.com...
Thanks for your response.
Now MSDE is a "desktop" solution, is it not? So with more then a few
users
I would need to get a full version of MS SQL Server? Which is another
issue...I beleive SQL Server is much more expensive then Interbase?
"Helmut Wöss" <h.woess (AT) iis-edv (DOT) at> wrote in message
news:3f4465ae$0$23286$91cee783 (AT) newsreader02 (DOT) highway.telekom.at...
Hi,
made a big application last year with delphi 5 pro and IBX. Everything
works
fine in my litte office network (3 pc's) but in the network of my
customer
where a lot of pc's with different operation systems, different
hardware
and
many switches and routers. So i had the problem that more ore less
often
the
connection between client and database died. And this is something
what
Interbase doesn't like. Without administration the database became
more
ond
more bad (consistency errors) and without a full backup/restore all 2
or
3
days it was always the danger that the database wouldn't start up
after
a
crash (and we had in the middle 5 crashes a day). No i have changed
everything to MSDE and ADO and no more problems since that.
Make a little application wich does some random reads, deletes,
updates,
...
by itself and let it run for a day or two. Try to find out what
happens
when
you stop and restart the database during the clients are active. This
was
my
second problem - catching the errors when the connection was broken!
And MSDE is royalty-free when you buy a sql server developer edition
(i
heard it costs only 49$ since this month).
So at least i want to say that Interbase isn't a bad database and had
some
features you will miss in sql server, but i had more troubles with it
than
with msde. If you will really work with Interbase then try IBObjects,
i
never did it but i had a lot more of database programming to do
because
IBX
doesn't have the features like IBObjects but you will need them! And
maybe
my problems are a result of this overhead programmings, so my tip:
Interbase
(7.1, better buy it than using the free versions!) and IBObjects (not
IBX)
or sql server / msde with ADO.
only my 2 cents,
Helmut
"Obadiah" <fr_libertarian (AT) hotmail (DOT) com> schrieb im Newsbeitrag
news:WLX0b.4529$r15.352969 (AT) twister (DOT) southeast.rr.com...
I'm going to be developing a system that will eventually go
commercial
in
a
medical setting...it will have approximately 5-20 users per office
(possibly
more).
There may be multiple offices connected via VPN tunnels over the
internet
(I
think using replication if I understand it correctly...so that data
from
all
offices is available anywhere, but that local clients access a local
server
for speed and reliability).
There will not be an on-site DBA or techie...just people using the
system.
I remember hearing at some point that InterBase didn't require the
amount
of
administration as other client/server databases. Also I like the
possibility of haveing tight integration with Delphi with the
InterBase
express components.
What about deploying? Would there be any great difficulties in
creating
installs to fully set up and configure a database for use in a
commercial
product like this?
I'd be gratefull for any advice / suggestions on this...
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
