I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql
Showing posts with label multiple. Show all posts
Showing posts with label multiple. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSDE 2K Merge replication without network
I'm new to replication, but have a challenging requirement...
I have multiple MSDE 2K instances that will be used by a surveying crew that
may be distributed across many miles - sometimes in jungle or desert
environments where they never even see each other.
All/any data in any instance is updateable; all changes must be propagated -
at irregular intervals (daily or?) to all other instances. There is no
designated "master" (or perhaps all instances could be considered "masters").
We can live with a hub-and-spoke replication topology (ie, all replication
occurs via a hub instance at the field camp, which then, eventually,
replicates to all the other spokes).
===> The instances are NOT (and are NEVER) connected over a network! (not
even wireless - although we should be able to at least keep the system clocks
synchronized, if that's required for reliable synchronization, by having
each system have a GPS receiver).
Therefore, all synchronization must be via files (flash drive, etc). Even
the definition/setup of the synchronization (subscriptions) must not require
a network connection.
Can Merge replication be implemented between MSDE instances, given these
network constraints?
Thanks!
David
Unless you provide at least an occasional network connectivity between
publisher and subscribers merge replication cannot be implemented.
Yury
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
> that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
> propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
> "masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
> clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
> require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
|||its probably better to use transactional replication with a local dummy
subscriber. Collect the contents of msrepl_commands and then mail them back
and forth. This will be a list of all database activity which you can run on
each node for synchronization purposes.
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" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
"masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
I have multiple MSDE 2K instances that will be used by a surveying crew that
may be distributed across many miles - sometimes in jungle or desert
environments where they never even see each other.
All/any data in any instance is updateable; all changes must be propagated -
at irregular intervals (daily or?) to all other instances. There is no
designated "master" (or perhaps all instances could be considered "masters").
We can live with a hub-and-spoke replication topology (ie, all replication
occurs via a hub instance at the field camp, which then, eventually,
replicates to all the other spokes).
===> The instances are NOT (and are NEVER) connected over a network! (not
even wireless - although we should be able to at least keep the system clocks
synchronized, if that's required for reliable synchronization, by having
each system have a GPS receiver).
Therefore, all synchronization must be via files (flash drive, etc). Even
the definition/setup of the synchronization (subscriptions) must not require
a network connection.
Can Merge replication be implemented between MSDE instances, given these
network constraints?
Thanks!
David
Unless you provide at least an occasional network connectivity between
publisher and subscribers merge replication cannot be implemented.
Yury
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
> that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
> propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
> "masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
> clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
> require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
|||its probably better to use transactional replication with a local dummy
subscriber. Collect the contents of msrepl_commands and then mail them back
and forth. This will be a list of all database activity which you can run on
each node for synchronization purposes.
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" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
"masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
Wednesday, March 21, 2012
MSDE 2000 and Multiple Applications
I built a server that will have three applications that require MSDE 2000. We
do not have a SQL server. The apps are SharePoint Services, NAI's ePO and
Veritas' Backup Exec. Can all three applications use one copy of MSDE? This
is a small shop, so there won't be incredible load on the server. Obviously,
I'm not a DBA :-)
Thanks for your help!
I've answered my own question after I discovered in this group that I was
using the wrong terminology.
Thanks all!
"Gene" wrote:
> I built a server that will have three applications that require MSDE 2000. We
> do not have a SQL server. The apps are SharePoint Services, NAI's ePO and
> Veritas' Backup Exec. Can all three applications use one copy of MSDE? This
> is a small shop, so there won't be incredible load on the server. Obviously,
> I'm not a DBA :-)
> Thanks for your help!
do not have a SQL server. The apps are SharePoint Services, NAI's ePO and
Veritas' Backup Exec. Can all three applications use one copy of MSDE? This
is a small shop, so there won't be incredible load on the server. Obviously,
I'm not a DBA :-)
Thanks for your help!
I've answered my own question after I discovered in this group that I was
using the wrong terminology.
Thanks all!
"Gene" wrote:
> I built a server that will have three applications that require MSDE 2000. We
> do not have a SQL server. The apps are SharePoint Services, NAI's ePO and
> Veritas' Backup Exec. Can all three applications use one copy of MSDE? This
> is a small shop, so there won't be incredible load on the server. Obviously,
> I'm not a DBA :-)
> Thanks for your help!
Monday, March 12, 2012
MSDE - Multiple versions coexist?
While setting up for HP Insight Manager...
Microsoft provided documentation is leading me to believe that MSDE 2000 SP3
and previous versions of MSDE could coexist on one box.
Is that true?
I installed MSDE 2000 SP3 on one of my servers which had a previous MSDE
version with existing active databases. The result was that though databases
were still running, I had difficulty seeing the certain databases through
Enterprise Manager.
hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:O7wPFHaoEHA.2032@.TK2MSFTNGP10.phx.gbl
> While setting up for HP Insight Manager...
> Microsoft provided documentation is leading me to believe that MSDE
> 2000 SP3 and previous versions of MSDE could coexist on one box.
> Is that true?
> I installed MSDE 2000 SP3 on one of my servers which had a previous
> MSDE version with existing active databases. The result was that
> though databases were still running, I had difficulty seeing the
> certain databases through Enterprise Manager.
yese , up to 16 instances of SQL Server 2000 and MSDE 2000 at different
service pack level can coexist on the same box.
1 instance will be the default instance, locally available as "(local)" or
generally available as "ComputerName", while all other instances will be
named instances, reachable with teir complete name, made up by the computer
name and instance name, in the form "ComputerName\InstanceName"
what kind of problem are you facing?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have a server running MSDE and two existing databases or instances. I am
uncertain of the version or how to determine the version.
I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
installed MSDE 2000, SP3 and created the new instance for Insight Manager.
The application worked and the existing databases/instances were accessible
and continued to work.
A few days later, an Programmer/Administrator was trying to
monitor/manipulate one of the previously existing databases via Enterprise
Manager and noticed he could not see it the applications utilizing the
databases worked fine.
I uninstalled the MSDE 2003. The Programmer/Administrator then was able to
monitor/manipulate the previously existing databases via Enterprise Manager.
I'm not certain my explanation is clear. Any help you can provide is
appreciated.
DWM
[vbcol=seagreen]
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rgrn3F1ad8ggU1@.uni-berlin.de...
> hi,
> what kind of problem are you facing?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
|||hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:%23$d0IXkoEHA.3464@.tk2msftngp13.phx.gbl
> I have a server running MSDE and two existing databases or instances.
> I am uncertain of the version or how to determine the version.
> I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
> installed MSDE 2000, SP3 and created the new instance for Insight
> Manager. The application worked and the existing databases/instances
> were accessible and continued to work.
> A few days later, an Programmer/Administrator was trying to
> monitor/manipulate one of the previously existing databases via
> Enterprise Manager and noticed he could not see it the applications
> utilizing the databases worked fine.
> I uninstalled the MSDE 2003. The Programmer/Administrator then was
> able to monitor/manipulate the previously existing databases via
> Enterprise Manager.
> I'm not certain my explanation is clear. Any help you can provide is
> appreciated.
actually there's no reason for that... all instances can be running
(resources allowing it) with no consequences...
each instace will have it's onw TCP address , provided by the service
listening on UDP 1434 port..
check the services (SQL Server services) are running and address each
instance with it's correct name (full name for named instance)
I do not know HP Insight manager, so I'm not able to provide fupport for
that tool/application
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Microsoft provided documentation is leading me to believe that MSDE 2000 SP3
and previous versions of MSDE could coexist on one box.
Is that true?
I installed MSDE 2000 SP3 on one of my servers which had a previous MSDE
version with existing active databases. The result was that though databases
were still running, I had difficulty seeing the certain databases through
Enterprise Manager.
hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:O7wPFHaoEHA.2032@.TK2MSFTNGP10.phx.gbl
> While setting up for HP Insight Manager...
> Microsoft provided documentation is leading me to believe that MSDE
> 2000 SP3 and previous versions of MSDE could coexist on one box.
> Is that true?
> I installed MSDE 2000 SP3 on one of my servers which had a previous
> MSDE version with existing active databases. The result was that
> though databases were still running, I had difficulty seeing the
> certain databases through Enterprise Manager.
yese , up to 16 instances of SQL Server 2000 and MSDE 2000 at different
service pack level can coexist on the same box.
1 instance will be the default instance, locally available as "(local)" or
generally available as "ComputerName", while all other instances will be
named instances, reachable with teir complete name, made up by the computer
name and instance name, in the form "ComputerName\InstanceName"
what kind of problem are you facing?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have a server running MSDE and two existing databases or instances. I am
uncertain of the version or how to determine the version.
I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
installed MSDE 2000, SP3 and created the new instance for Insight Manager.
The application worked and the existing databases/instances were accessible
and continued to work.
A few days later, an Programmer/Administrator was trying to
monitor/manipulate one of the previously existing databases via Enterprise
Manager and noticed he could not see it the applications utilizing the
databases worked fine.
I uninstalled the MSDE 2003. The Programmer/Administrator then was able to
monitor/manipulate the previously existing databases via Enterprise Manager.
I'm not certain my explanation is clear. Any help you can provide is
appreciated.
DWM
[vbcol=seagreen]
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rgrn3F1ad8ggU1@.uni-berlin.de...
> hi,
> what kind of problem are you facing?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
|||hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:%23$d0IXkoEHA.3464@.tk2msftngp13.phx.gbl
> I have a server running MSDE and two existing databases or instances.
> I am uncertain of the version or how to determine the version.
> I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
> installed MSDE 2000, SP3 and created the new instance for Insight
> Manager. The application worked and the existing databases/instances
> were accessible and continued to work.
> A few days later, an Programmer/Administrator was trying to
> monitor/manipulate one of the previously existing databases via
> Enterprise Manager and noticed he could not see it the applications
> utilizing the databases worked fine.
> I uninstalled the MSDE 2003. The Programmer/Administrator then was
> able to monitor/manipulate the previously existing databases via
> Enterprise Manager.
> I'm not certain my explanation is clear. Any help you can provide is
> appreciated.
actually there's no reason for that... all instances can be running
(resources allowing it) with no consequences...
each instace will have it's onw TCP address , provided by the service
listening on UDP 1434 port..
check the services (SQL Server services) are running and address each
instance with it's correct name (full name for named instance)
I do not know HP Insight manager, so I'm not able to provide fupport for
that tool/application
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Subscribe to:
Posts (Atom)