Personally I would never make any SQL database available to the general
Internet community. You are asking it to be attacked if you do and believe
me, if it has any sort of usefull info stored in it someone will hack it.
You may be better off looking at some sort of front end or portal that your
customers can use (maybe a web front end or something)? Not sure if that is
possible or not but just a thought.
You mentioned XML and maybe that would be good.. Maybe something like an XML
query/update system would work?
I would try to keep ANY direct access limited to just a front end of some
sort and put that data behind a firewall, etc.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Charles Cox
VC/VB/C# Developer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"asdf" <as**@asdf.com> wrote in message
news:HM*******************@news20.bellglobal.com.. .
Hi,
Currently, I have one database for Intranet clients on the server behind
the
firewall. But I was asked to allow the extranet users to access the same
data. From the security perspective what is the best way to make that data
accessible.
Should we have two databases one for Intranet and one for Extranet? In
that
case the second one would be a replica but that would cost us money for
the
extra MS SQL license. Maybe it is OK to have only one physical database.
Maybe MySQL is a good idea to use as a replica that would be refreshed
nightly. Or XML data would be OK to server only extranet.
What would be the best idea to do.
We are all MS shop.
Thanks in advance for any help,
Tom
