MSDE Subscriber names

I plan to set up merge replication and have laptops with an MSDE
subscription for replication. I want my application to use the database
name and wondered if I can (and should?) have the same database name on both
the laptop and the main publication. Thanks.
David
It helps to identify the subscriber database, but there is no real
requirement. All the subscribers should have the same database name if you
are publishing to multiple subscribers at once.
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
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23KWrAVCpFHA.320@.TK2MSFTNGP09.phx.gbl...
> I plan to set up merge replication and have laptops with an MSDE
> subscription for replication. I want my application to use the database
> name and wondered if I can (and should?) have the same database name on
both
> the laptop and the main publication. Thanks.
> David
>

MSDE Service permissions

Hi All,
I'm installing MSDE 2000 with a custom application (launched using
setup.exe, not integrating merge modules) and am having a problem with the
service permissions for SQL services. The custom app installer is being
build with Installshield Pro 6.3.
Everything works fine for admin users, but MSDE won't start for non-admin
users. The MSSQL$Instance service won't start unless it's logging on a Local
System.
I need non-admin users to have access to the database.
Is there any way to setup MSDE on install to work for everyone?
What does one need to do to manually configure it after install to work for
everyone?
Thanks,
leon.
hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> I'm installing MSDE 2000 with a custom application (launched using
> setup.exe, not integrating merge modules) and am having a problem with the
> service permissions for SQL services. The custom app installer is being
> build with Installshield Pro 6.3.
> Everything works fine for admin users, but MSDE won't start for non-admin
> users. The MSSQL$Instance service won't start unless it's logging on a
Local
> System.
> I need non-admin users to have access to the database.
> Is there any way to setup MSDE on install to work for everyone?
> What does one need to do to manually configure it after install to work
for
> everyone?
usually MSDE is installed setting the relative services account to
LocalSystem, that provide (far) enought privileges (on the local machine)
for all logged users...
have a look at
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
for more restrictions..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
By default the services use Local System option for log on. This worked fine
for all admin users but did not work for a non-admin user. When a non-admin
user logs in (local or domain user), the services won't start using Local
System. (side note: this is on a WinXP Pro machine). The non-admin user
cannot start or stop any service.
We did get it to work for the non-admin user by using the local
administrator account for log on (I goofed when trying it the first time by
using domain admin password instead of local admin password). This is not
the way we want to go, but it's the only way it does work right now.
I did find one thing via your link, in the Installation Recommendations:
"Create a least privileged local account with which to run the SQL Server
service. Use this account when you are prompted for service settings during
setup. Do not use the local system account or an administrator account. "
There is no prompt when installing MSDE. What exactly is a "least priviledge
local account"?
Any other suggestions are most welcome!
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2okhj5Fbml6lU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
the[vbcol=seagreen]
non-admin
> Local
> for
> usually MSDE is installed setting the relative services account to
> LocalSystem, that provide (far) enought privileges (on the local machine)
> for all logged users...
> have a look at
>
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
> for more restrictions..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi Andrea,
> By default the services use Local System option for log on. This worked
fine
> for all admin users but did not work for a non-admin user. When a
non-admin
> user logs in (local or domain user), the services won't start using Local
> System. (side note: this is on a WinXP Pro machine). The non-admin user
> cannot start or stop any service.
actually they shoul'd run, as all this is intended to work this way... SQL
Server is run under another privileged account than the current logged
account, which only needs to connect to the specified server and query for
information..
perhaps you have to check your local policies...

> We did get it to work for the non-admin user by using the local
> administrator account for log on (I goofed when trying it the first time
by
> using domain admin password instead of local admin password). This is not
> the way we want to go, but it's the only way it does work right now.
I usually use a local account (not LocalSystem), with enought rights on
relevent share(s) if needed..

