Re: SQL Server Express versus Access (In the World Series of Love)

Tech-Archive recommends: Fix windows errors by optimizing your registry

Ah, but storing computed values while not the theoretical ideal is sometimes
necessary. Case in point if you're working with a hotel reservation system
and need an screen that displays rooms available for sale a summary table
would be acceptable as the amount of time necessary to compute the
availability (or quantity sold) would take (seemingly) forever.

"Michel Walsh" wrote:

As far as the triggers are concerned, the first case is something to avoid
(storing computed values), unless you want to archive something, but then,
if you archive your data, you don't expect data to change and have other
mechanics to cover such exceptional cases. For the second example, it is
something related to the UI, not to the database engine. Sure, triggers may
have their usefulness, for updateability, but Jet has already updateability
covered automatically over saved query while MS SQL Server requires INSTEAD
OF triggers to achieve the same, say, over view, so, advantage to Jet. Sure,
MS SQL Server may have a horse shoe maker right out of the box, and Jet does
not, but if we don't own horse... is that an advantage?

Vanderghast, Access MVP


"dch3" <dch3@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B012073F-7738-47C4-B273-1B5568C88675@xxxxxxxxxxxxxxxx
I'm a bit concerned that most of the posts seemed to deal with the
interface
and not the inner workings of the underlying Engines - perhaps the thread
should have been entitled SSE versus Jet - as I now realize that was the
question at hand. No one mentioned that SQLServer supports triggers (how
many
times have you had a summary table that you've had to update a value when
the
detail changes? and how often do you have to remember that if you build a
new
screen that allows the detail to be edited that you also have to call the
code that updates the corresponding header record), or the fact that SQL
Server security can be integrated with Windows/Active Directory - not to
mention that it can be setup at the COLUMN level, I would assume that
upsizing from SQL Server Express to Big Daddy SQL Server would be easier
(than Access to SQL Server) as Express is for all basic purposes SQL
Server
with limitations (only 1 processor, max database size 4GB).




.

Relevant Pages

  • Re: New to SQL server
    ... it is called triggers. ... ANYTHING THAT YOU CAN DO IN JET IS BABY TALK COMPARED TO WHAT WE CAN DO ... anything that you can do in JET that I can't do in SQL Server ... self-referencing FKs and inline constraints. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: SQL Server Express versus Access (In the World Series of Love)
    ... As far as the triggers are concerned, the first case is something to avoid ... have their usefulness, for updateability, but Jet has already updateability ... OF triggers to achieve the same, say, over view, so, advantage to Jet. ... MS SQL Server may have a horse shoe maker right out of the box, ...
    (microsoft.public.access.modulesdaovba)
  • Re: SQL Server Express versus Access (In the World Series of Love)
    ... and not the inner workings of the underlying Engines - perhaps the thread ... upsizing from SQL Server Express to Big Daddy SQL Server would be easier ... so installation is easier with Jet. ... Updateability through a join. ...
    (microsoft.public.access.modulesdaovba)
  • Re: trigger counter part
    ... the Jet data engine does not support triggers or similar. ... I said constraints in Jet 4.0 are better than SQL Server ...
    (microsoft.public.access.tablesdbdesign)
  • Re: SQL Server Express versus Access (In the World Series of Love)
    ... If your need involve a form, then triggers are not an appropriate tool: ... after a change in the database. ... OF triggers to achieve the same, say, over view, so, advantage to Jet. ... MS SQL Server may have a horse shoe maker right out of the box, ...
    (microsoft.public.access.modulesdaovba)