Hi
I have a Windows Form running in 40 clients around the city, those apps are
communicating with a central SQLDB hosted in a hosting company (each one is
sending data, waiting for data comparisons and receiving the data back). I
have been using a Web Service to make the link between my apps and the SQLDB
,
but now I want to connect my Windows Form apps directly to de SQLServer
(because I think the roundtrip is going to be faster, which is the most
important factor in my app)
My question to the architects and everyone:
Is this a good, secure, recommended, intelligent practice or this is a big
big mistake '
thks
kengood - Prototype it and see. Depends on the specific case usage and
implementation. You may find that the old style tightly coupled connection
is faster.
secure - Unencrypted xml is easier to intercept and read than unencrypted
native sql network calls. Using an encrypted protocol, it makes little
difference between the two.
recommended, intelligent practice or this is a big big mistake - Consider
the above and decide based on your requirement priorities.
"Kenny M." <KennyM@.discussions.microsoft.com> wrote in message
news:72C3EF9C-7DF4-4C85-A43B-8CE0C5E63388@.microsoft.com...
> Hi
> I have a Windows Form running in 40 clients around the city, those apps
are
> communicating with a central SQLDB hosted in a hosting company (each one
is
> sending data, waiting for data comparisons and receiving the data back). I
> have been using a Web Service to make the link between my apps and the
SQLDB,
> but now I want to connect my Windows Form apps directly to de SQLServer
> (because I think the roundtrip is going to be faster, which is the most
> important factor in my app)
> My question to the architects and everyone:
> Is this a good, secure, recommended, intelligent practice or this is a big
> big mistake '
>
> thks
> ken
Showing posts with label company. Show all posts
Showing posts with label company. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
Architecture design to support global data replication
Hi,
In our global company, there is a proposal to have SQL Server hubs at
specific locations, say one in North America (NA) and the other in Asia (with
scalability option that other hubs could be added as our company grows).
With this mind, we are in the process of designing a strategy to support
bi-directional (and may be 3-way or X number of way in the future)
transactional replication of our PORTAL database between NA and Asia so that
any changes made in the DB in NA server is reflected to the DB in the Asia
server and vice versa. NA server will be used by NA clients and the Asia
server, by Asian clients.
Any ideas what would be the best strategy to implement this, keeping
latency, network speed, and most importantly choice of replication method in
mind? The PORTAL database is designed to be less than 15 GB.
Your thoughts and comments are appreciated. TIA.
I would recommend transactional replication. It if it two way replication I
would use bi-directional transactional replication. With careful filtering
you should be able to scale this to several more nodes.
Peer-to-peer replication is also an option in SQL 2005, however all updates
should originate on one node.
Merge can be used, but it adds latency to each DML.
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
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:C84C50BF-571D-4F43-BBB7-BF81BE06E34F@.microsoft.com...
> Hi,
> In our global company, there is a proposal to have SQL Server hubs at
> specific locations, say one in North America (NA) and the other in Asia
> (with
> scalability option that other hubs could be added as our company grows).
> With this mind, we are in the process of designing a strategy to support
> bi-directional (and may be 3-way or X number of way in the future)
> transactional replication of our PORTAL database between NA and Asia so
> that
> any changes made in the DB in NA server is reflected to the DB in the Asia
> server and vice versa. NA server will be used by NA clients and the Asia
> server, by Asian clients.
> Any ideas what would be the best strategy to implement this, keeping
> latency, network speed, and most importantly choice of replication method
> in
> mind? The PORTAL database is designed to be less than 15 GB.
> Your thoughts and comments are appreciated. TIA.
In our global company, there is a proposal to have SQL Server hubs at
specific locations, say one in North America (NA) and the other in Asia (with
scalability option that other hubs could be added as our company grows).
With this mind, we are in the process of designing a strategy to support
bi-directional (and may be 3-way or X number of way in the future)
transactional replication of our PORTAL database between NA and Asia so that
any changes made in the DB in NA server is reflected to the DB in the Asia
server and vice versa. NA server will be used by NA clients and the Asia
server, by Asian clients.
Any ideas what would be the best strategy to implement this, keeping
latency, network speed, and most importantly choice of replication method in
mind? The PORTAL database is designed to be less than 15 GB.
Your thoughts and comments are appreciated. TIA.
I would recommend transactional replication. It if it two way replication I
would use bi-directional transactional replication. With careful filtering
you should be able to scale this to several more nodes.
Peer-to-peer replication is also an option in SQL 2005, however all updates
should originate on one node.
Merge can be used, but it adds latency to each DML.
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
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:C84C50BF-571D-4F43-BBB7-BF81BE06E34F@.microsoft.com...
> Hi,
> In our global company, there is a proposal to have SQL Server hubs at
> specific locations, say one in North America (NA) and the other in Asia
> (with
> scalability option that other hubs could be added as our company grows).
> With this mind, we are in the process of designing a strategy to support
> bi-directional (and may be 3-way or X number of way in the future)
> transactional replication of our PORTAL database between NA and Asia so
> that
> any changes made in the DB in NA server is reflected to the DB in the Asia
> server and vice versa. NA server will be used by NA clients and the Asia
> server, by Asian clients.
> Any ideas what would be the best strategy to implement this, keeping
> latency, network speed, and most importantly choice of replication method
> in
> mind? The PORTAL database is designed to be less than 15 GB.
> Your thoughts and comments are appreciated. TIA.
Architecture design to support global data replication
Hi,
In our global company, there is a proposal to have SQL Server hubs at
specific locations, say one in North America (NA) and the other in Asia (wit
h
scalability option that other hubs could be added as our company grows).
With this mind, we are in the process of designing a strategy to support
bi-directional (and may be 3-way or X number of way in the future)
transactional replication of our PORTAL database between NA and Asia so that
any changes made in the DB in NA server is reflected to the DB in the Asia
server and vice versa. NA server will be used by NA clients and the Asia
server, by Asian clients.
Any ideas what would be the best strategy to implement this, keeping
latency, network speed, and most importantly choice of replication method in
mind? The PORTAL database is designed to be less than 15 GB.
Your thoughts and comments are appreciated. TIA.I would recommend transactional replication. It if it two way replication I
would use bi-directional transactional replication. With careful filtering
you should be able to scale this to several more nodes.
Peer-to-peer replication is also an option in SQL 2005, however all updates
should originate on one node.
Merge can be used, but it adds latency to each DML.
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
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:C84C50BF-571D-4F43-BBB7-BF81BE06E34F@.microsoft.com...
> Hi,
> In our global company, there is a proposal to have SQL Server hubs at
> specific locations, say one in North America (NA) and the other in Asia
> (with
> scalability option that other hubs could be added as our company grows).
> With this mind, we are in the process of designing a strategy to support
> bi-directional (and may be 3-way or X number of way in the future)
> transactional replication of our PORTAL database between NA and Asia so
> that
> any changes made in the DB in NA server is reflected to the DB in the Asia
> server and vice versa. NA server will be used by NA clients and the Asia
> server, by Asian clients.
> Any ideas what would be the best strategy to implement this, keeping
> latency, network speed, and most importantly choice of replication method
> in
> mind? The PORTAL database is designed to be less than 15 GB.
> Your thoughts and comments are appreciated. TIA.
In our global company, there is a proposal to have SQL Server hubs at
specific locations, say one in North America (NA) and the other in Asia (wit
h
scalability option that other hubs could be added as our company grows).
With this mind, we are in the process of designing a strategy to support
bi-directional (and may be 3-way or X number of way in the future)
transactional replication of our PORTAL database between NA and Asia so that
any changes made in the DB in NA server is reflected to the DB in the Asia
server and vice versa. NA server will be used by NA clients and the Asia
server, by Asian clients.
Any ideas what would be the best strategy to implement this, keeping
latency, network speed, and most importantly choice of replication method in
mind? The PORTAL database is designed to be less than 15 GB.
Your thoughts and comments are appreciated. TIA.I would recommend transactional replication. It if it two way replication I
would use bi-directional transactional replication. With careful filtering
you should be able to scale this to several more nodes.
Peer-to-peer replication is also an option in SQL 2005, however all updates
should originate on one node.
Merge can be used, but it adds latency to each DML.
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
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:C84C50BF-571D-4F43-BBB7-BF81BE06E34F@.microsoft.com...
> Hi,
> In our global company, there is a proposal to have SQL Server hubs at
> specific locations, say one in North America (NA) and the other in Asia
> (with
> scalability option that other hubs could be added as our company grows).
> With this mind, we are in the process of designing a strategy to support
> bi-directional (and may be 3-way or X number of way in the future)
> transactional replication of our PORTAL database between NA and Asia so
> that
> any changes made in the DB in NA server is reflected to the DB in the Asia
> server and vice versa. NA server will be used by NA clients and the Asia
> server, by Asian clients.
> Any ideas what would be the best strategy to implement this, keeping
> latency, network speed, and most importantly choice of replication method
> in
> mind? The PORTAL database is designed to be less than 15 GB.
> Your thoughts and comments are appreciated. TIA.
Architecture design to support global data replication
Hi,
In our global company, there is a proposal to have SQL Server hubs at
specific locations, say one in North America (NA) and the other in Asia (with
scalability option that other hubs could be added as our company grows).
With this mind, we are in the process of designing a strategy to support
bi-directional (and may be 3-way or X number of way in the future)
transactional replication of our PORTAL database between NA and Asia so that
any changes made in the DB in NA server is reflected to the DB in the Asia
server and vice versa. NA server will be used by NA clients and the Asia
server, by Asian clients.
Any ideas what would be the best strategy to implement this, keeping
latency, network speed, and most importantly choice of replication method in
mind? The PORTAL database is designed to be less than 15 GB.
Your thoughts and comments are appreciated. TIA.I would recommend transactional replication. It if it two way replication I
would use bi-directional transactional replication. With careful filtering
you should be able to scale this to several more nodes.
Peer-to-peer replication is also an option in SQL 2005, however all updates
should originate on one node.
Merge can be used, but it adds latency to each DML.
--
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
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:C84C50BF-571D-4F43-BBB7-BF81BE06E34F@.microsoft.com...
> Hi,
> In our global company, there is a proposal to have SQL Server hubs at
> specific locations, say one in North America (NA) and the other in Asia
> (with
> scalability option that other hubs could be added as our company grows).
> With this mind, we are in the process of designing a strategy to support
> bi-directional (and may be 3-way or X number of way in the future)
> transactional replication of our PORTAL database between NA and Asia so
> that
> any changes made in the DB in NA server is reflected to the DB in the Asia
> server and vice versa. NA server will be used by NA clients and the Asia
> server, by Asian clients.
> Any ideas what would be the best strategy to implement this, keeping
> latency, network speed, and most importantly choice of replication method
> in
> mind? The PORTAL database is designed to be less than 15 GB.
> Your thoughts and comments are appreciated. TIA.
In our global company, there is a proposal to have SQL Server hubs at
specific locations, say one in North America (NA) and the other in Asia (with
scalability option that other hubs could be added as our company grows).
With this mind, we are in the process of designing a strategy to support
bi-directional (and may be 3-way or X number of way in the future)
transactional replication of our PORTAL database between NA and Asia so that
any changes made in the DB in NA server is reflected to the DB in the Asia
server and vice versa. NA server will be used by NA clients and the Asia
server, by Asian clients.
Any ideas what would be the best strategy to implement this, keeping
latency, network speed, and most importantly choice of replication method in
mind? The PORTAL database is designed to be less than 15 GB.
Your thoughts and comments are appreciated. TIA.I would recommend transactional replication. It if it two way replication I
would use bi-directional transactional replication. With careful filtering
you should be able to scale this to several more nodes.
Peer-to-peer replication is also an option in SQL 2005, however all updates
should originate on one node.
Merge can be used, but it adds latency to each DML.
--
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
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:C84C50BF-571D-4F43-BBB7-BF81BE06E34F@.microsoft.com...
> Hi,
> In our global company, there is a proposal to have SQL Server hubs at
> specific locations, say one in North America (NA) and the other in Asia
> (with
> scalability option that other hubs could be added as our company grows).
> With this mind, we are in the process of designing a strategy to support
> bi-directional (and may be 3-way or X number of way in the future)
> transactional replication of our PORTAL database between NA and Asia so
> that
> any changes made in the DB in NA server is reflected to the DB in the Asia
> server and vice versa. NA server will be used by NA clients and the Asia
> server, by Asian clients.
> Any ideas what would be the best strategy to implement this, keeping
> latency, network speed, and most importantly choice of replication method
> in
> mind? The PORTAL database is designed to be less than 15 GB.
> Your thoughts and comments are appreciated. TIA.
Thursday, March 8, 2012
application with sql server database failing
Hi all,
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql serve
r
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql ser
ver
> database while application is running through a scheduled process it is ju
st
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are
in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give m
e
> some advices why this canb happen?
> Thank you,
> BaniSQL.
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql serve
r
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql ser
ver
> database while application is running through a scheduled process it is ju
st
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are
in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give m
e
> some advices why this canb happen?
> Thank you,
> BaniSQL.
application with sql server database failing
Hi all,
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql server
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql server
> database while application is running through a scheduled process it is just
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give me
> some advices why this canb happen?
> Thank you,
> BaniSQL.
I'm having problem with the step that runs from application which is
programmed by a company. These days on certain step which is using sql server
database while application is running through a scheduled process it is just
stoping in one certain moment. I can not locate the problem since I can't
receive the error. I'm reindexing the database, update of statistics. The
server is HP with SAN technology with the 5GB of RAM. I've putted
pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
locate fixed memory for sql server of 4 GB. First I left dynamically to be
used memory from sql server 2000, but again it crashed.
Can you please suggest what additionally I have to tune or check, since I
can't reproduce or see the error. Application and sql server database are in
the (this) same powerfull server.
Maybe you had such problems from your experience, so I expect to to give me
some advices why this canb happen?
Thank you,
BaniSQL.Try running the sql profiler while your process that is throwing the
error is running to see where it is crashing exactly.
BaniSQL wrote:
> Hi all,
> I'm having problem with the step that runs from application which is
> programmed by a company. These days on certain step which is using sql server
> database while application is running through a scheduled process it is just
> stoping in one certain moment. I can not locate the problem since I can't
> receive the error. I'm reindexing the database, update of statistics. The
> server is HP with SAN technology with the 5GB of RAM. I've putted
> pagefile.sys on the C drive with 5-7.5 GB space. I tried to enable AWE and
> locate fixed memory for sql server of 4 GB. First I left dynamically to be
> used memory from sql server 2000, but again it crashed.
> Can you please suggest what additionally I have to tune or check, since I
> can't reproduce or see the error. Application and sql server database are in
> the (this) same powerfull server.
> Maybe you had such problems from your experience, so I expect to to give me
> some advices why this canb happen?
> Thank you,
> BaniSQL.
Subscribe to:
Posts (Atom)