> I did find one thing via your link, in the Installation Recommendations:
> "Create a least privileged local account with which to run the SQL Server
> service. Use this account when you are prompted for service settings
during
> setup. Do not use the local system account or an administrator account. "
> There is no prompt when installing MSDE. What exactly is a "least
priviledge
> local account"?
no, there's not... that info is for a full blown SQL Server installation..
you have to set that property after MSDE installed, accessing the services
management applet... perhaps it can be done via WMI, but never tried it..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||more,
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:2omoccFcfn07U1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
Local[vbcol=seagreen]
they do not have to... set the service's "start at boostrap" property...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The instructions on the SQLServer Installation Recommendations say to create
a new user, remove it from the users group and use it for the service login.
We created an "msde" user, removed it from Users group, set it as the Log On
As account (it is listed in the "Log on as a service" policy), gave full
access rights for the data files to Everyone, and it doesn't work.
So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
starting with a non-admin log in?
If so, you must have some magic touch because we're trying this on 2
separate machines with the same failure on each. We'll be trying it on a
fresh XP install shortly, but I don't really expect different results.
Even when logged into the XP as an administrator, setting the MSDE service
login account to "msde" causes the service to fail on a start attempt. It
gives the following error:
Could not start the MSDE$... service on Local Computer.
Error 5: Access is Denied
How do you access the "start at boostrap" property of a service?
thanks,
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2omogoFcbbrgU1@.uni-berlin.de...[vbcol=seagreen]
> more,
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
> news:2omoccFcfn07U1@.uni-berlin.de...
> Local
user
> they do not have to... set the service's "start at boostrap" property...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> The instructions on the SQLServer Installation Recommendations say to
create
> a new user, remove it from the users group and use it for the service
login.
> We created an "msde" user, removed it from Users group, set it as the Log
On
> As account (it is listed in the "Log on as a service" policy), gave full
> access rights for the data files to Everyone, and it doesn't work.
> So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
> starting with a non-admin log in?
> If so, you must have some magic touch because we're trying this on 2
> separate machines with the same failure on each. We'll be trying it on a
> fresh XP install shortly, but I don't really expect different results.
> Even when logged into the XP as an administrator, setting the MSDE service
> login account to "msde" causes the service to fail on a start attempt. It
> gives the following error:
> Could not start the MSDE$... service on Local Computer.
> Error 5: Access is Denied
I do always use a local admin account, and I never use the special
LocalSystem account, created just for this purpose and never use an actual
local or domain administrator account. The account must be in the local
Administrators group if you're installing SQL Server on Windows NT or
Windows 2000. You can create this account before you begin installing SQL
Server, or you can change the account under which SQL Server runs at a later
time.
Setting less privileges is intended in not using a Domain Admin account for
network protection.
> How do you access the "start at boostrap" property of a service?
in the service management, select Startup Mode = automatic
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
Sorry, referring to the automatic service startup as "start at bootstrap"
property is a little different terminology than I am used to. I do
understand the automatic startup option.
We will just include some instructions for setting up the app for non-admin
users.
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2ong8qFcg0ccU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> create
> login.
Log[vbcol=seagreen]
> On
(MSDE$InstanceName)[vbcol=seagreen]
service[vbcol=seagreen]
It
> I do always use a local admin account, and I never use the special
> LocalSystem account, created just for this purpose and never use an actual
> local or domain administrator account. The account must be in the local
> Administrators group if you're installing SQL Server on Windows NT or
> Windows 2000. You can create this account before you begin installing SQL
> Server, or you can change the account under which SQL Server runs at a
later
> time.
> Setting less privileges is intended in not using a Domain Admin account
for
> network protection.
> in the service management, select Startup Mode = automatic
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

MSDE Replication issue

I am trying merge replication between two instances of MSDE on two
different machines on LAN.
I have setup the snapshot agent . when I try running the agent using
sp_start_job @.job_name='MergeSnapshot'
I get an error message saying job name ('MergeSnapshot') does not exist
I am new to replication and trying this for the first time...
Any help is appreciated.
Hello,
Please check out this article:
http://support.microsoft.com/default...b;en-us;324992
regards,
Henk Steunenberg
<prabhusangeeta@.yahoo.com> wrote in message
news:1133288220.042242.206490@.g44g2000cwa.googlegr oups.com...
>I am trying merge replication between two instances of MSDE on two
> different machines on LAN.
> I have setup the snapshot agent . when I try running the agent using
> sp_start_job @.job_name='MergeSnapshot'
> I get an error message saying job name ('MergeSnapshot') does not exist
> I am new to replication and trying this for the first time...
> Any help is appreciated.
>

