Architecture question.

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

Architecture advice

I need some advice on architecture.
I am a newbie to SQL Server, but a long time Access and FrontPage developer.
With these two apps, I have a "publish to the web" mentality, so I have
envisioned having my development SQL Server database on my local harddisk
and periodically "publishing" it to my production SQL Server out on the
Internet. (By development server, I mean where data creation and update is
accomplished.)
My idea: Update the production SQL Server periodically (weekly) from the
development server, but I need to capture data received from users on the
production server, then edit and merge on the development server for later
republishing to the production server. Alternatively, all data updates could
be done on the production server with backups to the local harddisk server.
Problem: My Internet SQL Server provider does NOT allow replication nor the
creation or implementation of DTS packages, but does support the DTS
import/export functions to a point of connection to and selection of my
database.
Which would be best approach to implement given the ISP's restrictions? Or
can you suggest another approach?
Many thanks for your expertise to point me in the right direction.
CharaxDo all your production changes on your production server,
and don't mix your Dev server with your prod server. If
you really need to do things first on your Dev server and
then publish 'it' to the prod server, you should then
treat your dev server as a prod server unless of course
by 'publishing' you meant scheduled releases in a
controlled fashion.
Linchi
>--Original Message--
>I need some advice on architecture.
>I am a newbie to SQL Server, but a long time Access and
FrontPage developer.
>With these two apps, I have a "publish to the web"
mentality, so I have
>envisioned having my development SQL Server database on
my local harddisk
>and periodically "publishing" it to my production SQL
Server out on the
>Internet. (By development server, I mean where data
creation and update is
>accomplished.)
>My idea: Update the production SQL Server periodically
(weekly) from the
>development server, but I need to capture data received
from users on the
>production server, then edit and merge on the development
server for later
>republishing to the production server. Alternatively, all
data updates could
>be done on the production server with backups to the
local harddisk server.
>Problem: My Internet SQL Server provider does NOT allow
replication nor the
>creation or implementation of DTS packages, but does
support the DTS
>import/export functions to a point of connection to and
selection of my
>database.
>Which would be best approach to implement given the ISP's
restrictions? Or
>can you suggest another approach?
>Many thanks for your expertise to point me in the right
direction.
>Charax
>
>.
>|||Thanks for the quick response, Linchi. Yes, you are quite right and my
terminology was wrong. (Remember, I'm an SQL server newbie!)
I now will call the server on my local harddisk the 'production' server. The
production server has the most current data and any changes to data or
database structure are made there. The ISP's SQL Server on the Internet is
simply a copy of the production server that web users can access -- let's
call it the 'slave'. Is this a reasonable architecture?
If so, how do you recommend that I update the slave server on the Internet
from the production server on local harddisk? Please keep in mind that the
slave server does not support replication, and only supports the DTS
import/export functions to a point of connection to and selection of my
database. On my local production server, I have all replication and DTS
features.
Many thanks for your ideas and help to a new guy.
Charax
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:339801c3e1c8$08021990$a601280a@.phx.gbl...
> Do all your production changes on your production server,
> and don't mix your Dev server with your prod server. If
> you really need to do things first on your Dev server and
> then publish 'it' to the prod server, you should then
> treat your dev server as a prod server unless of course
> by 'publishing' you meant scheduled releases in a
> controlled fashion.
> Linchisql

Architecture advice

I need some advice on architecture.
I am a newbie to SQL Server, but a long time Access and FrontPage developer.
With these two apps, I have a "publish to the web" mentality, so I have
envisioned having my development SQL Server database on my local harddisk
and periodically "publishing" it to my production SQL Server out on the
Internet. (By development server, I mean where data creation and update is
accomplished.)
My idea: Update the production SQL Server periodically (weekly) from the
development server, but I need to capture data received from users on the
production server, then edit and merge on the development server for later
republishing to the production server. Alternatively, all data updates could
be done on the production server with backups to the local harddisk server.
Problem: My Internet SQL Server provider does NOT allow replication nor the
creation or implementation of DTS packages, but does support the DTS
import/export functions to a point of connection to and selection of my
database.
Which would be best approach to implement given the ISP's restrictions? Or
can you suggest another approach?
Many thanks for your expertise to point me in the right direction.
CharaxDo all your production changes on your production server,
and don't mix your Dev server with your prod server. If
you really need to do things first on your Dev server and
then publish 'it' to the prod server, you should then
treat your dev server as a prod server unless of course
by 'publishing' you meant scheduled releases in a
controlled fashion.
Linchi

quote:

---

>--Original Message--
>I need some advice on architecture.
>I am a newbie to SQL Server, but a long time Access and

---

FrontPage developer.

quote:

---

>With these two apps, I have a "publish to the web"

---

mentality, so I have

quote:

---

>envisioned having my development SQL Server database on

---

my local harddisk

quote:

---

>and periodically "publishing" it to my production SQL

---

Server out on the

quote:

---

>Internet. (By development server, I mean where data

---

creation and update is

quote:

---

>accomplished.)
>My idea: Update the production SQL Server periodically

---

(weekly) from the

quote:

---

>development server, but I need to capture data received

---

from users on the

quote:

---

>production server, then edit and merge on the development

---

server for later

quote:

---

>republishing to the production server. Alternatively, all

---

data updates could

quote:

---

>be done on the production server with backups to the

---

local harddisk server.

quote:

---

>Problem: My Internet SQL Server provider does NOT allow

---

replication nor the

quote:

---

>creation or implementation of DTS packages, but does

---

support the DTS

quote:

---

>import/export functions to a point of connection to and

---

selection of my

quote:

---

>database.
>Which would be best approach to implement given the ISP's

---

restrictions? Or

quote:

---

>can you suggest another approach?
>Many thanks for your expertise to point me in the right

---

direction.

quote:

---

>Charax
>
>.
>

---

|||Thanks for the quick response, Linchi. Yes, you are quite right and my
terminology was wrong. (Remember, I'm an SQL server newbie!)
I now will call the server on my local harddisk the 'production' server. The
production server has the most current data and any changes to data or
database structure are made there. The ISP's SQL Server on the Internet is
simply a copy of the production server that web users can access -- let's
call it the 'slave'. Is this a reasonable architecture?
If so, how do you recommend that I update the slave server on the Internet
from the production server on local harddisk? Please keep in mind that the
slave server does not support replication, and only supports the DTS
import/export functions to a point of connection to and selection of my
database. On my local production server, I have all replication and DTS
features.
Many thanks for your ideas and help to a new guy.
Charax
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:339801c3e1c8$08021990$a601280a@.phx.gbl...

quote:

---

> Do all your production changes on your production server,
> and don't mix your Dev server with your prod server. If
> you really need to do things first on your Dev server and
> then publish 'it' to the prod server, you should then
> treat your dev server as a prod server unless of course
> by 'publishing' you meant scheduled releases in a
> controlled fashion.
> Linchi

---

APPS for SSIS

Help!
Does anyone know where can i find some windows or web applications using ssis for manipulations?
Are you looking for case studies? Or actual applications (executables) that incorporate SSIS?|||Hi,
an actual application (code sample) that use or manipulate ssis, hope you can help me on this one

Thanks|||

arsonist wrote:

Hi,
an actual application (code sample) that use or manipulate ssis, hope you can help me on this one

Thanks

This link should help: http://msdn2.microsoft.com/en-us/library/ms345167.aspx

Apps cannot connect to SQL after server upgrade to 2003 R2

I had a working SQL Server 2005 install based on an evaluation of Windows
Server 2003 SP2 Ent. I have several other servers running MOSS 07 and WSUS.
I upgraded the SQL server machine to 2003 R2 SP2 Ent. as the evaluation had
9 days before expiry.
However after the upgrade other machines cannot connect to the databases in
SQL, yet i can connect locally using SQL server management studio, the
databases are all intact and permissions have not been changed.
Any ideas would be gratefully received as I have my A Level coursework
stored in a a sharepoint site in one of these Databases!!!!!
AdamDid you check your Windows Firewall settings in your upgraded machine?
If it's not the problem, what's the error message exactly?
--
Ekrem Ã?nsoy
"Adam Gent" <AdamGent@.discussions.microsoft.com> wrote in message
news:2997350C-2891-46FB-AC33-010DBA43C807@.microsoft.com...
>I had a working SQL Server 2005 install based on an evaluation of Windows
> Server 2003 SP2 Ent. I have several other servers running MOSS 07 and
> WSUS.
> I upgraded the SQL server machine to 2003 R2 SP2 Ent. as the evaluation
> had
> 9 days before expiry.
> However after the upgrade other machines cannot connect to the databases
> in
> SQL, yet i can connect locally using SQL server management studio, the
> databases are all intact and permissions have not been changed.
> Any ideas would be gratefully received as I have my A Level coursework
> stored in a a sharepoint site in one of these Databases!!!!!
> Adam|||windows firewall is off - i get error message when i try to access sharepoint
pages - "cannot connect to configuration database" and WSUS gives similar
error.
I can see no errrors in the application logs on the SQL server.|||Then go to SQL Server Configuration Manager and check out your protocols.
Ensure they are enabled and configured correctly.
Also, You did not mention which SQL Server Edition you have, however SQL
Server 2005 Express and Developer Editions are configured Remote Connections
disabled by default. You could check it from SQL Server Surface Area
Configuration tool.
--
Ekrem Ã?nsoy
"Adam Gent" <AdamGent@.discussions.microsoft.com> wrote in message
news:654B7ED7-35C6-4854-8DBA-128757AAC45F@.microsoft.com...
> windows firewall is off - i get error message when i try to access
> sharepoint
> pages - "cannot connect to configuration database" and WSUS gives similar
> error.
> I can see no errrors in the application logs on the SQL server.|||I have SQL Server 2005 SP2 Enterprise.
All remote protocols are enabled apart from VIA as the service wont start
with it enabled.
"Ekrem Ã?nsoy" wrote:
> Then go to SQL Server Configuration Manager and check out your protocols.
> Ensure they are enabled and configured correctly.
> Also, You did not mention which SQL Server Edition you have, however SQL
> Server 2005 Express and Developer Editions are configured Remote Connections
> disabled by default. You could check it from SQL Server Surface Area
> Configuration tool.
> --
> Ekrem Ã?nsoy
>
> "Adam Gent" <AdamGent@.discussions.microsoft.com> wrote in message
> news:654B7ED7-35C6-4854-8DBA-128757AAC45F@.microsoft.com...
> > windows firewall is off - i get error message when i try to access
> > sharepoint
> > pages - "cannot connect to configuration database" and WSUS gives similar
> > error.
> >
> > I can see no errrors in the application logs on the SQL server.
>