| Author |
Upsizing to SQL Server
|
|
|
| We are upsizing our current Access 97 application to SQL Server. We are
doing this in a phased approach. First we are going to upsize the tables.
We are then going to link to the SQL tables from the current Access FE. I
read that we will have limitations in terms of the number of users the
application will be able to support using this configuration from the book
Microsoft Access Developer's Guide to SQL Server by Mary Chipman and Andy
Brown. I understand that this configuration will consume more resources on
the network and server. Is this causing the limit on the number of users?
About how many concurrent users should we be able to support using this
configuration? Thanks for your help.
| |
| Pat Hartman 2005-04-22, 8:24 pm |
| If you are using SQL server you shouldn't run into limitations as long as
you have SQL server licenses for everyone. The limitation was probably
referring to MSDE. That is a crippled version of SQL server that ships with
A2K and newer.
"Weste" <Weste@discussions.microsoft.com> wrote in message
news:3782DDBE-11DE-4523-B06E- C6719916CFE8@microso
ft.com...
> We are upsizing our current Access 97 application to SQL Server. We are
> doing this in a phased approach. First we are going to upsize the tables.
> We are then going to link to the SQL tables from the current Access FE. I
> read that we will have limitations in terms of the number of users the
> application will be able to support using this configuration from the book
> Microsoft Access Developer's Guide to SQL Server by Mary Chipman and Andy
> Brown. I understand that this configuration will consume more resources
on
> the network and server. Is this causing the limit on the number of users?
> About how many concurrent users should we be able to support using this
> configuration? Thanks for your help.
>
| |
| Robert1105 2005-06-10, 8:25 pm |
| We are migrating from Jet to MSDE with Access 2000. Are the user limitation
the same in both? Should we be able to support the same number of concurrent
sessions with MSDE as we did with Jet. It seems that this should be the
case. I was just wonder what the real world experience is with this?
When you say MSDE is a "clipped" version of SQL, what is done to clip the
MSDE?
Regards,
"Pat Hartman" wrote:
> If you are using SQL server you shouldn't run into limitations as long as
> you have SQL server licenses for everyone. The limitation was probably
> referring to MSDE. That is a crippled version of SQL server that ships with
> A2K and newer.
>
> "Weste" <Weste@discussions.microsoft.com> wrote in message
> news:3782DDBE-11DE-4523-B06E- C6719916CFE8@microso
ft.com...
> on
>
>
>
| |
| qinglianzhou 2005-08-04, 9:26 am |
| 00
"Robert1105" < Robert1105@discussio
ns.microsoft.com> 写入消息新闻
:9DD1C57D-058C-4EB4-B318- D9A2535963BF@microso
ft.com...
> We are migrating from Jet to MSDE with Access 2000. Are the user
limitation
> the same in both? Should we be able to support the same number of
concurrent[color=dar
kred]
> sessions with MSDE as we did with Jet. It seems that this should be the
> case. I was just wonder what the real world experience is with this?
>
> When you say MSDE is a "clipped" version of SQL, what is done to clip the
> MSDE?
>
> Regards,
>
> "Pat Hartman" wrote:
>
as[color=darkred]
with[color=darkred]
are[color=darkred]
tables.[color=darkred]
FE. I[color=darkred]
the[color=darkred]
book[color=darkred]
Andy[color=darkred]
resources[color=dark
red]
users?[color=darkred]
this[color=darkred]
|
|
|
|