Upsizing To SQL Server

[Wayne]

Can anyone point me to any info on the pros and cons of upsizing small
to medium size databases to SQL Server?

If the user base is never going to be more than about 10, the app
isn't totally mission critical and the record count will never get
into the hundreds of thousands, is upsizing even worth considering?

Any help is appreciated.

[lyle]

On Jul 8, 9:55 am, rkc <[e-mail] ba.dabba.do.com wrote:

Wayne wrote:

Thanks all for the feedback. Lyle and David you have confirmed what I
suspected to be the case.

Really? That's all it took?

It dosen't show up in the posting but I copied my response onto a
stone tablet and sent it directly to Wayne by messenger service.
That's probably the reason it was treated as being so authorative. You
think I needed to do the burning bush thing too?

[David W. Fenton]

lyle <ly************ @gmail.comwrote in
news:11******** **************@ o61g2000hsh.goo glegroups.com:

On Jul 8, 9:55 am, rkc <[e-mail] ba.dabba.do.com wrote:

>Wayne wrote:

Thanks all for the feedback. Lyle and David you have confirmed
what I suspected to be the case.

Really? That's all it took?

It dosen't show up in the posting but I copied my response onto a
stone tablet and sent it directly to Wayne by messenger service.
That's probably the reason it was treated as being so authorative.
You think I needed to do the burning bush thing too?

When Lyle and David agree, it must be truth.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Max Vit]

On Jul 9, 10:48 am, "David W. Fenton" <XXXuse...@dfen ton.com.invalid >
wrote:

The answer for both these questions is Windows Terminal Server.

Thanks David - Killed 2 birds with one stone :-)

[Wayne]

Thanks Tony. No, the data is nowhere near as mission critical as the
example you give. There are only a handful of records being entered
each day and the data can be rekeyed if there is a problem. I have
around 30 databases in use, all with Jet backends and I have only had
one data corruption issue caused by a faulty network connection. This
is over a period of about 5 years. I don't know if I've just been
lucky or if this is about average. Most of the systems have only 5
users or so.

My original post was prompted by a discussion that I had on another
forum (not an Access forum) where somebody was adamant that Jet
backends were only for amateurs and they were nothing but trouble.
This just hasn't been my experience.

[lyle fairfield]

Wayne <cq*******@volc anomail.comwrot e in news:1183671296 .673111.180040
@x35g2000prf.go oglegroups.com:

Can anyone point me to any info on the pros and cons of upsizing small
to medium size databases to SQL Server?

If the user base is never going to be more than about 10, the app
isn't totally mission critical and the record count will never get
into the hundreds of thousands, is upsizing even worth considering?

Any help is appreciated.

When we grant SQL permissions to users those permissions are independent
of Access (or any other application, for that matter).
If we create an ADP and connect using the same connection values we have
used in another Access application then all the objects for which we have
permissions will be open to us in that new ADP. But we will not be
constrained in our interaction with these objects by the other Access
application.
We may damage the data; we may have data available to us which we should
not.
I believe ODBC connections can be exploited in the same way, but I am not
familiar enough with ODBC to state that as a certainty.

A solution is to use MS-SQL Application Roles. When we use Application
Roles, a user has no permissions other than to log on. It is the
Application that has or seems to have permissions. Beyond the
application, (in a new ADP for example), the user cannot even see the
database objects, much less interact with them.

Access and Application Roles do not seem to mix well because Application
Roles give permissions to connections and Access may use many default
connections at the same time. Coding to grant those permissions to
connections used for Combo-Boxes, for example, may be a nightmare. (As an
aside I might point out that I am a very experienced VBA coder.) I
estimate using Applications Roles may increase development time by a
factor of three or more.

For these reasons I have stopped recommending the use of Access and MS-
SQL together, although I still enhance and maintain ADP applications for
which I have already wrestled with and defeated, more or less, the
problems of implementing Application Roles.

I have not studied this problem for more than a year; it's possible that
Microsoft has a new solution, or that an old solution existed about which
I am unaware.
But Microsoft's retreat from APDs causes me to guess that this is not
true.
As I pointed out I am not totally clear about how this relates to ODBC
connections; the little I know suggests the problem with be similar, but
I will emphasize the "little I know" here.

--
lyle fairfield

Ceterum censeo Redmond esse delendam

[Tony Toews [MVP]]

Wayne <cq*******@volc anomail.comwrot e:

>Thanks Tony. No, the data is nowhere near as mission critical as the
example you give.

Glad to hear it.

>My original post was prompted by a discussion that I had on another
forum (not an Access forum) where somebody was adamant that Jet
backends were only for amateurs and they were nothing but trouble.

Tell him to come on over hear and make his sentiments know. <chuckle>

>This just hasn't been my experience.

Agreed.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

[David W. Fenton]

Wayne <cq*******@volc anomail.comwrot e in
news:11******** **************@ i38g2000prf.goo glegroups.com:

I have
around 30 databases in use, all with Jet backends and I have only
had one data corruption issue caused by a faulty network
connection. This is over a period of about 5 years. I don't know
if I've just been lucky or if this is about average.

I'd call that average, not lucky.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/