Re: where to put SQL Server ?

From: S. Pidgorny (slavickp_at_yahoo.com)
Date: 05/29/04

  • Next message: Henning Krause: "Re: Drive restrictions but still searchable" 
    Date: Sat, 29 May 2004 21:41:14 +1000

    Refer to the

    http://support.microsoft.com/?id=316898

    for the details. 

    -- 
Svyatoslav Pidgorny, MVP, MCSE
-= F1 is the key =-
"Hernán Castelo" <hcastelo@cedi.frba.utn.edu.ar> wrote in message
news:#80qSRLREHA.2112@TK2MSFTNGP11.phx.gbl...
> oh, you was the poster of "overkill" all right
> look, i don't know much about ssl
>
> does ssl need to be implemented at both endpoints?
> from an asp page to sql ?
> from iis to sql ?
> does ssl is transparent ?
>
> what about the option "force encryption"
> at "sqlserver - server network utility" ?
>
> thanks again
> (i am now beginning to looking for ssl documentation)
>
> "S. Pidgorny <MVP>" <slavickp@yahoo.com> escribió en el mensaje
> news:uLE9E9IREHA.1396@TK2MSFTNGP12.phx.gbl...
> > That was me who told so. Overhead won't be huge, as performance of SQL
> > Server will be lokely limiting factor, not the network-traffic - please
> > advise if you're expecting transactions that will return big datasets
and
> > have very powerful SQL Server. I just don't like the idea of IPsec
> > communication across firewalls - that is pretty much like putting a
> > communication line that bypasses firewall and leaves traffic control to
> the
> > endpoints. And it is harder to implement than SSL encryption for TDS,
yet
> > with the same goal - confidentiality.
> >
> > -- 
> > Svyatoslav Pidgorny, MVP, MCSE
> > -= F1 is the key =-
> >
> > "Hernán Castelo" <hcastelo@cedi.frba.utn.edu.ar> wrote in message
> > news:e1ZbXv#QEHA.1620@TK2MSFTNGP12.phx.gbl...
> > > somebody in a newsgroup
> > > seuggest me that ipsec is an "overkill"
> > > and use ssl rather than it
> > >
> > > i don't believe i go to use ssl
> > > but,
> > > how much overhead take ipsec ?
> > >
> > > bye thanks
> > >
> >
> >
>
>
  • Next message: Henning Krause: "Re: Drive restrictions but still searchable"

    Relevant Pages

    • RE: SQL Server 2000 desktop MSDE + Internet Explorer 7 = Cant con
      ... cannot open SQL Enterprise Manager. ... From the error message, it seems to be related to SSL and certifcate. ... Edit the registry on the SQL Server machine and make the following ...
      (microsoft.public.sqlserver.connect)
    • Re: Seperation of SQL server files from windows 2000 directories.
      ... >> To be specific I see no support for running IPSEC or SSL where the SQL ... > fully supported when runing under non-administrative account. ... > users to your SQL Server service, and what makes you believe that SSL ...
      (microsoft.public.sqlserver.security)
    • RE: SQL Server 2000 desktop MSDE + Internet Explorer 7 = Cant connect
      ... cannot open SQL Enterprise Manager. ... suggest that you temporarily disable SSL for SQL Server to isolate the ... Edit the registry on the SQL Server machine and make the following ... Microsoft Online Community Support ...
      (microsoft.public.sqlserver.connect)
    • Re: installed ssl-certificate -> SQL-Server locked !
      ... Certificate issued to the FQDN name of the computer. ... This would be the same if you were to setup IIS for SSL using Server ... So, if IIS and SQL are on the same machine, ... Enable SSL Encryption for SQL Server 2000 with Certificate ...
      (microsoft.public.sqlserver.security)
    • Re: Seperation of SQL server files from windows 2000 directories.
      ... > To be specific I see no support for running IPSEC or SSL where the SQL ... I believe that SSL encryption for SQL Server 2000 with Service Pack 3 is ... fully supported when runing under non-administrative account. ...
      (microsoft.public.sqlserver.security)