MSDE Replication in Workgroup Enviromnet

We currently have two machines in a workgroup environment and both are
running WIndows XP Pro SP1 and MSDE Sp3.
The problem we have is with the Merge Replication. The publisher writes
snapshot data to the snapshot folder, but the subscriber is unable to open
this file across the network. We get error 5 access denied.
From the subscriber PC through explorer/notepad we can open the file. The
file name is MSmerge_genhistory.bcp
If we were to put the pc into a domain we have no problem. Replication wor
Replication is probably accessing this file through a admin share
something like \\servername\d$\xxxxx\repldata\ which needs admin access to
the distributor machine.
Try configuring a named share like \\servername\repldata and allow access to
relevant user and set that to be the working directory. You can set the
working directory when configuring publisher
or through sp_adddistpublisher or sp_changedistpublisher.
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"Colin M" <ColinM@.discussions.microsoft.com> wrote in message
news:027D0BE9-2D57-4DF4-888C-173A7FCD3404@.microsoft.com...
> We currently have two machines in a workgroup environment and both are
> running WIndows XP Pro SP1 and MSDE Sp3.
> The problem we have is with the Merge Replication. The publisher writes
> snapshot data to the snapshot folder, but the subscriber is unable to open
> this file across the network. We get error 5 access denied.
> From the subscriber PC through explorer/notepad we can open the file. The
> file name is MSmerge_genhistory.bcp
>
> If we were to put the pc into a domain we have no problem. Replication wor

MSDE package doesn't work on win 98

I created a install shield package on windows 98 using the
MSDE merge modules with vb .net. It works fine on 2000 and
xp but on windows 98 it give an ambiguous error: "Error
1723. Theres a problem with this windows installer
package. A DLL required for this installation to complete
could not be run."
This happenes as soon as I click on the msi file. Or if I
click the setup file then after a couple checks and when
setup tryes running the msi file.
Anyone have any ideas what it could be? Which dlls? Which
merge modules could be missing?
Any help would greatly appreciated. I've lost some hair
over this one.
You probably don't have any version of MDAC installed on the Win98 system.
Make MDAC a dependency of your install and install it first if needed before
going forward.
J
"MSDE" <Sebastian@.ilogic.com> wrote in message
news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
> I created a install shield package on windows 98 using the
> MSDE merge modules with vb .net. It works fine on 2000 and
> xp but on windows 98 it give an ambiguous error: "Error
> 1723. Theres a problem with this windows installer
> package. A DLL required for this installation to complete
> could not be run."
> This happenes as soon as I click on the msi file. Or if I
> click the setup file then after a couple checks and when
> setup tryes running the msi file.
> Anyone have any ideas what it could be? Which dlls? Which
> merge modules could be missing?
> Any help would greatly appreciated. I've lost some hair
> over this one.
|||The other problems we've found with Win98 are if file sharing isn't enabled
or if the Windows Family Logon is enabled.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:O3HnrMrnEHA.132@.TK2MSFTNGP09.phx.gbl...
> You probably don't have any version of MDAC installed on the Win98 system.
> Make MDAC a dependency of your install and install it first if needed
before
> going forward.
> J
> "MSDE" <Sebastian@.ilogic.com> wrote in message
> news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
>

MSDE Merge Replication (feasibility and licensing)

