Is Replication Too Much

We are developing a system for a manufacturing operation. The planned
approach is to develop stand alone data capture applications using MSDE for
the database. The production data from these systems needs to be posted to a
central SQL database. All systems will be in the same building. We plan to
roll out this system to a number of facilities. The number of data capture
systems could range from 5 to 25. Data Transfer requirements include: 1)
Master data from the central system will need to be sent to the data capture
machines (updated 4 times a day). 2) Production order informtation will be
sent to 1 or more data capture machines (updated as orders are scheduled to
production lines). 3) Production data from the data capture machines will
need to be sent in a timely manner because 4) Summary Production data (totals
by production order and material) is needed by the data capture machines to
prevent overruns.
The current application we have uses a separate VB application to update the
stand alone and central database. Users are given a message when the central
database cannot be accesssed, however, the stand alone machines must continue
working.
Would replication be a good design for this scenario? or is it overkill? I
have heard the replication is a resource hog, we will have only the central
server to work with.
Other information:
Production data on the stand alones need only be kept for a few days, after
that it can be purged.
Production records (single table) can be created every 6 seconds, updates to
central database can be queued.
Master data consist of 6 tables that are used for look up purposes by the
application running on the stand alone systems.
There are 2 production tables (Header and detail). Application displays
summary production (for detail record) by current system and across all
systems.
Thanks in advance for you help
Who told you replication is a resource hog? Running on property sized
hardware and with a well designed topology (minimal use of filters, etc),
the performance impact should range around 10% or less. If you are running
this on Pentium III hardware naturally performance will not be optimal.
Running it on Pentium IV 2 GHz or more (or some of the modern AMD
processors) with ample RAM (2 Gigs or more) you should be fine.
I think you should use merge replication for this. You can't use
transactional as MSDE can't be a transactional publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ken Ptaszynski" <Ken Ptaszynski@.discussions.microsoft.com> wrote in message
news:FA9B3270-7928-4C1C-9446-3FB489B2015A@.microsoft.com...
> We are developing a system for a manufacturing operation. The planned
> approach is to develop stand alone data capture applications using MSDE
for
> the database. The production data from these systems needs to be posted to
a
> central SQL database. All systems will be in the same building. We plan
to
> roll out this system to a number of facilities. The number of data
capture
> systems could range from 5 to 25. Data Transfer requirements include: 1)
> Master data from the central system will need to be sent to the data
capture
> machines (updated 4 times a day). 2) Production order informtation will
be
> sent to 1 or more data capture machines (updated as orders are scheduled
to
> production lines). 3) Production data from the data capture machines
will
> need to be sent in a timely manner because 4) Summary Production data
(totals
> by production order and material) is needed by the data capture machines
to
> prevent overruns.
> The current application we have uses a separate VB application to update
the
> stand alone and central database. Users are given a message when the
central
> database cannot be accesssed, however, the stand alone machines must
continue
> working.
> Would replication be a good design for this scenario? or is it overkill?
I
> have heard the replication is a resource hog, we will have only the
central
> server to work with.
> Other information:
> Production data on the stand alones need only be kept for a few days,
after
> that it can be purged.
> Production records (single table) can be created every 6 seconds, updates
to
> central database can be queued.
> Master data consist of 6 tables that are used for look up purposes by the
> application running on the stand alone systems.
> There are 2 production tables (Header and detail). Application displays
> summary production (for detail record) by current system and across all
> systems.
> Thanks in advance for you help

Is possible to design a localizable report?

We are developing an application that must work in two different languages,
and we have the following doubt:
Is it possible to design a localizable report ?, that is, that the report
appears in different languages depending on a parameter or the browser
configuration?
We are interested in develop only one version of every report, and that the
report server send to the user the report localized depending on a parameter
or the web browser configuration.
Is there something like the resource files for Windows forms?.
Thanks in advance for your help.Hi
I have found a workaround for this. Use the report parameters in your code
and set their default values in the code itself from the resource files and
then render the report. Since the default parameters will be based on the
culture settings the report would be rendered based on the culture.So all the
fields in the report that would vary with culture would be parameters
accepting the values form the resource file in the code.
Hope that helps.
Kalpna
"Eurofirms." wrote:
> We are developing an application that must work in two different languages,
> and we have the following doubt:
> Is it possible to design a localizable report ?, that is, that the report
> appears in different languages depending on a parameter or the browser
> configuration?
> We are interested in develop only one version of every report, and that the
> report server send to the user the report localized depending on a parameter
> or the web browser configuration.
> Is there something like the resource files for Windows forms?.
> Thanks in advance for your help.
>

Is MSDE what I need?

We are developing a fairly simple database to be deployed on the
internet. It consists of an artist's works (approx 2600 of them) based
on references to books from which his ideas came. Relative fields will
be fairly few, data related to the books, a pic of his initial sketch,
and a pic of the final painting. Searches will be provided and probably
a feedback form. The plan is for this database to be used by students
when studying myths of the world (and other interested parties, of course).
i am in the beginning stages using Access 2002 and Jet. We just
purchased and installed Visual Studio .net (academic version), but i
haven't actually used it yet. The install mentions MSDE. However, even
after reading about MSDE on MS's site, i still can't determine my course.
For our web application, what should i use? MSDE or Jet? ADO or is DAO
(i am familiar with DAO but not ADO)?
i need a plan, a course of action to follow for this, as it is new
ground for me. i'm not asking for details, just general direction. i'm
basically self-taught and there is no one here who knows any more about
this.
Any guidance is appreciated.
--e
If you're creating an internet application using ASP.NET, the home
page would be a good place to start doing research --
http://www.asp.net/Default.aspx. Jet isn't generally recommended for
Internet applications, although it is being used for small
applications with few concurrent users.You'll be using ADO.NET for
data access, not DAO or ADO. You'll need to do some research to
determine the best fit for your budget and needs. You can get more
information on using MSDE for a web application at
http://msdn.microsoft.com/library/?u...2000webapp.asp
and http://www.microsoft.com/sql/howtobuy/default.asp.
--mary
On Wed, 05 May 2004 11:04:24 -0700, elizabeth baker
<baker_eliz@.yahoo.com> wrote:

>We are developing a fairly simple database to be deployed on the
>internet. It consists of an artist's works (approx 2600 of them) based
>on references to books from which his ideas came. Relative fields will
>be fairly few, data related to the books, a pic of his initial sketch,
>and a pic of the final painting. Searches will be provided and probably
>a feedback form. The plan is for this database to be used by students
>when studying myths of the world (and other interested parties, of course).
>i am in the beginning stages using Access 2002 and Jet. We just
>purchased and installed Visual Studio .net (academic version), but i
>haven't actually used it yet. The install mentions MSDE. However, even
>after reading about MSDE on MS's site, i still can't determine my course.
>For our web application, what should i use? MSDE or Jet? ADO or is DAO
>(i am familiar with DAO but not ADO)?
>i need a plan, a course of action to follow for this, as it is new
>ground for me. i'm not asking for details, just general direction. i'm
>basically self-taught and there is no one here who knows any more about
>this.
>Any guidance is appreciated.
>--e