Complete user lockdown and then carefully assigning permissions on the
object level.  :-)  I would imagine anyways....


Mike



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2003 3:12 PM
To: CF-Talk
Subject: RE: CF and MS SQL server authentication

>> As for running SQL server on private network, that would be
>> fine except for remote administration - how can one with ease
>> connect to a host on a private network from a remote location.
>
> In that case, maybe you shouldn't be able to remotely administer your
> database server. In any case, your database server should not arbitrarily
> accept connections from anywhere in the world, and it really shouldn't be
> accessible at all from a public network. It should only accept connections
> from the web server, or from trusted internal sources. If you absolutely
> need remote administration, you could administer it from the web server, I
> suppose, although that has its own obvious problems.
>

That might work for a single company's site, but hosting companies can't do
that. You
have to give your clients some kind of remote access to manage their
databases.  Are
there any techniques/suggestions for allowing remote access to SQL server
via the
internet?  Obviously changing the port is one small step but are there
others people are
using?

Tom Nunamaker
  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to