I am new to replication and have a couple of questions.
My requirement is to keep several (2 - 10) databases in sync. My current thinking is to use MSDE, along with merge replication. I have determined from the documentation that MSDE has the features and capabilities to fulfil the data storage and retrieval
requirments.
1) Is merge replication possible among a number of MSDE databases across a network (no SQL Server involved)
2) Do any licenses have to be purchased? The documentation is a little inconsistent on this point.
Thanks a lot.
1) yes, but MSDE is optimized for 8 concurrent workloads
2) check out this link for MSDE licensing information
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
"JW" <anonymous@.discussions.microsoft.com> wrote in message
news:F861246B-EBDA-4EEA-8CA0-6077C3F5DBCD@.microsoft.com...
> I am new to replication and have a couple of questions.
> My requirement is to keep several (2 - 10) databases in sync. My current
thinking is to use MSDE, along with merge replication. I have determined
from the documentation that MSDE has the features and capabilities to fulfil
the data storage and retrieval requirments.
> 1) Is merge replication possible among a number of MSDE databases across a
network (no SQL Server involved)
> 2) Do any licenses have to be purchased? The documentation is a little
inconsistent on this point.
> Thanks a lot.
|||I must admit that I've never tested this, but as far as I
recall MSDE is throttled at 5 connections.
Regards,
Paul Ibison
|||Thanks for the replies.
1) I think that it's the number of concurrent batches that chokes MSDE, not the number of connections.
From "The SQL Server 2000 Workload Governor" at http://msdn.microsoft.com/library/?u...asp?frame=true :
"Like all versions of SQL Server 2000, SQL Server 2000 Personal Edition and MSDE 2000 allow 32,767 connections to an instance of the database engine. There is no limit for the number of connections that can be executing operations at the same time. The on
ly effect of the workload governor is that it starts slowing down the database engine when more than eight operations are actively running at the same time."
2) Based on my research, it looks like no extra licensing is required if there is no connection to any of the 'regular' SQL Server editions:
From "HOW TO: Use Replication with SQL Server 2000 Desktop Engine (MSDE 2000)" at http://support.microsoft.com/4
"Licensing Issues
MSDE 2000 does not require any licensing when you use it in a stand-alone mode, but when you use it as part of a replication topology that involves regular SQL Server editions, if the server is in Per Seat mode as opposed to a Per Processor mode, each MSD
E 2000 Subscriber must have a client-access license (CAL).
For more information about SQL Server licensing, visit the following Microsoft Web site:
http://www.microsoft.com/sql/howtobuy/SQL2KLic.doc"
Again, thanks for your time.
Regards,
Joe
|||JW,
interesting. In the MS knowledgebase it mentions throttling after 5
concurrent connections:
MSDE 2000-Specific Limitations and Caveats
a.. MSDE 2000 limits the size of the database to 2 GB...
b.. The number of connections to MSDE 2000 is optimized for five
connections. This may affect the performance of replication if MSDE 2000 is
the Publisher and there are a enough Subscribers to the publication or if it
is a Subscriber to multiple publications.
see: http://support.microsoft.com/default...;en-us;Q324992
I have seen this 'limit' mentioned elsewhere, so the mentioning of 8 is
strange. I'll do some more research and see if we can get a definitive
answer.
Regards,
Paul Ibison

MSDE merge modules

Hi
I wonder if anyone can help. I am looking for the MSDE merge modules to use
in a .net 2003 set up and deployment module. see
http://support.microsoft.com/kb/325004/EN-US/
However I have already installed SQL server standard edition on my
development server. How do I get these MSM's to merge into my MSI? Am I
barking up the wrong tree?
Thanking you in advance for any help
Richard
Hello,
Personally, I use the last setup of msde (sql2000.msi and I launch it
from my setup with a custom action.)
With that, I don't need to use the merge modules and if a custommer want
to use SQL Server instead, I don't need to change my setup (I don't need
to install MSDE and just connect to sql server and it will work.)
I can give all the parameters to msiexec (or to the property table of
the msi).
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I wonder if anyone can help. I am looking for the MSDE merge modules to use
> in a .net 2003 set up and deployment module. see
> http://support.microsoft.com/kb/325004/EN-US/
> However I have already installed SQL server standard edition on my
> development server. How do I get these MSM's to merge into my MSI? Am I
> barking up the wrong tree?
> Thanking you in advance for any help
> Richard
>
|||Hi
I am interested in how you do this. You suggest that you can supply the
paramters to msiexec or the property table of MSI? Please can you point me
in the right direction.
After the instance has been created how do you then create the database and
insert any data?
Thank you for your help so far.
Richard
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...[vbcol=seagreen]
> Hello,
> Personally, I use the last setup of msde (sql2000.msi and I launch it from
> my setup with a custom action.)
> With that, I don't need to use the merge modules and if a custommer want
> to use SQL Server instead, I don't need to change my setup (I don't need
> to install MSDE and just connect to sql server and it will work.)
> I can give all the parameters to msiexec (or to the property table of the
> msi).
> Marc Allard
> Allcomp
> Richard Wilde wrote:
|||Hello,
Here is how I do that ...
1) Create a
property MSIExecPos
Value : msiexec
in the table property of the msi file (or the merge module)
2) Create a custom action
InstallMsde
Type : 114 (to ignore the return code because in Win98 sometimes the
return code is not 0 so you have problems).
source : MsiExecPos
Target
/i "MSDE\Sql2000.msi" /qb /l c:\msde.log
Personally, I put the full MSDE installation directory into a sub
directory MSDE so the root of my CD is cleaner
3) In the InstallUISequence (you have tu use InstallUISequence or the
installation won't work)
You add the action
InstallMsde
You can put a install condition or not
For the sequence, you put something in the end (1305 in my case).
After that, you can change the parameters of the MSDE file
In the property table, you put
REBOOT Value : ReallySuppress
to avoid a reboot prompt after the installation of MSDE
INSTANCENAME value : NameofYourInstance
I believe that it is necessary because if a custommer has already MSDE
installed, then you will run into very big problems to install your software
DISABLENETWORKPROTOCOLSValue : 0
If you don't do it, your server will only work locally.
SqlSaPwdValue : YourPassword
I think it is better to pass it directly in the custom action instead of
the property table.
Normally with that, all should be fine
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I am interested in how you do this. You suggest that you can supply the
> paramters to msiexec or the property table of MSI? Please can you point me
> in the right direction.
> After the instance has been created how do you then create the database and
> insert any data?
> Thank you for your help so far.
> Richard
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...
>
>

MSDE General Questions

I am trying to better understand my replication options with MSDE.
I am pretty sure that with merge replication the remote MSDE database will
track the changes in a set of state tables. However with transactional
replication I have read conflicting information as to whether it tracks
changes in the MSDE transaction log or in state tables. Does anyone know the
answer to this?
Also since MSDE has a limit to the size of the database does anyone know how
much additional data is stored in these state tables whenever a change is
made?
Thanks
Answers in line
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
"Cavanagh" <Cavanagh@.discussions.microsoft.com> wrote in message
news:DBE421DC-3E4B-4BC6-9275-0DB77F7133E0@.microsoft.com...
> I am trying to better understand my replication options with MSDE.
> I am pretty sure that with merge replication the remote MSDE database will
> track the changes in a set of state tables. However with transactional
> replication I have read conflicting information as to whether it tracks
> changes in the MSDE transaction log or in state tables.
In merge replication is uses the same state tabels for all versions of SQL
Server including MSDE. For transactional replication MSDE can only subscribe
to transactional replication publications.
Does anyone know the
> answer to this?
> Also since MSDE has a limit to the size of the database does anyone know
how
> much additional data is stored in these state tables whenever a change is
> made?
For an insert or update roughly 2329 bytes. For a delete about 748.

> Thanks
|||> For transactional replication MSDE can only subscribe
> to transactional replication publications.
So for transactional replication (MSDE), does it track changes in state
tables or in the transaction log?
Thanks for the other answers.
|||I don't like this question, because if I was to say yes, which strictly
speaking is true, you would probably get a incorrect idea of how it works.
The state of the subscription is tracked in a table in MSDE called
MSreplication_subscriptions. This table contains information about what
transaction was last applied on the subscription database. It contains no
information about changes which were made to the subscriber tables per se.
So if a user makes a change to a subscriber table, it won't appear in
MSreplication_subscriptions. If a replication process makes a change some
metadata will be logged in MSreplication_subscriptions.
Changes themselves are logged in two "state tables" in the distribution
database on the publisher. Prior to being logged in the distribution
database, they are logged in the transaction log in the publication
database.
No changes are logged in the subscription database on the MSDE database,
unless you are using queued updating.
The way to think about it is, with plain vanilla transactional replication,
any user activity originating on the subscriber (MSDE), in the subscription
database will not be logged in state tables, but replication activity
originating on the publisher will update the subscriber tables, and write
replication metadata to the "state" table MSreplication_subscription.
HTH
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
"Cavanagh" <Cavanagh@.discussions.microsoft.com> wrote in message
news:181BE87C-FAEC-467E-861C-0E19DED023F8@.microsoft.com...
> So for transactional replication (MSDE), does it track changes in state
> tables or in the transaction log?
> Thanks for the other answers.
|||Thanks!
"Hilary Cotter" wrote:

> I don't like this question, because if I was to say yes, which strictly
> speaking is true, you would probably get a incorrect idea of how it works.
> The state of the subscription is tracked in a table in MSDE called
> MSreplication_subscriptions. This table contains information about what
> transaction was last applied on the subscription database. It contains no
> information about changes which were made to the subscriber tables per se.
> So if a user makes a change to a subscriber table, it won't appear in
> MSreplication_subscriptions. If a replication process makes a change some
> metadata will be logged in MSreplication_subscriptions.
> Changes themselves are logged in two "state tables" in the distribution
> database on the publisher. Prior to being logged in the distribution
> database, they are logged in the transaction log in the publication
> database.
> No changes are logged in the subscription database on the MSDE database,
> unless you are using queued updating.
> The way to think about it is, with plain vanilla transactional replication,
> any user activity originating on the subscriber (MSDE), in the subscription
> database will not be logged in state tables, but replication activity
> originating on the publisher will update the subscriber tables, and write
> replication metadata to the "state" table MSreplication_subscription.
> HTH
> --
> 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
> "Cavanagh" <Cavanagh@.discussions.microsoft.com> wrote in message
> news:181BE87C-FAEC-467E-861C-0E19DED023F8@.microsoft.com...
>
>

MSDE for replication on both ends?

We are designing an application that will use merge replication from a
wireless laptop back to a server. Plan on using MSDE on the laptops, can the
central P.C. that will be on the other end use the MSDE also, or does one of
them need to be full blown SQL Server?
Thanks,
Steve
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:CF01E337-7EC0-4879-816C-D572F86A8131@.microsoft.com...
> We are designing an application that will use merge replication from a
> wireless laptop back to a server. Plan on using MSDE on the laptops, can
the
> central P.C. that will be on the other end use the MSDE also, or does one
of
> them need to be full blown SQL Server?
> Thanks,
> Steve
|||It can be used as a publisher or subscriber with merge replication - so it
should work for you.
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:CF01E337-7EC0-4879-816C-D572F86A8131@.microsoft.com...
> We are designing an application that will use merge replication from a
> wireless laptop back to a server. Plan on using MSDE on the laptops, can
the
> central P.C. that will be on the other end use the MSDE also, or does one
of
> them need to be full blown SQL Server?
> Thanks,
> Steve
|||Thanks for your information again Hilary.
We have some current applications with MSDE doing Merge replication back to
our servers running MS SQL. So we do have experience setting up and
maintaining it. We just had not set one up with the MSDE on both ends. You
lose having Enterprise Manager in the mix I guess, but we should be able to
plug the laptops into our network here and use Enterprise Manager from my
workstation to set up the publications and subscriptions on the laptops.
Thanks,
Steve
"Hilary Cotter" wrote:

> It can be used as a publisher or subscriber with merge replication - so it
> should work for you.
> --
> 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
> "SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
> news:CF01E337-7EC0-4879-816C-D572F86A8131@.microsoft.com...
> the
> of
>
>